9ARD171384-600 - en System 800xa 6.0 IEC 61850 Engineering Workflow

System 800xA
IEC 61850
Engineering Workflow
System Version 6.0
Power and productivity

for a better world ™
System 800xA
IEC 61850
Engineering Workflow
System Version 6.0

NOTICE
This document contains information about one or more ABB products and may include a
description of or a reference to one or more standards that may be generally relevant to
the ABB products. The presence of any such description of a standard or reference to a
standard is not a representation that all of the ABB products referenced in this document
support all of the features of the described or referenced standard. In order to determine
the specific features supported by a particular ABB product, the reader should consult the
product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intel-
lectual property in the ABB products described in this document.
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license. This
product meets the requirements specified in EMC Directive 2004/108/EC and in Low Volt-
age Directive 2006/95/EC.
TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respec-
tive owners.
Copyright © 2003 - 2014 by ABB.

All rights reserved.
Release: August 2014

Document number: 9ARD171384-600
Table of Contents
About This User Manual

Assumption........................................................................................................................8
Exclusions..........................................................................................................................9
Methodology......................................................................................................................9
User Manual Conventions .................................................................................................9
Feature Pack .........................................................................................................10
Warning, Caution, Information, and Tip Icons ....................................................10
Terminology.....................................................................................................................11
Released User Manuals and Release Notes.....................................................................14
Section 1 - Introduction
Objective..........................................................................................................................17
Classification ...................................................................................................................17
Section 2 - Substation Engineering

Inputs Required ...............................................................................................................22
Project Inputs .......................................................................................................22
ABB Engineer or Project Inputs ..........................................................................23
Sample Inputs with Signal List ............................................................................23
Tools Required .....................................................................................................31
Configuring CI868 IED ...................................................................................................32
CI868 CID File Export using IEC 61850 Wizard ................................................47
CI868 ICD File Export using IEC 61850 Wizard ................................................54
Configuring other IEDs ...................................................................................................57
Substation Communication Engineering in CCT600 / IET600.......................................83
Communication Engineering using CCT600 .......................................................83
9ARD171384-600 5
Table of Contents
Communication Engineering using IET600 ...................................................... 119

Updating IED configuration with SCD file................................................................... 160
CI868 IED Engineering with Control Builder M.......................................................... 168
CI868 IED Sending GOOSE Signals................................................................. 180
CI868 IED Receiving GOOSE Signals.............................................................. 181
CI868 IED MMS Command Signal................................................................... 186
CI868 IED Receiving MMS Signal ................................................................... 186
Control Builder Application Engineering with IEC 61850 Communication .... 187
IEC 61850 Connect Engineering .................................................................................. 221
IEC 61850 OPC Server Configuration............................................................... 221
800xA Control and Functional Structure Configuration ................................... 239
Summary ....................................................................................................................... 261
Section 3 - Handling the Changes at Different Levels of

Engineering and Commissioning
Addition of a LN, for example, SPGGIO in one of the IED......................................... 264
Addition of a New Third Party IED in the Configuration............................................. 269
Addition of New Signal through MMS......................................................................... 275
Addition of New GOOSE Signal between CI868 and an IED...................................... 277
Modification in Name at Different Levels .................................................................... 285
Replace Burnt Out IED with New One ......................................................................... 290
IED Application Logic Change..................................................................................... 291
Alarm and Event Related Modification......................................................................... 293
Index
6 9ARD171384-600
About This User Manual
Any security measures described in this User Manual, for example, for user
access, password security, network security, firewalls, virus protection, etc.,
represent possible steps that a user of an 800xA System may want to consider
based on a risk assessment for a particular application and installation. This risk
assessment, as well as the proper implementation, configuration, installation,
operation, administration, and maintenance of all relevant security related
equipment, software, and procedures, are the responsibility of the user of the
800xA System.
This user manual describes the IEC 61850 (Ed1) Engineering Workflow in 800xA.
The intention is to execute typical engineering use cases which the user may come
across while implementing the actual engineering. This manual provides a step-by-
step procedure to engineer Substation Automation (SA) and Process Automation
(PA) in an integrated manner. This manual also provides the rules and guidelines for
the engineering workflow.
This manual:
• Provides a guaranteed and optimized solution to perform IEC 61850 (Ed1)
Engineering Workflow in 800xA.
• Concentrates on the following ways to perform the IEC 61850 (Ed1)
Engineering Workflow in 800xA.
– Simplified workflow with CCT600 or IET600 Tool
The main topics covered in this manual are:
• Overview of IEC 61850 (Ed1) Engineering with 800xA.
• Substation Engineering Workflow.
• Maintenance.
9ARD171384-600 7
Assumption About This User Manual
• Useful tools for commissioning and testing the IED.

The user must have adequate knowledge of the 800xA control system and IEC
61850 (Ed1) protocol.
This manual can be used in situations like substation planning or in the
commissioning activity. This manual describes modification and maintenance use
cases when a small change is required for a fully configured substation.
This manual is useful to the following user categories:
• Planning engineers.
• Commissioning engineers.
• Plant engineers.
• Configuration engineers.
• System architect.
The following sections are included in this manual.
• Section 1, Introduction, provides a brief overview of IEC 61850 (Ed1)
Engineering with 800xA.
• Section 2, Substation Engineering, describes a simplified workflow for 800xA
IEC 61850 (Ed1) Engineering.
• Section 3, Handling the Changes at Different Levels of Engineering and
Commissioning, describes the changes required after substation configuration
during commissioning or in run-time.
Assumption
In this manual, user works with different tools with respect to Substation
Automation and Process Automation. This manual helps the user to understand the
usage of these tools in an integrated manner to perform complete IEC 61850 (Ed1)
Engineering.
It is assumed that the user has undergone a suitable training program and has the
working knowledge of tools. For example, Control Builder/CCT, IET600 and PCM
600 should be known to SA engineer and 800xA to plant engineer.
8 9ARD171384-600
About This User Manual Exclusions
It is also expected that the user has an adequate understanding of IEC 61850 (Ed1)
standard and different abbreviations such as SCD, CID, ICD, GOOSE, MMS, and
IED.
Exclusions
This user manual does not cover the basic installation and configuration of 800xA
and other associated tools that contribute to the workflow.
Methodology
The user should execute the following engineering use cases in a structured manner:
• Complete Substation Engineering use case is executed based on an actual
customer project. The procedure starts with normal inputs from the customer
and ends with a completely configured substation with respect to Substation
Automation and Process Automation.
• Maintenance use cases such as addition/deletion of IEDs, signal change
through GOOSE and MMS, addition/deletion of Logical Nodes, and change of
faulty IED with new one.
• Modifying use cases such as change in IED name, IP address, change in LN
name, change in tag name for primary equipment, and alarm severity
modification.
• Complex use cases such as redundancy handling and multiple subnetworks in
one SCD.
• Other use case such as handling of special IEDs. For example, REF541,
REF542+, REF500 and 3rd party IEDs.
User Manual Conventions

Microsoft Windows conventions are normally used for the standard presentation of
material when entering text, key sequences, prompts, messages, menu items, screen
elements, etc.
9ARD171384-600 9
Feature Pack About This User Manual
Feature Pack
The Feature Pack content (including text, tables, and figures) included in this User
Manual is distinguished from the existing content using the following
two separators:
Feature Pack Functionality______________________________________________________________________
<Feature Pack Content>

___________________________________________________________________________________________
Feature Pack functionality included in an existing table is indicated using a

table footnote (*):
*Feature Pack Functionality
Unless noted, all other information in this User Manual applies to 800xA Systems
with or without a Feature Pack installed.
Warning, Caution, Information, and Tip Icons

This User Manual includes Warning, Caution, and Information where appropriate to
point out safety related or other important information. It also includes Tip to point
out useful hints to the reader. The corresponding symbols should be interpreted as
follows:
Electrical warning icon indicates the presence of a hazard that could result in
electrical shock.
Warning icon indicates the presence of a hazard that could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard that could result
in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
10 9ARD171384-600
About This User Manual Terminology
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
fully comply with all Warning and Caution notices.
Terminology
A complete and comprehensive list of Terms is included in the System 800xA,
Engineering Concepts instruction (3BDS100972*). A complete and comprehensive
list of terms is included in System 800xA System Guide Functional Description
(3BSE038018*). The listing includes terms and definitions that apply to the 800xA
System where the usage is different from commonly accepted industry standard
definitions and definitions given in standard dictionaries such as Webster’s
Dictionary of Computer Terms. Terms that uniquely apply to this User Manual are
listed in the following table.
Term/Acronym Description
800xA ABB automation system (eXtended Automation).
AC 800M ABB Controller 800M series, general purpose process
Controller series by ABB.
AC 800M Controller Any Controller constructed from the units and units
connected to the AC 800M hardware platform.
AE Alarm and Event.
Append Function for creating objects (based on object types) in
the 800xA Control Structure.
CCT Communication Configuration Tool.
CDC Common Data Class, is a Data Type definition in
IEC61850.
CDC Block CDC representation in Control Builder M Project
Explorer.
CET Communication Engineering Tool.
9ARD171384-600 11
Terminology About This User Manual
CID Configured IED Description file.
CI868 Module CI868 module for IEC 61850 (Ed1). Communication
Interface Module for AC 800M controller. These modules
are connected over the CEX bus and contain
implementation of a specific communication protocol.
Control Builder M Controller Builder M (Control Builder Professional or
Compact Control Builder).
DA Data Access / Data Attribute.
DO Data Object
FBD Feeder Block Diagram.
FB Function Block
GOOSE Generic Object Oriented Substation Event. Based on the
VLAN and priority tagging, GOOSE is used for very fast
peer-to-peer data exchange between IEC 61850 (Ed1)
compliant IEDs, also termed as Horizontal
Communication.
GCB GOOSE Control Block.
HMI Human Machine Interface.
I/O Input and Output.
ICD IED Capability Description. A type of SCL file.
IEC International Electrotechnical Commission.
IEC 61850 (Ed1) IEC standard for Communication Networks and Systems
in Substations.
System 800xA only supports IEC 61850-Ed1(Edition1).

IED Intelligent Electronic Device.
IET Integrated Engineering Tool.
12 9ARD171384-600
About This User Manual Terminology
LD Logical Device: A virtual device which enables
aggregation of Logical Nodes and Datasets for
communication purposes. Additionally, Logical Devices
contain convenient lists of frequently accessed or
referred to information. For example, datasets.
LN Logical Node.
MMS Manufacturing Message Specification (MMS) is an
international standard (ISO 9506) dealing with
messaging system for transferring real time process data
and supervisory control information between network
devices and/or computer applications.
Node A computer communicating on a network, for example
the Internet, Plant, Control or IO network. Each node
has a unique node address with a format depending on
the network it is connected to.
OCS Open Control System.
OPC OLE for Process Control. A set of standard interfaces
based on COM technology.
OT Object Type, object template in Object Type Structure in
800xA.
PA Process Automation.
Plant Explorer Process Portal A.
PGS Power Generation Solutions.
PMS Power Management Solutions.
RCB Report Control Block.
Retrieve Function for collecting information regarding a control
network.
SA Substation Automation.
SBO Select Before Operate Command
9ARD171384-600 13
Released User Manuals and Release Notes About This User Manual
SCD Substation Configuration Description, type of SCL file.
SCL Substation Configuration Language.
SLD Single Line Diagram.
Upload Retrieve + Append.
XML eXtensible Markup Language.
Released User Manuals and Release Notes

A complete list of all User Manuals and Release Notes applicable to System 800xA
is provided in System 800xA Released User Manuals (3BUA000263*).
System 800xA Released User Manuals (3BUA000263*) is updated each time a
document is updated or a new document is released. It is in pdf format and is
provided in the following ways:
• Included on the documentation media provided with the system and published
to ABB SolutionsBank when released as part of a major or minor release,
Service Pack, Feature Pack, or System Revision.
• Published to ABB SolutionsBank when a User Manual or Release Note is
updated in between any of the release cycles listed in the first bullet.
A product bulletin is published each time System 800xA Released User Manuals
(3BUA000263*) is updated and published to ABB SolutionsBank.
14 9ARD171384-600
Section 1 Introduction
IEC stands for International Electrotechnical Commission. IEC 61850 (Ed1) is an

IEC standard for Communication Networks and Systems in Substations.
ABB provides Power management and Power generation solutions to industries
such as refineries, petrochemical plants, and power plants using 800xA Process
Automation systems. Power applications such as load shedding, generator controls,
unit control, and synchronization can be offered to provide optimum power
reliability, utilization, and control of the customers electrical network. Power
management and Power generation solutions logics run on AC 800M process
controllers and the Human Interface functions are available on Operator workplaces.
The Substation Automation domain in the recent years has accepted IEC 61850
(Ed1) as the communication standard for interoperability between automation
devices on the substation network. IEC 61850 (Ed1) advocates interoperability
amongst IEDs from various manufacturers using common engineering models, data
formats and communication protocol.
The influence of IEC 61850 (Ed1) has also spread from traditional Power Utility
Substations to the Industrial Substation Automation area. Increasing number of
industrial customers today seek to automate their electrical networks and combine
the Power management and Power generation solutions with Protection and Control
devices using devices conforming to IEC 61850 (Ed1).
9ARD171384-600 15
Section 1 Introduction
Doma i n Cont r ol l e r AC 8 0 0M Engi ne e r i ng

Wor kpl a c e Ope r a t or Cl i e nt s
8 0 0xA Pl a nt N e t w or k
Aspe c t Se r ve r
+
I EC 6 1 8 5 0 CS
+
AC8 0 0M CS
8 0 0xA Cont r ol N e t w or k
CI 8 6 8 PM8 xx
I EC 6 1 8 5 0 MMS
I EC 6 1 8 5 0 GOOSE & MMS
Subst a t i on
I EC 6 1 8 5 0 Ri ng N e t w or k
I ED De vi c e s
Subne t w or k
Figure 1. Sample system configurations for combined 800xA based Process

Automation and IEC 61850 (Ed1) Industrial SA
16 9ARD171384-600
Section 1 Introduction Objective
Objective
In general, the implementation of 800xA-IEC 61850 (Ed1) integration program
shall comprise of the following:
1. IEC 61850 (Ed1) Client/OPC Server implementation in Connectivity Server
for connectivity between IEC 61850 (Ed1) compliant Protection and Control
IEDs and 800xA Aspect Servers.
2. IEC 61850 (Ed1) Communication Interface in AC 800M (through CI868
module).
3. Implementation of an IEC 61850 (Ed1) Configuration environment that works
in tandem with Control Builder.
Classification
The following is the classification of the workflow for IEC 61850 (Ed1) integration
in System 800xA:
1. Substation Engineering
– Exporting CI868 IED file from Control Builder
– Exporting other IED file using PCM600
– Creating SCD file using IEC 61850 (Ed1) engineering tools such as ABB
CCT600 and ABB IET600.
– Updating IED configuration with SCD file
– IED application logic building and CID file generation for ABB-IEDs
using PCM 600 or third party vendors having their own IED specific
device configuration tools.
– CI868 IED Engineering with Control Builder M
2. 800xA Engineering
– OPC Server configuration for MMS using the CET tool.
– Object type creation using the 800xA Uploader.
9ARD171384-600 17
Classification Section 1 Introduction
– CI868 IED for Horizontal Communication with GOOSE/MMS Client

functionality configured with Control Builder - IEC 61850 Wizard
– Select Before Operate (SBO) Application Engineering for MMS Control
using Control Builder Application Library Function Blocks.
This workflow is a combination of top-down and bottom-up approach. The above
steps can be separated according to the location and time, and can be executed in
parallel.
Figure 2 and Figure 3 shows an overview of a complete IEC 61850 Engineering
workflow.
I CD Fi l e for I HMI Subs ta ti on Automa ti on Engi ne e r i ng

IEC 61850 OPC Server
C:\Pr ogr amFi l es( x86) \ABB\61850
OPCSer ver
 OPC Ser ver wi th 1 sub networ k. i cd
 OPC Ser ver wi th 16 sub networ k.i cd
CI 8 6 8 I ED Engi ne e r i ng
Cont rol Builder
 Expor t CID /ICD Fi l e
 Confi gur e CI868 IED Templ ate + Impor t CID Fi l e Subst at ion Conf igurat ion Communicat ion Conf igurat ion
 Impor t CID Fi l e
 Substati on Str uctur e
I ED Appl i c a ti on Engi ne e r i ng  Data Set Confi gur ati on
 Si ngl e Li ne di agr am
 Assi gn LN to Conducti ve Equi pment
PCM 600  Stati on Confi gur ati on Di agr am
 RCB Confi gur ati on
Expor t IED Confi gur ati on  Feeder Bl ock Di agr am  GCB Confi gur ati on
Ex
po
rt
SC
D
Fil
e
Thi r d Par ty CID Fi l e, speci fi ed by

vendor s.
Figure 2. IEC 61850 Engineering Workflow - Step 1 & 2
18 9ARD171384-600
Section 1 Introduction Classification
Plant Explor er
 Upl oad SCD Fi l e for IEC 61850

Connect
 Contr ol & Functi onal Str uctur e
Cr eati on
CET for IEC 61850 OPC Ser ver
 Impor t SCD Fi l e
 Confi gur ati on
 IEC 61850 OPC Ser ver
 IEC 61850 Al ar ms & Events
Impor t SCD Fi l e +
Contr ol Builder for CI 868 IED
 Impor t SCD Fi l e
 Downl oad CI868 Confi gur ati on
i nto AC 800M Contr ol l er
PCM600 for ABB IEDs
 Downl oad Confi gur ati on to IED
Figure 3. IEC 61850 Engineering Workflow - Step 3
9ARD171384-600 19
Classification Section 1 Introduction
20 9ARD171384-600
Section 2 Substation Engineering
This section explains the simplified 800xA IEC 61850 (Ed1) Engineering Workflow
for substation automation based on bottom-up approach of substation engineering.
This workflow approach adapts CI868 as an IED and user can define the CI868 IED
by configuring associated LDs and LNs within Control Builder hardware tree
structure and export it as CID / ICD file.
The new workflow supports export of multiple CID / ICD files, one for each
configured CI868 IED and also supports import of one SCD file per CI868.
IEC 61850 (Ed1) Wizard handles one SCD file per CI868 board for a complete
configured substation, enabling the user to have flexible and distributed engineering
to work on different SCD files.
The process of workflow for substation engineering begins with the creation of CID
/ ICD file for CI868 in the Control Builder. The CI868 ICD file along with the ICD /
CID files of other IEDs and OPC Server are imported into IET600 / CCT 600 or any
other third party tool to perform communication engineering for GOOSE and MMS
mapping and generate a configured SCD file.
The configured SCD file is then imported into,
• Control Builder using IEC 61850 Wizard tool and downloaded to CI868 IEC
61850 communication interface (IED) controller after IO channel assignment
and application engineering.
• CET tool for configuring IEC 61850 (Ed1) OPC server Alarm and Events and
for vertical communication with IEDs.
• 800xA by Uploader to instantiate objects in 800xA Control Structure and
Functional Structure using the information from SCD file.
• PCM600 tool only for ABB IEDs or respective IED Engineering Tool for
downloading the configuration to the corresponding IED.
9ARD171384-600 21
Inputs Required Section 2 Substation Engineering
With the new Engineering Workflow, the use of IET-CCT tool is not required.
The following sub sections describes the steps to perform IEC 61850 (Ed1)
Engineering Workflow:
1. Configuring CI868 IED on page 32
2. Configuring other IEDs on page 57
3. Substation Communication Engineering in CCT600 / IET600 on page 83.
a. Communication Engineering using CCT600 on page 83.
b. Communication Engineering using IET600 on page 119.
4. Updating IED configuration with SCD file on page 160
Application Engineering of IED is not required if the IED is preconfigured from
the vendor as per requirement. IED CID file can be created from the
configuration present in IED.
5. CI868 IED Engineering with Control Builder M on page 168
6. IEC 61850 Connect Engineering on page 221
Inputs Required
This section describes the inputs required before starting 800xA IEC 61850 (Ed1)
Engineering.
Project Inputs
Following project inputs required Before starting 800xA IEC 61850 (Ed1)
Engineering:
1. Single Line Diagram.
2. Functionalities such as protection and control, and interlocking functions. The
functionality can be a device function number according to IEEE. The IEC
61850 (Ed1) offers the concept of logical nodes (LN) for formally defining
functions.
3. Constraints such as the existing network and the geographical situations onsite.
4. Preconfigured CID file for OPC server
22 9ARD171384-600
Section 2 Substation Engineering ABB Engineer or Project Inputs
5. Preconfigured IED files.

Obtain an IED preconfigured from a non ABB vendor according to the
requirement. In this case, IED vendor must deliver the preconfigured IED and
the corresponding CID file.
ABB Engineer or Project Inputs

Following ABB Engineer or project inputs required Before starting 800xA IEC
61850 (Ed1) Engineering
1. Naming of Substation, Voltage Levels, and Bays (Customer Designation).
2. Network topology which includes Sub Networks, OPC Servers, Switches, and
IP address preference according to the existing network.
3. Signal List for horizontal and vertical communication.
4. Alarms and Events - Details about the signals for which alarms and events
should be generated with a severity level.
5. Operator interfaces such as faceplates and trends.
Sample Inputs with Signal List

This section describes the sample inputs for starting the 800xA IEC 61850 (Ed1)
Engineering workflow.
9ARD171384-600 23
Sample Inputs with Signal List Section 2 Substation Engineering
Single Line Diagram

Figure 4 shows a Single Line Diagram used in this document. This SLD is a part of
large configuration. This figure displays a single Bay.
Bay B 1_MC 21_1

BB1_N110
I _ S LA 1
C B _ L5 R I _ S LB 1
MBI101
MBI102
TR 1 _ 1 1 0 3 3
I _ S LB 2
MP_107 M
B 1 _ L4
Figure 4. Single Line Diagram
24 9ARD171384-600
Section 2 Substation Engineering Sample Inputs with Signal List
Table 1 provides the description of SLD specified by the customer. It is assumed

that each equipment has functionality requirements. For example. Circuit Breaker
performs the function of over current tripping and Isolator performs no-current
switching operation.
Table 1. Sub Station Primary Equipment List
SLD of a Primary Equipment

SL.
Customer Designation Remarks
No.
1 B1_MC21_1 Bay 1 motor control area 21 sub area 1
2 BB1_N110 Bus bar sub area 1 North 110kV
3 I_SLA1 Main Isolator 1
4 I_SLB1 Primary Earthing Isolator 1
5 CB_L5R Circuit Breaker L5R
6 MBI101 CT - measurement sub area 1 Eqp 1
7 MBO102 PT - measurement sub area 1 Eqp 2
8 I_SLB2 Primary Earthing Isolator 2
9 TR1_11033 Transformer 1 110/33 kV
10 MP_107 Process Motor 07 sub area 1
11 B1_L4 Line 4 Bay1
Table 2 lists the customer identified IEDs to be used for this Bay.
Table 2. IED List (Secondary Equipment)
Sl.
IED Name IED Type Vendor Purpose Remark
No.
1 BC101(1) REC670 ABB Bay Protection and Control Preconfigured IED
9ARD171384-600 25
Table 2. IED List (Secondary Equipment) (Continued)
Sl.
IED Name IED Type Vendor Purpose Remark
No.
2 TC102(1) RET670 ABB Transformer Protection and Preconfigured IED
Control
3 PC103 CI868 ABB DCS command, control and CI868 as an IED
Report handling Type
(1) Typically the naming convention for IED Name in real time environment is, Substation>Voltage>Bay+ IED Name. In
this document, for illustration purpose, only the IED Name is used. For example: BC101(for REC_670 IED Type),
TC102 (for RET_670 IED Type).
An ABB Engineer designs the network topology as shown in Figure 5 after

discussing with the customer. The IP addresses and the switch is defined. A station
computer is set up as a HMI.
1 0 . 1 4 0 . 4 3. 1 1 0 OP C 1
1 0 . 1 4 0. 4 3 . 1 0
1 0 . 1 4 0. 4 3 . 5 1 10.140.43.52
P C103
B C1 0 1 TC 1 0 2
Figure 5. Network Topology
26 9ARD171384-600
Table 3 lists the GOOSE signals that are used for Interlocking and Protection.
Table 3. GOOSE Signal List
Sl.No. Signal From IED To IED

1 Switch I_SLA1 Position BC101 TC102, PC103
2 Switch I_SLB1 Position BC101 TC102, PC103
3 Switch I_SLB2 Position BC101 TC102, PC103
4 Circuit Breaker CB_L5R Position BC101 TC102, PC103
5 Transformer Tap Control Position TC102 PC103
6 Transformer Tap Control Command PC103 TC102
7 Load Shedding Command PC103 TC102
8 Active Power TC102 PC103
9 Local Remote Position TC102 PC103
Table 4 Lists the MMS Signals that are used for Control and Measurements.
Table 4. MMS Signal List
Sl No. Signal From IED To IED

1 Phase 1 Voltage BC101 PC103
4 Phase 1 Current BC101 PC103
7 Active Power BC101 PC103, TC102
8 Frequency BC101 PC103
9 Reactive Power BC101 PC103
9ARD171384-600 27
Table 4. MMS Signal List (Continued)
Sl No. Signal From IED To IED

10 Power Factor BC101 PC103
11 Switch I_SLA1 Position BC101 PC103
12 Switch I_SLA1 Command PC103 BC101
13 Switch I_SLB1 Position BC101 PC103
14 Switch I_SLB1 Command PC103 BC101
15 Switch I_SLB2 Position BC101 PC103
16 Switch I_SLB2 Command PC103 BC101
17 Circuit Breaker CB_L5R Position BC101 PC103
18 Circuit Breaker CB_L5R Command PC103 BC101
20 Transformer Voltage Control Position TC102 PC103
21 Directional Over Current Protection TC102 PC103
22 Rate of Change of Frequency TC102 PC103
23 Active Energy TC102 PC103
24 Reactive Energy TC102 PC103
25 No. of Operation TC102 PC103
26 Local / Remote TC102 PC103
27 Voltage TC102 PC103
28 Current TC102 PC103
29 Frequency TC102 PC103
28 9ARD171384-600
Table 5 Lists the MMS Signals with Alarm and Events.
Table 5. MMS Signal List with Alarm and Event
Sl. Process Object Process Object IED Alarm and

Signal Type Priority
No Name Description Name Event
1 Phase 1 Voltage VM-PA-BC101 Voltage Value BC101 Limit Alarm 310
from IED BC101 and Event
4 Phase 1 Current CM-PA-BC101 Current Value BC101 Limit Alarm 310
7 Active Power PM-PA-BC101 Active Power BC101 Limit Alarm 310
Value from IED and Event
BC101
8 Frequency FM-PA-BC101 Frequency Value BC101 Limit Alarm 310
9 Reactive Power RM-PA-BC101 Reactive Power BC101 Limit Alarm 310
BC101
10 Power Factor PFM-PA-BC101 Power factor BC101 Limit Alarm 310
BC101
11 Switch I_SLA1 SW-PA-P-SLA1 Position of Switch BC101 Alarm and 910
Position I_SLA1 Event
12 Switch I_SLA1 SW-PA-C-SLA1 Command of BC101 Event 510
Command Switch I_SLA1
9ARD171384-600 29
Table 5. MMS Signal List with Alarm and Event (Continued)

13 Switch I_SLB1 SW-PA-P-SLB1 Position of Switch BC101 Alarm and 910
Position I_SLB1 Event
14 Switch I_SLB1 SW-PA-C-SLB1 Command of BC101 Event 510
Command Switch I_SLB1
15 Switch I_SLB2 SW-PA-P-SLB2 Position of Switch BC101 Alarm and 910
Position I_SLB2 Event
16 Switch I_SLB2 SW-PA-C-SLB2 Command of BC101 Event 510
Command Switch I_SLB2
17 Circuit Breaker CB-PA-P-L5R Position of Circuit BC101 Alarm and 910
CB_L5R Position Breaker L5R Event
18 Circuit Breaker CB-PA-C-L5R Command of BC101 Event 510
CB_L5R Circuit Breaker
Command L5R
19 Transformer Tap TTP-PA-C-TR1 Tap control TC102 Event 410
Control Position Position of TR1
20 Transformer TVC-PA-C-TR1 Voltage control TC102 Event 410
Voltage Control Position of TR1
Position
21 Directional Over TDOC-PA-P-TR1 TR1 over current TC102 Alarm and 910
Current protection status Event
Protection
22 Rate of Change ROF-PA-P-TR1 TR1 ROF TC102 Alarm and 810
of Frequency protection status Event
23 Local / Remote CB-PA-C-L5R Command of BC101 Event 610
Switch I_SLB2
24 No. of Operations CB-PA-P-L5R Position of Circuit BC101 Limit Alarm 610
Breaker L5R and Event
30 9ARD171384-600
Section 2 Substation Engineering Tools Required
Table 5. MMS Signal List with Alarm and Event (Continued)

25 Active Energy CB-PA-P-L5R Position of Circuit BC101 Limit Alarm 910
26 Reactive Energy CB-PA-P-L5R Position of Circuit BC101 Limit Alarm 910
Tools Required
Following tools are required for 800xA IEC 61850 (Ed1) configuration and
planning:
• Control Builder M (Compact / Professional)
• ABB IET600 or ABB CCT600 Tool
• PCM600 for ABB IEDs
• CET for IEC 61850 OPC Server
• 800xA Uploader for SCD file upload
9ARD171384-600 31
Configuring CI868 IED Section 2 Substation Engineering
Configuring CI868 IED

Goal: Define CI868 as an IED
Input: Control Builder
Output: CID/ ICD file
Tools Used: IEC 61850 Wizard
Workflow:
Perform the following steps to create a project in Control Builder.
1. Open the Control Builder and create a new project. The New Project dialog
window appears.
Figure 6. Control Builder New Project
32 9ARD171384-600
Section 2 Substation Engineering Configuring CI868 IED
2. Enter the name of the project in the Name field and click Ok.
Figure 7. Control Builder New Project - Environment
The Control Builder project name is independent of any parameter such as CI868
IED or AC 800M IED description or Substation name in SCD file.
Figure 8. Control Builder New Project
9ARD171384-600 33
3. Expand Libraries and Insert CI868 HW Library under Hardware object.
Figure 9. Hardware - CI868 HW Library
34 9ARD171384-600
4. Right-click... and select Insert Unit from the context menu of 'Hardware
AC800M'. The Insert Unit appears.
Figure 10. Hardware AC800M - Insert Unit
9ARD171384-600 35
5. Select the Unit and select the CI868 position in Position option.
Figure 12 shows the CI868 object in the Control Builder tree structure after
insertion.
Figure 11. CI868 Unit
Figure 12. CI868 Tree View
36 9ARD171384-600
6. Double-click CI868 object in tree view to open the CI868 IED Editor and set
the communication parameters for the CI868 Access Point.
Figure 13. CI868 Setting Tab
9ARD171384-600 37
7. Right-click CI868 object and select Insert Unit from the context menu.
Figure 14. CI868 - Insert Unit
Renaming of CI868, MyIED, IED, LD and Send LN's objects are disabled.
38 9ARD171384-600
8. In the Insert Unit for CI868, select MyIED and click Insert.
Figure 15. CI868 - MyIED Update screen
The IED object displayed represents other IEDs in the SCD file. This must not be
selected, as it does not represent the CI868 IED. Only MyIED object must be
selected.
a. Double-click MyIED object to open the MyIED editor and configure
MyIED name in Settings Tab. Replace the default value (CI868IED).
Figure 16. MyIED - Settings
9ARD171384-600 39
By default the name is CI868IED. If MyIED Name is modified, it must be unique

(among CI868 modules within Control Builder project) and must not contain
space or other special characters ({, _ is allowed).
If the conditions are not met, during export, IEC 61850 wizard displays an error
message Configuration Incomplete and export operation is stopped.
9. Right-click MyIED object and click Insert Unit to open Insert Unit to
MyIED.
Figure 17. CI868 MyIED - Insert Unit
40 9ARD171384-600
10. Select Logical Device (LD) object and Click Insert.
Figure 18. Insert Unit for MyIED
The LD is inserted under MyIED.
Figure 19. CI868 - MyIED, LD
9ARD171384-600 41
11. Double-click LD object to configure LD name in the Settings Tab as shown in

Figure 20.
By default a blank field is displayed, replace this with a user defined name.
Figure 20. LD Settings
LD Name value must be unique (among LDs objects within CI868 object) and
must not contain space or other special characters ({, _ is allowed).
Wizard displays an error message Configuration invalid at LD node(s) and export
operation is stopped.
42 9ARD171384-600
12. Right-click LD object and select Insert Unit to open Insert Unit for LD.
Logical Nodes library with all supported LNs are listed as shown in Figure 22.
Figure 21. CI868 MyIED - LD, Insert Logical Nodes
9ARD171384-600 43
13. Insert the mandatory logical nodes LN0 followed by LPHD. Similarly insert
other required Logical Nodes under LD, by providing the position.
Figure 22. CI868 MyIED - LD, Insert Logical Nodes
It is mandatory to position the logical node LN0 first, then LPHD logical node
and followed by other required logical nodes in the Control Builder hardware tree
structure.
In case LN0 nodes is not positioned first, IEC61850 Wizard will automatically
position the LN0 node first.
In the IEC 61850 subnetwork, the logical node ITCI under CI868 represents and
activates CI868 as MMS Client.
44 9ARD171384-600
14. The selected LNs are listed in the Tree View as shown in Figure 23.
The configuration of CI868 is automatically stored as part of Control Builder
project.
Figure 23. CI868 MyIED - Logical Nodes
Logical Nodes QC1 ARCO and VC1 AVCO are newly introduced logical nodes
that are same as previously existing QC ARCO and VC AVCO, but contains
corrected names of Data Objects in IO channels as per IEC 61850 (Ed1)
specification 7-4 for AVCO and ARCO.
9ARD171384-600 45
15. Double-click LN object to configure LN name in the Settings Tab.
Figure 24. LN Settings
By default the LN name field is blank. The LN name field must be configured
with an appropriate name, else an error message is displayed during export of
CID file. Following parameters must be considered while configuring the LN
Name:
• LN name field cannot be blank.
• LN name must not contain special or space character ({, _ is allowed).
• For LN0, the LN name must be LLN0.
• For LPHD and ITCI, the LN name must be LPHD<Instance Num> and
ITCI<Instance Num>, where Num can range from 1 to 253.
• The naming of other LNs must be in the following format:
<LN Prefix><LN Class Name><LN Instance Num>
For example: <LS><GAPC><1>. The LN instance Num should be within the
range of 1 to 253.
• The LN name must be unique within an LD.
This completes the configuration of CI868 module in Control Builder.
If required, repeat Step 6 through Step 15 to configure multiple CI868 Access
Points (Maximum of 12 CI868 are allowed per AC 800M / Redundant
Controller).
46 9ARD171384-600
Section 2 Substation Engineering CI868 CID File Export using IEC 61850 Wizard
CI868 CID File Export using IEC 61850 Wizard

Perform the following steps to generate and export CID file using IEC 61850
Wizard.
1. Right-click CI868 object and select IEC 61850 Wizard from the context menu
to open the IEC 61850 Wizard window as shown in Figure 26.
Figure 25. IEC 61850 Wizard
9ARD171384-600 47
CI868 CID File Export using IEC 61850 Wizard Section 2 Substation Engineering
2. Select ICD/CID Export tab.
Figure 26. IEC 61850 Wizard - Export
To view all the messages generated by IEC 61850 Wizard, right-click IEC
61850 Wizard and select View Log. List of all logs generated during export is
displayed in the IEC 61850 Wizard Window.
The logs can also be viewed by opening the IEC 61850ImportWizard.log located
in installed folder.
For Compact Control Builder: C:\ABB Industrial IT Data\Engineer IT
Data\Compact Control Builder AC 800M\LogFiles\Importwizard.log.
For Control Builder Professional: C:\ABB Industrial IT Data\Engineer IT Data\
Control Builder M Professional\LogFiles\Importwizard.log.
3. In the File Path, click Browse to locate the destination folder for CID file.
48 9ARD171384-600
4. Save the CID file to the specified location.
Figure 27. IEC 61850 Wizard - CID File Save
CID file name is generated in the following format. User can modify the file if
required.
CI868_n_IEDName_TimeStamp.cid
– n is the instance of CI868 where the IEC wizard is invoked.
– IEDName is read from MyIED name parameter of MyIED hardware unit
in Control Builder.
– TimeStamp is the system date and time. The timestamp will be in the
DD-MM-YYYY HH-MM-SS format.
9ARD171384-600 49
5. To save the file, click Export.
Figure 28. IEC 61850 Wizard - Export CID file
The File Revision and Version settings are generated while exporting the CID
file. These values can be edited or updated every time the CID file is exported
from Control Builder, with a new version and revision.
While exporting as CID file, IEC61850 Wizard checks for the last imported SCD
file to retain the configured Data Sets and GCBs. For more information on
retaining the Data Sets and GCBs, refer to Retaining Data Set and GCBs in
Configured CID File on page 53.
50 9ARD171384-600
6. Click OK to confirm the specified location of the exported CID file.

This completes the generation of CI868 CID file in the Control Builder.
Figure 29. CI868 - CID File Export
The CID file contains Header, Communication, IED and Data Type Templates
sections based on CI868 configuration from Control Builder. Figure 30 is an
example of a generated CI868 CID file.
9ARD171384-600 51
Figure 30. Sample CI868 CID File
The generated CID file is further used in CCT or other IEC 61850 engineering tools
for substation communication configuration to perform signal configuration.
52 9ARD171384-600
Retaining Data Set and GCBs in Configured CID File

When the CI868 configuration is exported as CID file, IEC 61850 Wizard checks
from any previously imported SCD file and retains the configured CI868 Data Sets
and GOOSE Control Blocks.
During the CID file export, IEC61850 Wizard validates the Control Builder CI868
Configuration with the previously imported SCD file stored in the project folder for
the following:
– Checks if the CI868 position in Control Builder is same as the Access
Point name under CI868 or AC 800M IED.
– Checks if LD name configuration in Control Builder is present under this
Access Point.
– Checks if LN0 is present under that LD.
– Checks if Data Sets and GSE Control block is present.
If the conditions are met, the configured DataSets signals and GSE Control blocks
are retained in the exported CID file. If anyone of the conditions are not met, a
default DataSet and GCB for the CID file is generated.
Before exporting the CID file, if user has modified the name of any LN or deleted
any LN under corresponding LD, DataSets retained for that particular LD will not
detect the modifications, and will contain the contents of DataSets as per the
configured SCD file.
The signals of the default dataset that are not matching with the LNs of CI868 are
filtered out in CCT tool during signal configuration.
The client mapping of CI868 IED dataset is not retained in the configured CI868
CID file that is imported into CCT tool. To retain the client mapping, manually
drag and drop the required IED to GCB of CI868 IED, as client.
When exporting CI868 configuration into existing CCT600 project already
containing the CI868 module with the same name, it is recommended to export
the CI868 configuration as CID file to retain previously configured datasets in
CI868. Incase of exporting the ICD file the Data Set informations are not retained
9ARD171384-600 53
CI868 ICD File Export using IEC 61850 Wizard Section 2 Substation Engineering
CI868 ICD File Export using IEC 61850 Wizard

The CI868 can alternatively be configured and exported as ICD file that is used as a
template for CI868 ICD in CCT600 or equivalent tools. Thereby the same ICD file
can be imported multiple times with different CI868 IED name to represent multiple
CI868 IEDs in the substation.
Each imported CI868 instance is configured for Subnetwork, CI868 name,
Communication Parameter, LD, and LN objects as required in CCT600 or IET600
tool.
While configuring CI868 in Control Builder for exporting as ICD file, typically all
required LN types and qualities foreseen for all CI868 IEDs in substation is
included. Further the configuration parameters of CI868, MyIED, LD, LN their
objects is not configured as the same is set individually in CCT600 or IET600 for
each CI868. Generate the ICD file by selecting .icd in save as option as shown in
Figure 31.
Figure 31. IEC 61850 Wizard - ICD File Save
54 9ARD171384-600
Section 2 Substation Engineering CI868 ICD File Export using IEC 61850 Wizard
The following are typical steps to generate ICD file.

1. Create a new Control Builder Project.
2. Insert a compatible CI868 HW Library.
3. Insert one CI868 Hardware unit and provide the CI868 position, under
Hardware AC800M object.
4. Insert the MyIED hardware unit from CI868 hardware unit and configure
generic MyIED name in Settings Tab.
5. Insert LD hardware unit from MyIED hardware unit and configure generic LD
name. Insert multiple number of LDs for maximum LDs foreseen for CI868 in
substation.
6. Insert the mandatory logical nodes LN0 followed by LPHD under LD
hardware unit. Similarly insert other required Logical Nodes, by providing the
position. Insert multiple number of LNs for maximum LNs foreseen for CI868
in substation.
7. Open the IEC61850 Wizard from CI868 hardware unit context menu.
8. Select ICD / CID Export tab and click Browse.
9. Select the path to save as ICD file and click Export.
This completes the ICD file generation. This file can be used as CI868 template for
further engineering in CCT or other IEC 61850 substation communication
configuration tools to perform signal configuration.
The ICD file contains Header, Communication, IED and Data Type Templates
sections based on CI868 configuration from Control Builder as shown in Figure 32.
9ARD171384-600 55
CI868 ICD File Export using IEC 61850 Wizard Section 2 Substation Engineering
Figure 32. Sample CI868 ICD File
56 9ARD171384-600
Section 2 Substation Engineering Configuring other IEDs
Configuring other IEDs

This section explains the general handling of IED’s CID files with IED Device
Configuration tools. The IED Device Configuration tool used for configuring ABB
IEDs in this example is, ABB PCM 600 Device Configuration Tool.
ABB PCM 600 Device Configuration Tool does not support configuring of other
third party IEDs. For configuring third party IEDs, refer their own IED specific
device configuration tools.
Goal:
To create the project tree structure in PCM 600 and to fetch the CID files from the
preconfigured IEDs if they are not available. IED is supplied and preprogrammed.
The CID files are not supplied. There is no requirement to create a PCM tree
structure if the CID files are supplied corresponding to the application logic in the
IED. The user can proceed to the next step of Communication Engineering in CCT.
Inputs:
Preconfigured IED is online to upload the application logic. If the physical IED is
not available, then the application logic is ready to be imported to the IED tool.
Outputs:
PCM 600 project structure is ready and CID files are created.
Tools used:
ABB PCM 600 as IED Device Configuration Tool for ABB-IEDs.
Prerequisite:
All the required Connectivity packages for ABB IEDs are installed and added in
Connectivity package manager. For more information, refer to the PCM 600
documents and respective connectivity packages.
Perform the following steps to generate the CID file for an IED:
1. Double-click icon on the desktop to open PCM 600 tool.
9ARD171384-600 57
Configuring other IEDs Section 2 Substation Engineering
The welcome screen appears as shown in Figure 33.
Figure 33. PCM 600 Version Details
2. In the PCM 600 dialog box, select File > Open/Manage Project to create a
new project.
Figure 34. New PCM600 Project
58 9ARD171384-600
3. In the Open/Manage Project dialog box, select New Project.
Figure 35. Open/Manage Project Dialog Box
4. In the New Project dialog box, enter the project name.

OntarioHydro is used a sample project name.
Figure 36. Example of PCM600 Project Name
9ARD171384-600 59
5. Select the project and click Open Project to open the project tree structure in
PCM 600.
Figure 37. PCM600 Project List
6. Create the project tree structure in the PCM 600 window.

7. Right-click the root and select New > General > Substation to create a new
substation.
Figure 38. Creation of Substation in PCM 600
60 9ARD171384-600
8. Right-click the substation and select Rename to rename the substation as

defined in CCT. In this example, rename it as AA1.
Figure 39. Rename the Substation
9. Right-click the substation and select New > General > Voltage Level to create
a new voltage level under substation.
Figure 40. Creation of New Voltage Level in PCM 600
10. Right-click the voltage level and select Properties.
9ARD171384-600 61
11. In the Object Properties dialog box, select the actual voltage level value
available in CCT from the VoltageRange drop-down list. In this example,
select 110-220 kV.
Figure 41. Selection of Actual Voltage Level
12. Right-click the voltage level and select New > General > Bay to create a new
Bay.
Figure 42. Creation of New Bay in PCM 600
62 9ARD171384-600
13. Right-click the bay level and select New > Transmission IED > REC 670 IEC
to create a new IED under the bay level.
In this example, the first IED is REC 670 IEC and the second IED is RET 670
IEC.
Figure 43. Creation of New IED in PCM 600
The context menu shows the available 670 series IEDs to be inserted, on the bay
level in the Plant Structure, according to the installed connectivity package.
The technical key in the physical IED and IED object in PCM600 must be the
same for communication between the IED and PCM600, otherwise it is not
possible to download a configuration.
Each IED in a PCM600 project must have a unique technical key. Therefore, it
is not possible to set the same technical key for several IEDs in the same
PCM600 project.
The IED is delivered with a factory default technical key. The validation of the
technical keys between PCM600 and the IED does not occur if the IED contains
the factory default technical key.
9ARD171384-600 63
The technical key property in PCM600 corresponds to the IED name attribute in
SCL files. Avoid changing the IED name attribute outside PCM600, because data
in PCM600 may get lost when importing the SCL files.
The technical key can be read from the IED and updated to PCM600, or the
PCM600 technical key can be written to the IED. Alternatively, a user-defined
technical key can be defined.
When writing a configuration to the IED, PCM600 checks for a mismatch
between the IED object and the physical IED technical key and appropriate
message is displayed.
Ensure that the IED object in PCM600 has the same IP address as the physical
IED that is intended to be connected through the technical key concept.
The technical key for an IED object can be changed in the Object Properties
dialog box in PCM600.
14. In Configuration Mode, select the mode of IED configuration. IED
Configuration can be done in two ways.
– Online Configuration
– Offline Configuration.
64 9ARD171384-600
Figure 44. Configuration Mode
15. Online IED Configuration Mode

During online mode configuration, PCM600 reads the configuration directly
from the physical IED. This is useful when an order specific IED is used. The
order configuration is written to the IED at the factory and can be accessed by
PCM600. The housing type, the used overlay version for local HMI, and the IO
boards included in the IED will be read from the IED directly.
9ARD171384-600 65
a. Select the IED Communication protocol.
Figure 45. Communication protocol selection wizard
66 9ARD171384-600
b. Select the Port and enter the correct IP address of the physical IED to be
configured.
Figure 46. Communication port and IP address
9ARD171384-600 67
c. Click Scan to scan/read the IED Type and IED Version for the IED that is
online.
The user cannot scan data from the IED or proceed further if the IED is not online
or if the IP address is not correct.
Figure 47. IED Version detection
68 9ARD171384-600
d. Click Next to open the Housing Selection Page and select the Housing
and Display type of the IED.
Figure 48. IED housing and display type detection
e. The Setup Complete Page dialog shows the summary of the IED Type,
IED Version, IP Address of IED and Order Number. Click Finish to
complete the online IED configuration.
9ARD171384-600 69
Figure 49. IED Setup completion wizard
After completing online configuration, read the configuration from the IED to
ensure that the IED object in PCM600 has the same configuration data as the
physical IED.
70 9ARD171384-600
16. Offline IED Configuration Mode

When the physical IED is not available or not connected to PCM600 the
engineering steps are done without any synchronization with the IED. The
offline configuration in PCM600 can be synchronized with the physical IED at
a later state by connecting the IED to PCM600.
a. Select Offline Configuration mode in the Configuration Mode
Selection page and click Next.
Figure 50. Configuration Mode
9ARD171384-600 71
b. In IED protocol, select IEC 61850 and click Next.
Figure 51. Communication Protocol
c. Enter the IP address and click Next.
Figure 52. IEC 61850 Communication Protocol
72 9ARD171384-600
Verify that PCM600 tool detects the IP address entered for the IED in the project
tree structure.
d. Click Next.
Figure 53. Configuration Complete
9ARD171384-600 73
e. Select the Product Version and click Next.
Figure 54. Version selection
f. Browse and select the Order Specific File and click Next.
Figure 55. Order Option Browser
74 9ARD171384-600
If the order specific file is not available, select the No Order Specific File check
box and proceed to the next wizard. The order code can be configured later when
the IED is online.
g. Click Next.
Figure 56. Housing/Display Selection
In case of customer specific IEDs, select the corresponding housing type series.
9ARD171384-600 75
h. Click Finish to complete the configuration for the selected IED.
Figure 57. Setup Complete
17. The following page appears after completing the selected IED configuration.
Figure 58. PCM IED Structure
The configuration for IED is complete.

18. Repeat the Step 1 to Step 16 for configuring other IEDs and to have the PCM
600 project ready.
76 9ARD171384-600
19. In IED application, create GOOSE data receiver channel. Right-click the IED
level and select Application Configuration from the context menu to open the
Application Configuration page.
Figure 59. IED Application Configuration
9ARD171384-600 77
20. The Application Configuration window for the selected IED opens. Create an
Application logic.
Figure 60. Application Configuration
The meaning of this application is that this IED receives GOOSE data on
channels 'GooseData1' to 'GooseData4'. This block converts first channel data
into its quality and value. Signal 1 value appears at 'OUT1VAL' while its
quality appears at 'OUT1'. These signals are sent to the Binary output module
of IED.
78 9ARD171384-600
Perform the application logic for other tabs and save the work.
For more details on configuring application logic, refer to the respective PCM
600 IED Manual.
9ARD171384-600 79
21. Right-click the IED and select Export to export the CID file.
Figure 61. Option to Export CID File
22. In the Export dialog box, browse the path to export the CID file and select
Configured IED Description (*.cid) from the Save as type drop-down list.
80 9ARD171384-600
Figure 62. Location to Save CID File
It is recommended to name the CID file according to the syntax, IED-

Type_ApplicationName.cid
For example, REC670_ControlA1.cid.
Create new folders for storing different versions of CID files.
23. Click Save.
Figure 63. CID File Naming Convention
9ARD171384-600 81
24. Clear the selection of Export Private Sections check box and click Export.
The CID file is generated for the selected IED.
Figure 64. SCL Export Options
25. Repeat the Step 19 to Step 23 for all other IEDs.

This completes the CID file generation of other IEDs and creation of PCM 600
project tree structure.
For third party IEDs other than ABB types, use IED tools from respective the
vendors to generate CID files.
82 9ARD171384-600
Section 2 Substation Engineering Substation Communication Engineering in CCT600 / IET600
Substation Communication Engineering in CCT600 /

IET600
This section describes the steps for performing IEC 61850 Communication
Engineering in CCT600 and IET600 for generating a fully configured SCD file.
The SCD files is generated using.
• Communication Engineering using CCT600
• Communication Engineering using IET600
Communication Engineering using CCT600

Communication Configuration Tool (CCT) is used to create Substation section and
perform communication engineering tasks (Datasets, GCB, and RCB), assign LNs
to Primary Equipment and Bay. Following tasks are performed in CCT to generate
final SCD file.
• Assign IED LNs to Bay Equipment
• Assign LNs to Primary Equipment
• Configuring Vertical Communication for MMS Protocol
• Configuring Horizontal Communication for GOOSE Protocol
Goal:
To create Substation section and perform communication engineering tasks
(Datasets, GCB, and RCB), assign LNs to Primary Equipment and Bay, and
generate final SCD file.
Inputs:
CID files of CI868 and other IEDs.
Output:
SCD file.
Tools used:
CCT600.
Workflow:
9ARD171384-600 83
Communication Engineering using CCT600 Section 2 Substation Engineering
Perform the following steps:

1. Double-click to open the CCT.
Figure 65. CCT Project Navigator
2. To create a new project, select File > Create new project.
Figure 66. CCT New Project
84 9ARD171384-600
Section 2 Substation Engineering Communication Engineering using CCT600
3. Enter a Project Name and the Project Path and click Ok.
Figure 67. CCT New Project
Project tree Structure is created with Substation, Communication and IED

Section along with Data Type templates.
Figure 68. CCT Project Tree
9ARD171384-600 85
4. In Substation Section,
to create Voltage Level, right-click substation name and select create new
Voltage Level from the option menu.
The substation, Voltage, and Bay name must match with the project tree structure
created in PCM.
Figure 69. Substation Voltage Level
86 9ARD171384-600
a. To create a Bay, right-click Voltage Level and select Create new Bay
from the context menu.
Figure 70. Voltage Level - Bay
9ARD171384-600 87
b. To create a Conducting Equipment, right-click Bay and select Create new

Conducting Equipment from the context menu.
Figure 71. Bay Level - Conducting Equipment
5. In Communication Section,
a. To create a Bus, right-click Communication Section and select Create
new Bus from the context menu.
88 9ARD171384-600
Figure 72. Communication Section - Create Bus
Bus name can be customized as per project requirements.
6. To import ICD file(s), right-click IED Section and select Import ICD File(s)
from the context menu.
Figure 73. IED Section - Import ICD File
9ARD171384-600 89
7. In the Import ICD Files(s) dialog box, click Add File to browse the CID file.
Figure 74. Browse CID file
8. In the Browse window, select the required CID / ICD file(s) of CI868 and other
IEDs to display in the list.
The Customer Name of other IEDs in CCT should be modified, as entered in the
Caption Field in PCM as shown in Figure 75.
90 9ARD171384-600
Figure 75. Other IED Name Modify
9. Import IEC 61850 OPC Server ICD file. Use one or more of the following
OPC Server ICD file variants available with 800xA IEC 61850 Connect
package.
– OPC Server with 1 sub network.icd
– OPC Server with 16 sub network.icd
IEC 61850 OPC Server ICD file can be configured in CCT, only if the IEC 61850
Connect is installed in 800xA System.
By default the IEC 61850 OPC Server ICD file is located in C:\Program
Files(x86)\ABB\61850 OPC Server, with the default name and it can be renamed
as required.
9ARD171384-600 91
10. Select the Import check box of respective IEDs and click Import All Files.
Figure 76. Import CID File
IED name can be modified if necessary in the IED Name in CCT column.
Incase of importing same ICD file as template for multiple IED instances, it is
required to use IED Name in CCT option to configure individual IED names.
When AC 800M with multiple access points are imported into CCT600 as
individual configured CID files, it is recommended to modify the individual IED
names with CI868 Access Point name in IED name in CCT column, otherwise
the AC 800M access point is overwritten. After importing the CID files, retain the
client mapping as mentioned in Retaining Data Set and GCBs in Configured CID
File on page 53.
11. Modify the OPC Server name in the IED Name in CCT column.
Modification of OPC Server name is necessary as the OPC Server ICD file
contains default name.
Incase of importing same OPC Server ICD file as template for multiple OPC
Server instances, it is required to use IED Name in CCT option.
92 9ARD171384-600
12. The messages shown in Figure 77 is displayed after a successful import.

Figure 78 shows the CCT project tree structure after importing all the files.
Figure 77. Successful Import Indication Message
Figure 78. CCT Project Tree View
9ARD171384-600 93
13. Assign the IP address for IEDs, if correct IP address is not configured in
imported CID file.
Figure 79. IED IP Address
94 9ARD171384-600
14. Assign the IEDs to the respective IEC 61850 bus.
Figure 80. IED Subnetwork
9ARD171384-600 95
Assigning IED LNs to Bay Equipment

1. In CCT, map the required LDs and LNs of IEDs to Bay and Conducting
Equipment.
This step is applicable to display the process objects in Functional Structure of
800xA System.
The LDs and LNs are defined only for CI868 IED while configuring in Control
Builder. LDs and LNs for other IEDs are defined when the CID file is imported.
The Bay must contain information about the LDs and LNs after importing CID
files for CI868 and other IEDs and populating in the CCT database.
a. On the right pane of CCT, select IEC 61850 Object Mapping tab in the
IEC 61850 Data Engineering tab.
b. Expand Substation Section and select the Bay level.
c. On the left pane, select the LD0 of the corresponding IED.
d. Drag and drop LD0 to the Bay.
Perform step c and step d for other LDs of the IED as required.
It is recommended to drag and drop only the required LNs to the Conducting
Equipment. Assigning all LDs and LNs to the Bay is optional.
96 9ARD171384-600
The LDs and LNs are assigned to the Bay.
Figure 81. Drag and Drop LDs to Bay
Assign LNs to Primary Equipment

Perform the following steps for assigning the LNs to primary equipment:
1. Assign LNs to the primary equipment by mapping the functionality. The user
might require the default functionality provided by the equipment as input.
Table 6 provides a list of primary equipment name along with the customer
designation along with the corresponding LNs.
Table 6. Assigning LNs to the Primary Equipment
Sl.No. Primary Equipment Name Customer Designation Functionality/ LNs

1 VL1Bay1PTR1 TR1-11033 PTRC, PTOC
2 TransformerWinding1(PTW) TR1-11033 PTRC, PTOC
3 QA1 (CBR) CB_L5R XCBR, CSWI, CILO
4 QA2 (DIS) I_SLA1 CSWI, XSWI
9ARD171384-600 97
Table 6. Assigning LNs to the Primary Equipment (Continued)
5 VTR1(VTR) MBI102 MMXU

6 CTR1(CTR) MBI101 MMXU
2. Drag and drop LNs to the Primary Conducting Equipment.
Figure 82. Drag and Drop LN on Primary Equipment
98 9ARD171384-600
3. Repeat the Step 1 and Step 2 for other Primary Equipment according to Table 6
and save the changes.
Figure 83. Assign LNs to Primary equipment
Configuring Vertical Communication for MMS Protocol

Perform the following steps to perform vertical communication for MMS protocol:
1. To perform the signal engineering, first perform MMS data engineering for
vertical communication. 4
2. Take a printed copy of the signal list. These signals should be part of the
dataset.
Signal Engineering is done in CCT using the following feature:
• Datasets: Each dataset is a grouped number of signals defined as IED
interface for communication.
• Report Control Blocks (RCB): RCBs are selected dataset for vertical
communication as MMS Server with MMS Clients such as OPC server and
IED-CI868.
• GOOSE Control Blocks (GCB): GCBs are selected dataset for horizontal
fast IED to IED communication as Multicast.
9ARD171384-600 99
3. By default, the IED tools generate CID files which have predefined datasets.
Figure 84 shows the dataset and RCB defined for IED already.
Create all the signal engineering for an IED under LD0.LLN0. Keep LD0.LLN0
selected to view all the data engineering fields as shown in Figure 84.
Figure 84. Default datasets and RCB
100 9ARD171384-600
4. Select LD0.LLN0 for an IED and on the right pane select IEC 61850 Data
Engineering tab and then select the Data Set Engineering tab.
Figure 85. Datasets and Entries
5. On the Data Sets panel, click Add, a new dataset named new_ds is created. If
required rename it.
Figure 86. New Data Set Creation
9ARD171384-600 101
6. Navigate to the desired signal in the IED data Model panel and click Add.
For example, if the Circuit breaker CB_L5R position must be sent through
MMS from the signal list, then add this signal in the dataset.
Figure 87. Data Set - Data Object Level
The signal is added in the Data Set Entries panel.

For RCB Data Set, the signals must be assigned at Data Object (DO) level that
includes the attributes of the DO (Signal, Quality (t), and Time (t)).
For example: Pos, EnaOpn, EnaCls
It is recommended Not to configure RCB datasets containing Data Objects of
Functional Constraint type CO as it is used for Control purpose.
102 9ARD171384-600
Following rules apply when using Default Datasets for MMS:

- Only the LNs specified under IEC 61850 (Ed1) specification7-4 are
supported.
- All Mandatory and Optional Data Objects are available in default dataset for
supported LNs. However DO must be of supported CDC types (SPS, DPS,
INS, ACT, ACD, MV, CMV, SAV, WYE, DEL, SEQ, SPC, DPC, INC, BSC,
ISC, and APC.).
- Under Data Objects, only mandatory Data Attributes are available.
If the above criteria are not met when the default datasets are used for RCB
client, SCD file import is cancelled. The IEC 61850 wizard tool does not
import DO with unsupported CDC types and LNs.
Figure 88. Data Set Entries List - Data Object Level
9ARD171384-600 103
Figure 89. Data Set - Data Attribute Level
Figure 90. Data Set Entries - Data Attribute Level
104 9ARD171384-600
For GCB Data Set, the signals must be assigned at Data Attribute (DA) level.
Ensure that for each configured GCB Data Set, Quality (q), Time (t), and Signal
Attribute is available. Time attribute is optional for GOOSE signals.
For example: stVal, ctlModel, q
SCD file import is cancelled, if the configured SCD file does not contain Signal
Attribute.
It is recommended Not to configure RCB datasets containing Data Attributes of
Functional Constraint type CO as it is used for Control purpose
It is recommended to have a maximum of 10 data objects per GCB dataset. Use
additional datasets to add more than 10 data objects.
7. Similarly, add other signals in the signal list for this IED. Dataset is defined and
save the settings.
For GCB Datasets signals sending to and from CI868, include the signals
mentioned in Table 3.
For RCB Datasets to CI868, include signals as mentioned in Table 4.
8. Define Report Control Block for this dataset. Select the Report Control
Engineering tab and click Report Control.
Figure 91. Report Control Engineering Tab
9ARD171384-600 105
9. Entry for a new RCB is created. Rename new_rcb suitably.
Figure 92. Creation of New RCB
10. Select the dataset.
Figure 93. Select Dataset Option
The datset column can also have configured RCB datasets that have Data objects
of LLN0 and LPHD logical nodes sending data from other IEDs to CI868
module.
11. The check boxes selected by default in Figure 94 indicate the following:
– Selected dataset will be buffered for 500 ms.
– 5 MMS clients can access this data simultaneously.
– Data is reported if there is a data update or quality update.
106 9ARD171384-600
For more details, refer to the CCT manual.
Figure 94. RCB properties
RCB for the selected IED is defined. Save the work.

12. Repeat Step 1 to Step 10 for defining the RCBs for other IEDs.
The process of manually generating datasets and RCB can be prompted to errors.
To overcome this, CCT provides a feature to automatically generate the datasets
and RCB based on a set of rules.
Configuring Horizontal Communication for GOOSE Protocol

Perform GOOSE data engineering based on the example of CI868 IED shown in
Table 3.
1. Navigate to CI868 IEDs LD0.LLN0 and create a new dataset as explained in
Step 4 through Step 6 in Configuring Vertical Communication for MMS
Protocol on page 99. After adding the signals, the data appears as shown in
9ARD171384-600 107
Figure 95.
Figure 95. Data Set Entries - Data Attribute Level
2. Save the work in CCT.

3. Select the GOOSE Control Engineering tab.
Figure 96. GOOSE Control Engineering Tab
108 9ARD171384-600
4. Click GSE Control.
Figure 97. GSE Control Button
5. A new entry is created for GCB to be defined. Rename if required.

6. Select the dataset.
Figure 98. Dataset Selection
7. Save the work in CCT.

8. Click Address Definition.
Figure 99. Create New Address Definition Button
9ARD171384-600 109
9. Address Definition Field is created. Click the button in MAC Address.
Figure 100. GCB MAC Address Definition Field
10. In IEC 61850 GSE Applications dialog box, select GSE Application from the
list and click Select.
Figure 101. IEC 61850 GSE Applications Dialog Box
110 9ARD171384-600
Table 7 explains about each field in the Address Definition table.
Table 7. Address Definition table
Field Label Description

Description Can be left blank.
MinTime Minimum time indicates the minimum response time in
milliseconds for data change. This time can be used by the
receiver to discard the old messages. By default, keep this
value to 10 milliseconds.
MaxTime Maximum time indicates the background "heartbeat" cycle
time in milliseconds. The default value is 10000 ms. If there
are no data changes, IED still resends the message with a
heartbeat cycle.
MAC Address MAC Address is the Multicast MAC address to which the
specific GOOSE data is sent. The receiving IED filters the
frames and starts to process them if the specific multicast
address is defined in configuration. It is recommended to
have one unique multicast address per GoCB. Although
there is no limitation on this, it is recommended to set the
usable range as 01-0C-CD-01-00-00 to 01-0C-CD-01-01-FF.
ApplicationId Unique Id for the sending GoCB within the system. It
identifies the purpose of this particular dataset. Range is
0x0000 to 0x3FFF. Ensure that all the four digits are entered
while defining ApplicationId.
VLAN-ID and Used in the network supporting Virtual LANs. The priority is
VLAN-PRIORITY used with network switches. The default value for GOOSE is
4 and range is from 0 to 7. The default VLAN Identifier is 0
and its range is 0x000 to 0xFFF. Ensure that all the three
digits are entered while defining the VLAN-ID.
9ARD171384-600 111
Figure 102. GCB Definition
The appID field must not be left empty in the GOOSE Control Block Definition
even if the 3rd party IEDs are present in the configuration.
11. Define the IED to act as the receiver of the above GOOSE message. According
to the signal list, this message is relevant to IED AA1E1Q01_BC101. Drag and
drop AA1CI868IED_PC103 into the name field of the GOOSE control block.
Figure 103. GOOSE Client
112 9ARD171384-600
Figure 104 shows the result of this process.
Figure 104. GCB Definition for CI868
One GOOSE message is defined. Save the work.
9ARD171384-600 113
12. Repeat Step 1 to Step 11 for configuring other IEDs according to the signal list.
See another example shown in Figure 105.
Figure 105. GCB Definition for IED670
GCB datasets can be automated using the procedure defined above for RCB. For
more details refer to CCT Manual.
13. Update the Dataflow. This step identifies the IED from which the GOOSE
receives the inputs. Each RCB present in the configuration, sets IEC 61850
OPC Server / ITCI from CI868 as a client.
Figure 106. Update dataflow option
114 9ARD171384-600
14. After successful update data flow, the tree structure appears as shown in
Figure 107.
Figure 107. GOOSE Input Section in CCT
15. Each RCB gets,

– IEC 61850 OPC Server as client, shown in Figure 108.
Figure 108. OPC Client in CCT
9ARD171384-600 115
– ITCI from CI868 as an MMS client node, shown in Figure 109.
Figure 109. CI868 Client in CCT
16. To manually add an MMS client:

a. Select Tools > Options > Environment > Execution Mode and change
the user role to Expert.
Figure 110. CCT User Role Option
116 9ARD171384-600
b. Go to properties of the IED that needs to be configured for RCB client

manually. Under Data flow generation option set update Report Client
Mapping as False.
If update Report Client Mapping is not set to false, during update data flow
process the report clients are automatically associated with the RCBs for the
corresponding IED.
Figure 111. Update Report Client Mapping
9ARD171384-600 117
Save the configuration.
Figure 112. SAVE CCT Configuration
17. Export all the updates to an SCD file.
Figure 113. Export SCL File Option in CCT
18. In the FormSclExportDialog dialog box,

select the Suppress Private CCT Type Information check box and browse
the path to store SCD file. Click Export.
Figure 114. Select Path to Export SCD file
19. Click Export to export the SCD file.

This completes the creation of a fully configured SCD file.
118 9ARD171384-600
Section 2 Substation Engineering Communication Engineering using IET600
Communication Engineering using IET600

ABB Integrated Engineering Toolbox (IET600) is a system engineering tool for IEC
61850 (Ed1) based communication networks and Substation Automation (SA).
IET600 enables a simplified, consistent and flexible approach to SA Engineering
and contains various modules to complete the system engineering of an IEC 61850
(Ed1) based substation, including:
• configuration of the communication network
• configuration of the IEC 61850 (Ed1) dataflow
• import and export of IEC 61850 SCL data for exchange with other tools
Goal:
To perform communication engineering tasks (Datasets, GCB, and RCB), assign
LNs to Primary Equipment and Bay, and generate final SCD file.
Inputs:
Inputs as defined in Inputs Required on page 22.
Output:
SCD file.
Tools used:
IET600, PCM 600, ABB IEDs and other third party IEDs.
Workflow:
The following subsections describes the workflow doe generating the SCD file:
9ARD171384-600 119
Communication Engineering using IET600 Section 2 Substation Engineering
Creating a New Project

Perform the following steps to create a new project.
Screen shot in this manual are used for illustration purpose only, the version
number varies according to the latest software version packaged with the
software.
1. Click to open the Project window and select Manage Projects.
Figure 115. New Project
120 9ARD171384-600
2. The Projects window provides access to the projects stored in your computer
and enables the addition and removal of projects.
Figure 116. Project List
3. Click New, to create a new Project and enter the name and directory.
The project files are then stored into specified path. The default location of the
IET600 project file is located under C:\Data\IETProjects.
The engineering process for an IEC 61850 (Ed1) based substation automation
system involves the following steps:
• IED Data Engineering
• Communication Network Configuration
The engineering workflow of IET600 is depicted below.
a. Export IEDs - CID (icd) files from IED configuration tool such as PCM
600 for ABB IEDs.
b. Import specific IEDs cid/icd file for each IED type that is used in
substation.
c. Define full substation topology from Single Line diagram (SLD)
d. Map Logical Nodes of the IED to the primary elements in the Bay
9ARD171384-600 121
e. Add station level IEDs

f. Define RCB/GCB Datasets
g. Define subnetworks & connect IEDs
h. Map RCB and GCB clients
i. Export IEC 61850 Substation Configuration as scd-file
j. Re-import scd-file in all used IEDs with their specific IED configuration
tool (PCM 600 for ABB-IED)
Substation Engineering
Open the Substation tab in the Menu to access the IET600 functions to build the
substation topology. The Build group contains the following functions:
• Substation
• Voltage Level
• Bay
• IED
Figure 117. Substation Menu
Alternatively, these functions can be accessed through the context menu of the
respective nodes in the Navigation Tree.
• To create the substation node:
a. Select the project node and right click to open the Substation dialog.
Alternatively, select the Substation function in the menu to open the same dialog.
b. Enter a new Object Name for the substation.

c. Click OK and a new Substation node is created in the Navigation view.
122 9ARD171384-600
• To create a new voltage level:

a. Select the substation node and right click to open the menu.
Alternatively, click on the Voltage Level function in the menu to open the same
dialog.
b. Enter a new Object Name for voltage level.
The name must be unique within the substation.
c. Click OK and a new Voltage Level node is created in the Navigation view.
• To create a new Bay:
a. Select the Voltage Level node, right click and select “Create New Bay” or
click on the Bay function in the menu to open the Bay dialog.
b. Enter an Object name for the new Bay in the dialog.
c. Click OK and a new bay node is created in the Navigation view.
To define the full topology of the substation, repeat the steps for each successive
bay. The full substation topology is viewed from the voltage level node.
IED Data Engineering

In IET600, IEDs can be configured by manually adding an IED or copying a
configured IED from the same or another project.
• To create an IED from the Main Menu:
a. Select either the Substation or the IED menu tab.
b. Select IED
Select the node in the Dialog Tree to create the Standalone IED, right-
click and select Create new IED.
c. Click OK.
The navigation tree changes to either Substation or IEDs, if a new IED is created.
• To create an IED from the Context Menu:
9ARD171384-600 123
a. Select either the Substation or IED navigation tab.

b. Select a Tree Node,
this node could be,
– Substation, Voltage Level or Bay node in the Substation tab.
– the Project node in the IED tree.
c. Right-click the node.
The context menu for that node appears.
Figure 118. IED Context Menu
124 9ARD171384-600
d. Select Create New IED.
Figure 119. Create New IED
e. The tree in the dialog window shows the node that is used to create the
IED.
f. Enter the name of the IED and click OK.
• Updating IEDs:
During the later stages in the project engineering, an IED is updated in the
IET600 project whenever there is a change in the IED.
Updating an IED can be done,
– as a simple Update from a file (old IED content is removed and then
created newly from the file).
– as a Merge that allows user to merge parts of the IED in IET600 with parts
from the file.
To update an IED:
9ARD171384-600 125
a. Right-click on an IED and Select Update IED.
Figure 120. Import SCL File
b. Select any valid SCL file (SCD, ICD, CID file) and click Open.
Figure 121. Update IEDs
126 9ARD171384-600
c. Click OK.
The IED is imported from the file.
To check the differences between the Source and the Destination IED,
click <> in the Compare column. The following window appears.
Figure 122. Compare Source IED Window
Check the differences and click Merge to import the IED from the file.
The IED is imported into IET600.
9ARD171384-600 127
To update several IEDs:

a. Right-click on a Project, Substation, Voltage Level or Bay and select
Update IEDs.
Figure 123. Update Several IEDs Context Menu
b. Select any valid SCL file (SCD, ICD file) in Import SCL File and click
Open.
Figure 124. Import SCL Files
128 9ARD171384-600
c. The following Update IEDs window appears.
Figure 125. Updating IEDs
IET600 automatically matches the IEDs with the same name in IET600
and in the source file.
The Update column allows you to select or deselect individual IEDs for updating.
Only the selected IEDs are updated.
Perform Step c available in To update an IED to compare and merge the
source IEDs with the destination IEDs.
• Deleting IEDs:
IEDs can be deleted from its context menu. IEDs can either be completely
deleted or its content be removed.
• Mapping LNs to Substation Elements:
LN in any IED can be mapped to any node in the Substation Tree. However,
IET600 has mapping restrictions for efficient engineering and correct mapping
of specific LN types. For example, LN CSWI can be mapped only to
equipment of type CBR or DIS.
Some IEDs having LNs are mapped to an equipment from another Bay or to a
station level equipment.
Following restrictions are applied while mapping LNs to bay:
9ARD171384-600 129
– LN type CSWI and SCILO can only be mapped to equipment of the type
Circuit Breaker (CBR) or Disconnector (DIS).
– LN type XCBR and RSYN can only be mapped to equipment of the type
CBR.
– LN type XSWI can only be mapped to equipment of the type DIS.
– LN type MMXU can only be mapped to equipment of the type Current
Transformer (CT) or Voltage Transformer (VT).
– LN type LLN0 and LPHD can only be mapped to the bay.
An exception to the above rules is that all LN types can be mapped to the
bay. For more details, refer to IET600 manual.
Communication Engineering
This section explains on creating subnetwork and connecting the subnetwork to the
IEDs in the communication tree. Creating a subnetwork can be done using any of
the following methods:
• Creating Subnetwork from Main Menu on page 130
• Creating Subnetwork from Context Menu on page 132
Creating Subnetwork from Main Menu.

Perform the following steps to create subnetwork from the main menu:
1. Select the Communication menu tab.
Figure 126. IET600 Communication Tab
130 9ARD171384-600
2. To create a new subnetwork, select Subnetwork. The Create New

Subnetwork window appears as shown in Figure 127.
Figure 127. Create New Subnetwork - Main Menu
3. Enter the name of the subnetwork and click Ok.

4. If a new Subnetwork is created, the Navigation Panel changes to
Communication and the Subnetwork appears there and the editor does not
change.
9ARD171384-600 131
Creating Subnetwork from Context Menu.

Perform the following steps to create subnetwork from the context menu:
1. Select the Communication tab in the Navigation Panel, right click the Project
node. The Context Menu for that node appears:
Figure 128. Create Subnetwork - Context Menu
132 9ARD171384-600
2. To create a new subnetwork, select Subnetwork. The Create New

Subnetwork window appears as shown in Figure 127.
Figure 129. Create New Subnetwork - Main Menu
3. Enter the name of the subnetwork and click Ok.

4. If a new Subnetwork is created, the Navigation Panel changes to
Communication and the Subnetwork appears there and the editor does not
change.
Connecting IEDs to a Subnetwork in the Subnetwork Editor.

Perform the following steps to connect the IEDs to a subnetwork:
1. Select a tab in the navigation tree where the Subnetwork Editor is visible (IEDs
or Communication tab).
select an appropriate node (usually the Communications tab and the Root node or
a subnetwork node is a good choice).
9ARD171384-600 133
2. Select the Subnetwork Editor.
Figure 130. Subnetwork Editor
3. To connect the Subnetwork to an IED/Access Point, select the Subnetwork to

from the Subnetwork column. The Subnetwork column list all the existing
Subnetwork that can be connected to IEDs.
To disconnect the IED from Subnetwork, select an empty row.
After connecting the IEDs, the communication tree is updated and the
connected IED is seen under the new Subnetwork.
134 9ARD171384-600
An IED can have several Access Points that can be connected to different
Subnetworks. However, IED with two Access Point should not be connected to
the same Subnetwork.
Mapping of two Access Points of the same IED to the same Subnetwork by
should be avoided by sorting, for example. First sort the Access Point and then on
the IED.
Use the Fill Down mechanism to connect multiple IEDs/Access Points to a
Subnetwork.
Connecting IEDs to a Subnetwork in the Communication Tree.

Perform the following steps to connect the IEDs to a subnetwork in the
communication tree:
1. Select the Communication tab in the Navigation Panel.
9ARD171384-600 135
2. To connect IEDs to a Subnetwork in a communication tree, Drag and drop an

IED (Connected Access Point) to the Subnetwork.
Figure 131. Connect IEDs to Subnetwork - Communication Tree
The Communication Tree is updated and the IED is seen under the new
Subnetwork.
Unconnected IEDs/Access Points appear directly under the root node.
136 9ARD171384-600
Editing IP Addresses.
Perform the following steps to edit an IP address that is mapped to a subnetwork.
1. Select the Subnetwork Editor.
Figure 132. Subnetwork Editor - Edit IP Address
2. In the IP Address column, enter the IP Address.

Duplicate IP address are marked in Red and should not be duplicated.
9ARD171384-600 137
Dataflow Engineering
This section explains on the functionality and configuration of the dataflow required
for exchanging data between different IEDs. To configure the dataflow, the data
model of the IEDs and the communication (the connection between the IEDs) must
be defined. The IEC 61850 (Ed1) standard distinguishes:
• A Dataset that specifies what data are sent among the IEDs.
• A Control Block that specifies how the data are sent. IEC 61850 (Ed1) defines:
– Report Control Blocks (RCBs)
– GOOSE Control Blocks (GCBs)
IET engineering specifies two ways of communication engineering:
1. Vertical communication from bay level IEDs to HMIs or NCC Gateways. The
vertical communication includes:
– configuring Datasets, either manually or by rules.
– configuring Report Control Blocks, either manually or by rules.
– configuring Clients for the Report Control Blocks in a matrix.
2. Horizontal communication between IEDs with similar functionality (typically
between. The horizontal communication includes:
– configuring Datasets, either manually or by rules.
– configuring Goose Control Blocks, either manually or by rules.
– configuring receivers for Goose Control Blocks in a matrix.
Creating (RCB) Datasets Manually.

Datasets for RCBs can be manually created either from Communication main menu
or from the context menu of the node in the navigation tree.
Creating Datasets from Main Menu.

Perform the following steps to create dataset from Main Menu:
138 9ARD171384-600
1. Select the Communication menu to open the Communication Navigation tab

as shown in Figure 133.
Figure 133. Communication Menu - Dataset
2. To create a Dataset, select Create Dataset(s) from the Communication menu.

The Create New Dataset window appears as shown in Figure 134. Select an
LN, and enter a name for the Dataset.
The name entered must be a valid. Duplicate names or special characters are not
allowed for a particular node.
Figure 134. Create New Dataset
3. Click OK to create the new Dataset.

If a new Dataset is created, the Navigation Tree remain as is and the Editor
changes to Dataset.
9ARD171384-600 139
Creating Datasets from Context Menu.

Perform the following steps to create dataset from Context Menu:
1. Select the Dataset Editor.
2. Select any node that has Datasets below it in the Navigation Tree.
3. Select a row with an existing Dataset in the LN to create a new Dataset.
Figure 135. Dataset Editor
4. Right-click and select Insert new row from the context menu.
140 9ARD171384-600
5. The Create New Dataset window appears as shown in Figure 136. Select an
LN, and enter a name for the Dataset.
Figure 136. Create New Dataset
6. Click OK to create the new Dataset.
Editing Datasets.
In the Dataset Editor, the name and the description of a Dataset can be edited. If
name is changed, the attached RCBs or GCBs are automatically updated.
Adding Dataset Entries.

To add Dataset Entries, the lower panel of the editor is used.
9ARD171384-600 141
1. Select the Dataset to which you want to add entries.
Figure 137. Dataset Entries
2. The selected Dataset determines the IED. The first list shows the available LDs.
3. Select LD > LN > DObject > DAttr.
It is recommended Not to configure RCB or GCB datasets containing Data
Objects and Data Attributes of Functional Constraint type CO as it is used for
Control purpose.
142 9ARD171384-600
Following precaution should be handled in the configured SCD file during

Communication Engineering:
• For GCB Data Set, the signals must be assigned at Data Attribute (DA) level.
Ensure that for each configured GCB Data Set, Quality (q), Time (t), and
Signal Attribute is available. Time attribute is optional for GOOSE signals.
For example: stVal, ctlModel, q
SCD file import is cancelled, if the configured SCD file does not contain
Signal Attribute.
• For RCB Data Set, the signals must be assigned at Data Object (DO) level
that includes the attributes of the DO (Signal, Quality (t), and Time (t)).
For example: Pos, EnaOpn, EnaCls
Figure 138. IED Dataset Add
4. Select a unique Functional Constraint.

All the attributes added to the Dataset are seen in the Data Result List. If the list is
empty, the selection is not yet valid (when the Data Object has attributes with
several Functional Constraints, for example; CF and ST and FC is not yet been
selected).
9ARD171384-600 143
Figure 139. IED RCB Dataset
5. Click Add to add the attributes to the Dataset entries.

It is not possible to add the same data twice to the same attribute, for example.
CMMXU1.A[MX] cannot be added twice to the same attribute.
144 9ARD171384-600
Creating RCBs from Main Menu.

1. Select the Communication menu, the Communication Navigation tab is
automatically be selected as shown in Figure 140.
Figure 140. Communication Menu
2. To create RCB, you can preselect an appropriate node in the Substation, IEDs,
Communication Navigation Tree or select the Project node Figure 141.
Figure 141. Communication Tree - RCB
9ARD171384-600 145
3. Select Create RCB(s), Create New RCB window appears as shown in

Figure 142. Select an LN, and enter a name for the RCB.
Figure 142. Create New RCB
4. Click OK to create the new RCB.
Creating RCBs from Context Menu.

1. Select the RCB Editor.
2. Select any node that has RCBs below it in the Navigation Tree.
146 9ARD171384-600
3. Select a row with an existing RCB in the LN.
Figure 143. RCB Editor
5. Create New RCB window appears as shown in Figure 144. Select an LN, and
enter a name for the Dataset.
9ARD171384-600 147
Figure 144. Create New RCB
6. Click OK to create the new RCB.
Editing RCBs.
The RCB configuration can be edited in the RCB editor. Following must be
observed during renaming:
• An RCB cannot be renamed. To rename an RCB, delete it and create a new
RCB with the intended name.
• Removing a Dataset from an RCB will automatically put the RCB into a
deleted state.
• Configuration changes will cause the configRev value to be increased to the
next multiple of 10,000. This will happen only once between import and
export, not with every change.
Configuring RCB Client .

To do a RCB client configuration, the potential clients and their communication
configuration should be known (Gateways). Before doing the RCB client
configuration add these IEDs and configure them to the subnetworks.
Bay-level IEDs can be added and configured easily also in later stages of the
project.
148 9ARD171384-600
RCB Client Editor Overview.

The RCB client editor rows display IEDs (or their Access Points) and RCBs. The
rows depend on the node selected in the Navigation Tree.
The columns show the available client IEDs (and their Access Points). Valid clients
are IEDs that have IHMI, ITCI, or ITMI Logical Nodes. The columns does not
depend on the node selected in the Navigation Tree.
Figure 145. RCB Clients
9ARD171384-600 149
Configuring Default Clients.

Default clients are configured for each IED. These Default clients are used by the
rule-based RCB generation to automatically configure clients.
1. Select the RCB Client Editor.
Figure 146. IED Default Client
2. Make the AP column visible in the RCB Client Editor, if IEDs have more than
one Access Points.
3. To configure the IEDs/Access Points with Default and RCB clients:
– Click Clear All to remove all the existing clients.
– Click Configure Empty to configure clients for those IEDs/Access Points
that have no clients configured yet.
– Click Configure All to delete all the existing clients and replace them
with default configuration.
150 9ARD171384-600
Creating GCBs/Datasets/Clients.
GCBs/Datasets can be generated:
• from the context menu of an IED.
• from the context menu of an IED under a node.
1. To generate GCBs/Datasets, right-click a node and select Generate
GCBs/Datasets from the context menu.
Figure 147. Generate GCBs / Datasets Context Menu
2. GCBs/Datasets are generated.

If a node is selected in the navigation tree other than an IED, the IEDs under that
node are used for generating GCBs/Datasets.
3. Following conditions apply, while automatically creating Datasets and GCBs:
9ARD171384-600 151
– Existing Datasets that have a Status of Manually Created or IED

configured, Fix are not touched.
– Otherwise, Datasets are changed, added or deleted as required by
Rulesets.
– Existing GCBs that have a Status of Manually Created or IED
configured, Fix are not touched.
– Otherwise GCBs are added or deleted as required by the number of
Datasets generated by the rules.
– Deleted GCBs are recycled.
GCB Clients have to be created manually in the GCB client editor.
Creating (GCB) Datasets Manually.

Datasets for GCBs can be manually created either from Communication main menu
or from the context menu of the node in the navigation tree.
Creating Datasets from Main Menu.

1. From the Communication menu, select Create GCB(s) as shown in
Figure 148.
Figure 148. Communication Tab - Create GCBs
2. Create New GCB window appears as shown in Figure 149.
152 9ARD171384-600
Figure 149. Communication Tab - Create GCBs
3. Select an LN, and enter a name for the GCB.

4. Click OK to create the new GCB.
9ARD171384-600 153
Creating GCBs from Context Menu.

1. Select the GCB Editor.
2. Select a node that has GCBs below it in the Navigation Tree.
3. Select a row with an existing GCB in the LLN0 where you want to create new
GCB.
Figure 150. GCB Editor
5. Repeat Step 2 to Step 4 to create GCBs from the context menu
154 9ARD171384-600
Configuring GCB Client .

To perform GCB client configuration, most of the Bay-level IEDs should be
identified and attached to the correct Subnetworks.
1. Select the GCB Client Editor.
2. Make the AP column visible in the GCB Client Editor, if IEDs have more than
one Access Points.
Figure 151. GCB Clients
3. To configure the GCBs with Clients:
9ARD171384-600 155
– Right-click and select Remove all GCB Client connections to remove all
existing connections in the editor and all related inputs.
If this action is preformed, all the configured mappings in the Signal Matrix in
PCM600 is lost. This can be avoided by setting the filters and hiding all the IEDs
that are configured for GCB clients.
– Right-click and select Connect all GCBs to Clients to connect all GCBs
in rows to all Clients in the columns.
Exporting SCD File

SCD files are exported from the Main menu or Context menu of the project.
From Main Menu
1. Select the Home menu tab.
2. Click Export in the Main Menu.
Figure 152. SCD File Export - Main Menu
3. Export SCL File dialog window appears. Select the directory to save the file
and with an appropriate SCD file name.
156 9ARD171384-600
Figure 153. SCD File Save
9ARD171384-600 157
From Context Menu

1. Right-click on a Project and select Export SCL File from the context menu.
Figure 154. SCD File Export - Context Menu
2. Export SCL File dialog window appears. Select the directory to save the file
and with an appropriate SCD file name.
158 9ARD171384-600
Figure 155. SCD File Save
This completes the creation of a fully configured SCD file in IET600 Tool.
9ARD171384-600 159
Updating IED configuration with SCD file Section 2 Substation Engineering
Updating IED configuration with SCD file

This section explains how to update the IED configuration with SCD file that
contains the communication information.
The IED Device Configuration tool is used for configuring ABB IEDs. In this
example, ABB PCM 600 Device Configuration Tool. For handling third party
IEC 61850 IEDs, contact the IED vendor.
Goal:
To update the IED about the signal Engineering done in CCT and also about
application engineering in IED to receive GOOSE data.
For a detailed information on IED configuration, refer to the respective IED
Engineering Manual.
Inputs:
SCD file.
Output:
IED is aware of GOOSE and MMS signals it is expected to transact.
Tools used:
PCM 600. Other specific tools for 3rd party IEDs.
The resulting SCD file contains individualized IED descriptions for the system
under design. Download these descriptions through IED tools to IEDs to confirm
the location in the system and the connection to other IEDs.
Perform the following steps to configure the IED:
1. Open PCM 600 project.
2. Right-click the substation level and select Import.
Ensure to take a PCM project backup before import. Open/Manage project and
select Export Project as shown in Figure 156. This saves the project in .pcmp
format. In case something goes wrong, this saved project can be imported back.
160 9ARD171384-600
Section 2 Substation Engineering Updating IED configuration with SCD file
Figure 156. PCM Project Backup option
Figure 157. Import SCD File in PCM 600
3. Select the SCD file.
9ARD171384-600 161
4. In the SCL Import Options dialog box, select Advanced Options.
Figure 158. SCL Import Options Tab
5. Click Import to start import.

6. After successful import of SCD file, the PCM 600 tree structure appears as
shown in Figure 159.
Figure 159. PCM Tree Structure with Updated IED
The question mark appearing on an IED icon might be a PCM 600 error. Close
the PCM 600 and reopen to clear the question mark.
162 9ARD171384-600
7. In PCM 600, right-click the IED and select Signal Matrix.
Figure 160. Option to Open the Signal Matrix
9ARD171384-600 163
8. In the Signal Matrix tool, define the Hardware input/output connection to the
variables defined in application logic. Define the Goose matrix.
Notice that the tab named Goose Receive is created.
Figure 161. Signal Matrix Tool- Goose Receive
9. Select the Goose Receive tab and perform the signal mapping of GOOSE
sending and receiving channels.
Figure 162. SMT GOOSE Mapping
Figure 162 explains that signal Tr1 from CI868 IED will be assigned to channel
GooseData1 in the IED REC670.
10. A function block is defined in an application logic. This enables the digital
output to be switched on while receiving GOOSE data. Map the function block
channels to real hardware outputs in the Binary Outputs tab. Similarly, LED
outputs can also be mapped.
164 9ARD171384-600
Figure 163. Signal Matrix Tool
11. Signal Matrix is configured. Click to download the signal matrix

configuration to IED.
Figure 164. Signal Matrix Save
12. Right-click the IED and select Write to IED.

The technical key in the physical IED and IED object in PCM600 must be the
same, otherwise it is not possible to download the IED configuration.
9ARD171384-600 165
Figure 165. Write to IED
166 9ARD171384-600
13. The Read/Write window appears, click Yes to continue.
Figure 166. IED Download Prompt
14. The process of download is shown in the progress bar.
Figure 167. IED Download In Progress
IED restarts after the download is complete. The IED is then ready to exchange both
MMS and GOOSE data.
15. Repeat Step 1 to Step 14 for other IEDs.
IED parameters can be set through Parameter setting tool in the PCM 600. Do not
set hysteresis values to very low for analog values (that is, voltage, current). This
results in unnecessary fluctuation in the indication of analog values.
9ARD171384-600 167
CI868 IED Engineering with Control Builder M Section 2 Substation Engineering
CI868 IED Engineering with Control Builder M

Goal:
• To create hardware tree structure in Control Builder with GOOSE and MMS
communication for CI868.
• To develop IEC 61131-3 Application for Circuit Breaker control using
ProcessObjectBasicLib library Function blocks for IED.
Inputs:
SCD file and application logic for AC 800M Controller.
Output:
Hardware tree structure in Control Builder is created for CI868 with GOOSE and
MMS data exchange with other IEDs.
Tools used:
Control Builder M with IEC 61850 Wizard.
Workflow:
1. Open the Control Builder project that was used for creating CID / ICD file as
168 9ARD171384-600
Section 2 Substation Engineering CI868 IED Engineering with Control Builder M
Figure 168. Control Builder ICD Tree Structure
9ARD171384-600 169
2. Right-click CI868 object and select IEC 61850 Wizard as shown in

Figure 169.
Figure 169. IEC 61850 Wizard - Context Menu
170 9ARD171384-600
The IEC 61850 Wizard appears as shown in Figure 170.
Figure 170. IEC 61850 Wizard Window
3. Click Browse to locate the .scd file folder. Select the SCD file and click Open.
Figure 171. IEC 61850 Wizard Window - Browse
9ARD171384-600 171
IEC 61850 wizard detects all CI868 IEDs and the corresponding access points in
SCD file and lists in Select IED Name drop-down list.
The list can also have AC800M IED.
4. Select the corresponding CI868 IED from the Select IED Name and click
Verify to validate any errors only for the selected CI868 IED access point in
the configured SCD file.
If any errors are found in the selected access point of the SCD file, they are
logged in the IEC61850 Wizard log file. A generic message is displayed to refer
the IEC61850ImportWizard.log file.
5. Click Import to import the SCD file into the existing CI868 module in Control
Builder hardware.
For projects with multiple CI868 IEDs, the correct instance of CI868 module has
to be selected for SCD file import. For rules regarding the selection criteria, refer
to AC800 M configuration manual (9ARD171385*).
Figure 172. SCD File Import Wizard
172 9ARD171384-600
SCD file import is cancelled, if the Main Signal data attribute is not configured in
k
the inputs sections of the SCD file. A warning message appears as shown in
Figure 173. To configure the Main Signal attribute perform Step 6 and Step 7
explained in Configuring Vertical Communication for MMS Protocol on page 99
Figure 173. Missing Signal Attribute Warning message
6. Notice the progress bar showing the progress of import as shown in Figure 174.
Figure 174. IEC 61850 Wizard SCD File Import Progress
9ARD171384-600 173
7. The Tree View Comparator opens after importing the SCD file as shown in
Figure 175.
Figure 175. Tree View Comparator Window
174 9ARD171384-600
8. In the Comparator dialog box, click Create.
Figure 176. Import Wizard Comparator Window
9. Once the import is completed, a successful message box appears as shown in

Figure 177. Click OK.
Figure 177. Import Wizard Upload Success Message
After import, the SCD file is saved in Control Builder project folder (Compact
Control Builder) or Aspect Directory (Control Builder professional). For every
subsequent import, the SCD file is overwritten and the last imported SCD file per
CI868 IED is saved. Only one SCD file is stored per CI868.
Deleting the CI868 object in the Control Builder tree structure deletes the stored
SCD file.
The Get SCD button in the IEC61850 Wizard window retrieves the last saved and
imported SCD file. This SCD file is used for retaining configured Data set and
GOOSE Control Blocks during subsequent CID file export. For more
information, refer to Retaining Data Set and GCBs in Configured CID File on
page 53.
10. In the IEC61850 Wizard tool, click CCF tab.
CCF tab is viewed or used only for maintenance purpose.
9ARD171384-600 175
Figure 178. CCF View
Select the CCF file of the access point to verify the number of datasets available in
the corresponding CCF file.
Figure 179. CCF View Datasets
176 9ARD171384-600
It is recommended to have maximum of 150 datasets assigned to a single CI868

module (GCBs and RCBs) in SCD file.
A caution is displayed in CCF view, when the assigned datasets in CI868 exceeds
150.
Click Ok to open the CCF file as a tree structure in the Selected CCF File tree view.
Select the object or node in the CCF File tree structure, contents of the object are
displayed in the property view as shown Figure 11.
Figure 180. CCF File Tree Structure
9ARD171384-600 177
11. Right-click the IEC 61850 Wizard screen and from the context menu select
View Log to view the log information as shown in Figure 181.
Figure 181. IEC 61850 Wizard View Log
12. Click Exit.

This completes the import of a fully configured SCD file and the hardware tree
structure is created in the Control Builder M project as shown in Figure 182.
178 9ARD171384-600
Figure 182. Hardware Tree Structure in Control Builder
9ARD171384-600 179
CI868 IED Sending GOOSE Signals Section 2 Substation Engineering
The position of the GOOSE objects in the Control Builder hardware tree structure
is between 1 to 199, for MMS Diagnostics the numbering is 200, and for MMS
objects it is between 201 to 254. IEC 61850 Wizard generates the numbering
sequence during SCD file import.
The naming convention of MMS objects in the Hardware tree is as follows:
<LN Prefix>_<LN Instance> <LN name>. For example, CV_2 MMXU
Use the Hide Unused Channels option to hide the IO channels that have empty
Protocol Info for all the Hardware objects in CI868 hardware library.
CI868 IED Sending GOOSE Signals

Double-click on a Logical Node to open the hardware editor. The editor shows the
data that is sent to the IED. In this case, it is IED AA1FP1 and AA1A2.
The protocol information path for GOOSE data been sent out from CI868 to other
IEDs in IEC 61850 is in the following format:
SubNetworkName.IEDName.
For example. AA1WA1.AA1FP1, In this example, AA1WA1 is the subnetwork
and AA1FP1 is the IED that receives GOOSE Data from CI868 IED.
Figure 183. Hardware Editor Window for GOOSE Output
180 9ARD171384-600
Section 2 Substation Engineering CI868 IED Receiving GOOSE Signals
CI868 IED Receiving GOOSE Signals

Open the Hardware editor of a Receive Data Block, for GOOSE receive signals. The
editor shows the data that is received from other IEDs to CI868 IED.
Figure 184. Hardware Editor Window for GOOSE Input
The protocol information path for GOOSE data sent from other IEDs to CI868 in
IEC 61850 is in the following format:
SubNetworkName.IEDName.LogicalDeviceName.LogicalNodeName.Dat
aObjectName.
For example. AA1WA1.AA1A1.LD0.SP16.GGIO.2.Ind, where
• AA1WA1 is Subnetwork
• AA1A1 is IED
• LD0 is Logical Device
• SP16.GGIO.2 is Logical node
• Ind is Data Object
9ARD171384-600 181
CI868 IED Receiving GOOSE Signals Section 2 Substation Engineering
Control Builder hardware object LN-ATCC Data Object name attribute is

corrected from Vol to CtlV according to IEC61850 specification 7-4.
When a Control Builder project is migrated from previous version, the ATCC LN
Hardware Object (under CI868 MyIED object) containing Vol channel is
automatically updated to new CtlV channel and the previously connected
variable Protocol info for the Vol channel is retained in the new CtlV channel.
However after migration, if SCD file containing ATCC LN as Data Object name
Vol is imported in new Control Builder version, the protocol info for CtlV
channel under ATCC LN Hardware Object is missing due to the correction
implemented in ATCC LN Hardware Object.
To retain the communication for the ATCC CtlV channel, before importing SCD
file, ensure that the Data Object name under ATCC LN is corrected from Vol to
CtlV in SCD file via XML Marker tool as shown in Figure 185, Figure 186 and
Figure 187.
182 9ARD171384-600
Figure 185. SCD file - Logical Node ATCC, DataSet Level
9ARD171384-600 183
CI868 IED Receiving GOOSE Signals Section 2 Substation Engineering
Figure 186. SCD file - Logical Node ATCC, Inputs Section Level
184 9ARD171384-600
Figure 187. SCD file - Logical Node ATCC, LN Level
9ARD171384-600 185
CI868 IED MMS Command Signal Section 2 Substation Engineering
CI868 IED MMS Command Signal

Open the Hardware editor for MMS logical node level below the IED level.
Figure 188. Hardware Editor Window for MMS Command
CI868 IED Receiving MMS Signal

Open the Hardware editor for MMS logical node level below the IED level.
Figure 189. Hardware Editor Window for MMS Receive
186 9ARD171384-600
Section 2 Substation Engineering Control Builder Application Engineering with IEC 61850 Communication
Control Builder Application Engineering with IEC 61850 Communication

CI868 supports sending of IEC 61850 MMS Control Commands to CSWI and
XCBR controllable LNs in other IEDs for typical application such as Circuit
Breaker Control.
The application logic for Circuit Breaker control is available in two Function Blocks
under ProcessObjectBasicLib namely IEDStatusReceive and IEDCommandSend.
Both Direct and Select Before Operate (SBO) mode of operation can be configured
by using these function blocks along with standard Application Libraries to map the
Process Control Commands to IEC 61850 Control Commands.
Perform the following steps to insert the ProcessObjBasicLib library:
1. Right-click Libraries and select Insert Library as shown in Figure 190.
Figure 190. Insert Library
9ARD171384-600 187
Control Builder Application Engineering with IEC 61850 Communication Section 2 Substation
2. Select ProcessObjBasicLib and click Insert. Figure 191 shows

ProcessObjBasicLib listed under libraries structure.
Figure 191. Insert Library
188 9ARD171384-600
Figure 192. Control Builder Libraries list
9ARD171384-600 189
Control Builder Application for IEC 61850 GOOSE Communication

Perform the following steps to create a Controller Application for Bay type motor
feeder.
1. Right-click Application and select New Application from the context menu as
Figure 193. Create a New Application
2. Enter the name of the application and click Ok.

The application is listed under Applications in the Control Builder project as
Figure 194. New Application
190 9ARD171384-600
Figure 195. Application List
9ARD171384-600 191
3. To create a new program, right-click Applications, Select New > Program

from the context menu as shown in Figure 196.
Figure 196. Create Application Program
4. Enter the name of the program and click Ok.

The program is listed under Programs in the Control Builder project as shown
in Figure 198.
Figure 197. New Program Window
192 9ARD171384-600
Figure 198. Load Shed Program
5. Double-click the program to open the Program Editor window as shown in

Figure 199.
Figure 199. Control Builder Program Window
9ARD171384-600 193
6. Define a sample application logic to enable the CI868 to send a trip signal to
the IED whenever the Power exceeds the MaxPower. The IED sends Current
and Voltage signal to CI868 through GOOSE.
7. Define the signals for the Load Shed application as shown in Figure 200.
Figure 200. Variable List
8. For example, define a sample logic for loadshed as shown in Figure 201.
Figure 201. Control logic in Control Builder
9. Save the program and close the Program Editor window.

This completes the Controller Application for Bay Type Motor Feeder.
Control Builder Application for Circuit Breaker Control with MMS Commands
This section explains how to use the Controller Application for Motor Feeder with
controlled circuit breaker via IEC 61850 communication.
Under ProcessObjectBasicLib, IEDCommandSend and IEDStatusReceive function
blocks are available for mapping process control commands to IEC 61850 control
commands. IEDCommandSend object performs MMS based Direct and Select
Before Operate (SBO) Functions to control circuit breakers or switches and
generate feedback timeout error signals. Circuit Breaker control functionality is
typically used for operator commands from CI868 to other IEDs.
194 9ARD171384-600
IEDStatusReceive object is used to receive status information from the IED and
provide actual feedback status information to process object function blocks.
IEDCommandSend and IEDStatusReceive function blocks can be used with any
library. The sample application in Figure 210 shows function block of
Uni_Simple from processObjectBasicLib library.
Perform the following steps to create Control Builder Application for Circuit
Breaker Control via MMS:
1. To create a new program, right-click Applications, Select New > Program
from the context menu as shown in Figure 202.
Figure 202. New Application Program
2. Enter the name of the program and click Ok.

The program is listed under Programs in the Control Builder project as shown
9ARD171384-600 195
in Figure 204.
Figure 203. New SBO Program Window
Figure 204. SBO Program List
3. Double-click the program to open the Program Editor window as shown in

Figure 205.
196 9ARD171384-600
Figure 205. SBO Program Editor Window
4. Create application logic to perform Select Before Operate (SBO) Function to

control circuit breakers or switches and generate feedback timeout error
signals.
9ARD171384-600 197
5. Define the variables for the SBO application as shown in Figure 206.
Figure 206. SBO Variable List
6. Assign the defined variables to the parameters.

a. Assign variables to the parameters for IEDStatusReceive function block,
Figure 207. IEDStatusReceive - Assign Parameter
198 9ARD171384-600
b. Assign variables to the parameters for UniSimple function block, as

Figure 208. UniSimple - Assign Parameter
9ARD171384-600 199
c. Assign variables to the parameters for IEDCommandSend function block,

Figure 209. IEDCommandSend - Assign Parameter
7. A typical Application with SBO created for Circuit Breaker Control is shown
in Figure 210.
The IEDStatusReceive and IEDCommandSend function blocks can be used
with any Library. In this example, the sample application shows using
UniSimple_1 function block from ProcessObjBasicLib.
For more information on IEDCommandSend and IEDStatusReceive function
block, refer to AC 800M IEC 61850 Configuration for CI868 (9ARD171385*)
Manual.
200 9ARD171384-600
Figure 210. SBO Function Block
The Out0 and Out1 parameter of UniSimple function block sends Open and
Close command respectively, which is received by Open and Close input
parameter of IEDCommandSend_1 function block. The CTLCMD parameter in
IEDCommandSend function block sends the necessary Control Commands to
the respective IED. The feedback from the IED is received by PosStatus
parameter of IEDStatusReceive function block and further sent to the
UniSimple function block as actual feedback.
9ARD171384-600 201
IEDCommandSend function block has additional monitoring outputs

SelectFailed, CloseFailed, OpenFailed and IOError can be connected to
AlarmCond, AlarmCondBasic or SimpleEventDetector external function
blocks to generate Alarms and Events as per project requirements.
CancelTimeout is used to delay the operate command, when selected feedback from
IED is active.
• If the Cancel input is received within CancelTimeout time:
– Cancel with Open commands are sent
or
– Cancel with Close commands are sent.
• If the Cancel input is received after CancelTimeout time:
– Operate with Open commands are sent
or
– Operate with Close commands are sent.
The configured value for CancelTimeout must be lower than the duration of stSeld
staying active on a selection in respective IED.
The configured value in the IEDCommandSend function block for SelTimeout must
be greater than the duration of stSeld staying active on a selection in respective IED.
The configured value IEDCommandSend function block for PosTimeout must be
greater than the duration of configured SelTimeout value.
Configuring Process Alarm for Circuit Breaker Control using Signal ID

SignalIDs are used for generating Alarms and Events with the external timestamp of
IED in the Alarm and Event list.
The SignalId used for capturing the Alarm or Event in the Simple Event Detector or
Alarm Cond Block contains the hardware address of the CSWI or XCBR logical
node along with the device number and the name of the Alarm or Event.
For example:
CIPos(1-12).IEDPos(1-n).LDPos(1-n).CSWI_LNPos(1-n).BreakerNumber(1-4)
202 9ARD171384-600
For example. 1.2.201.9.1.E_Cls.

For more information on hardware address, refer to AC 800M IEC 61850
Configuration for CI868 (9ARD171385*) Manual.
Perform the following steps to create a sample logic for Alarm and Event using
SignalID:
1. Define the variables for Alarm Cond and Event Detector function block as
Figure 211. Alarm and Event Condition Variable
Alarms and Events generated using Signal ID is used for External / IED time
stamp.
9ARD171384-600 203
2. Create a sample logic for Alarm Cond and Event Detector as shown in
Figure 212.
204 9ARD171384-600
Figure 212. Alarm and Event Generation using Signal ID
9ARD171384-600 205
The Alarms are generated for the IEDs, only if the Generate Alarm parameter is
set to Enable for the corresponding IED hardware object as shown in Figure 213.
For more details on Alarms and Event generation using SignalID, refer to AC
800M Configuration for CI868 (9ARD171385*) Manual.
Figure 213. Generate Alarms - IED Hardware Object
206 9ARD171384-600
Figure 214 shows Alarm and Event list with Process Alarms for the application
logic for Alarm Cond and Event Detector.
Figure 214. Alarm and Event List with Process Alarms
3. Save the program and close the Program Editor window.

This completes the creation of a sample application logic of SBO Function
Block for controlling circuit breakers.
9ARD171384-600 207
Connecting Applications to Controller

Perform the following steps to connect the application logic to the controller.
1. To connect the Application to the Controller, right-click the Connected
Applications from the context menu and click Connect Application as shown
in Figure 215.
Figure 215. Application Connection in Control Builder
2. The Reserve dialog window appears, enter the comment and click OK.
Figure 216. Reserve Window
208 9ARD171384-600
3. Select the application to be connected to the Controller and click Ok. The
application is added under Controller > Connected Applications as shown in
Figure 217.
Figure 217. Connect Application Window
Figure 218. Connected Application List
4. To connect the task (that is, cycle interval) for Application and Program,
right-click the Application and select Properties > Task Connection from the
context menu as shown in Figure 219.
9ARD171384-600 209
Figure 219. Task Connection Option
5. The Task Connection window appears as shown in Figure 220. Select the task
from the list and click Ok.
Figure 220. Task Selection Window
6. Similarly, select the task connection for the program.
Figure 221. Application Connection
210 9ARD171384-600
Assigning Variables to Channels (IEDs)

Perform the following steps to assign the variables to the IEDs.
1. Connect the program variables to the actual channels.
2. Open hardware tree editor for DO MVgroup under IED.
Figure 222. Hardware Tree Editor
3. Click icon and select the variable.
Figure 223. Variable Assignment in Control Builder
9ARD171384-600 211
4. For assigning GOOSE Data, open the hardware editor of LN of the IED
AA1A2 and assign the program variables as shown in Figure 224.
Figure 224. Hardware Editor Window GOOSE Input
5. Similarly, open the hardware editor of LN of the CI868 IED and assign the
program variables as shown in Figure 225.
Figure 225. Hardware Editor Window GOOSE Output
212 9ARD171384-600
6. For assigning MMS Data Receive, open the hardware editor of LN of the IED
AA1E1Q01 as shown in Figure 226 and assign the program variables.
Figure 226. MMS Hardware Editor Assign Variable
9ARD171384-600 213
Defining IP address of the Controller

Perform the following steps to define the IP address of the controller.
1. To define the IP address of the Controller, right-click the IED (For example,
Controller_1) and select Properties > System Identity from the context menu
Figure 227. System Identity Selection
214 9ARD171384-600
2. In the System Identity window, enter the IP address and click Ok.
Figure 228. Enter System Identity
3. Double-click the IED to open the Hardware editor. In the Hardware editor
window, enter the IP address of the Controller at the Ethernet level.
Figure 229. Controller IP Address Assignment
9ARD171384-600 215
4. The programming is complete. Click and Go Online icon to download the

program to the Controller.
Figure 230. Control Builder Project Download
Once program download is successful, CI868 goes into hardware initialization

mode.
Figure 231. CI868 Status in Control Builder
5. Check the online view of Load Shed in the program.
Figure 232. Online View in Control Builder
In this example, the power is more than Maxpower. AC 800M sends the TripSignal
to AA1A1.
6. Open the Application Configuration page of the IED in PCM 600 and use
online option to check whether the signal is reached into the selected IED.
216 9ARD171384-600
Figure 233 shows a sample screen shot of the IED in PCM 600 in online mode.
Figure 233. IED Online View in PCM 600
7. Simulate the current value to zero and observe that TripSignal is no longer
True.
Figure 234. Online View
9ARD171384-600 217
8. Figure 235 shows the online view of SBO in the program.
Figure 235. SBO Online View
218 9ARD171384-600
9. Figure 235 shows the online view of the Alarm Cond and Simple Event
Detector.
Figure 236. Alarm Cond and Simple Event Detector Online View
This completes the configuration of GOOSE and MMS Application.
9ARD171384-600 219
Figure 214 shows sample Alarm and Event list with Process Alarms for the
application logic for Alarm Cond and Event Detector.
Figure 237. Alarm and Event List with Process Alarms
220 9ARD171384-600
Section 2 Substation Engineering IEC 61850 Connect Engineering
IEC 61850 Connect Engineering

This section describes about configuring the 800xA system for IEC 61850 (Ed1)
vertical communication using IEC 61850 (Ed1) Connect and IEC 61850 OPC
Server software.
The configuration for 800xA system on MMS and GOOSE communication task is
classified into two steps as follows:
• IEC 61850 OPC Server Configuration
• 800xA Control and Functional Structure Configuration
IEC 61850 OPC Server Configuration

Goal: Configure Alarm and Event in IEC 61850 OPC Server.
Inputs: SCD file
Outputs: OPC Server is configured and vertical communication with IED
established
Tools Used: CET for IEC 61850 OPC Server
Workflow: Perform the following steps to configure IEC 61850 OPC Server for
Alarm and Event, and vertical communication with IEDs using Communication
Engineering Tool.
Install the CET tool on the Connectivity Server node.
1. Open CET (Communication Engineering Tool).
Figure 238. Communication Engineering Tool Icon
9ARD171384-600 221
IEC 61850 OPC Server Configuration Section 2 Substation Engineering
Figure 239. Welcome Screen of CET
2. Create a new project.
Figure 240. OpenManage Project
222 9ARD171384-600
Section 2 Substation Engineering IEC 61850 OPC Server Configuration
Figure 241. New Project
Figure 242. Create and Open a New Project in CET
9ARD171384-600 223
3. In CET, right-click the project and select New > Communication > Computer
Node.
Figure 243. Create a Computer Node in CET
4. Right-click the computer node and select New > IEC 61850 > IEC 61850
OPC Server to create OPC Server object.
Figure 244. Create OPC Server Object in CET
224 9ARD171384-600
5. Rename the OPC Server object. It is recommended to maintain the same name
as the subnetwork. In this example, it is AA1MainNorth1.
Figure 245. Rename OPC Server Option in CET
For one subnetwork in SCD file, define one OPC Server object.
CET can support SCD files configured with one or more subnetworks (max 16)
under one OPC Server object.
6. Right-click the OPC Server level and select SCL Import.
Figure 246. SCD Import in CET
7. In the IEC61850 OPC Server SCL Import screen,

a. Click Choose File to select the SCD file.
b. Select the OPC Server for desired subnetwork from the list.
SCD file supports multiple configured IEC 61850 OPC server instances in one
subnetwork.
9ARD171384-600 225
c. Click Import.
Figure 247. SCD Upload in CET
226 9ARD171384-600
Table 8 details the communication Options field available in the IEC61850 OPC
Server SCL Import screen.
Table 8. Communication Options field details
Subnetwork Field Labels Description

Filter DOs that don’t belong to On selecting this option the performance can
DataSet be enhanced, as it limits the amount of data
objects being imported. If a data object does
not belong to any data set, it will not be
imported. Some IEDs can provide large
amounts of data that is not reported, that is,
not updated in this substation HMI.
Overwrite existing descriptions This option overwrites all existing descriptions
on objects affected by the import operation.
Select this option only if you know that the
importable file contains better descriptions
than your current configuration.
Import protocol configuration On selecting this option, both the object tree
(sAddr) and protocol configuration are created. If you
do not select
This option, only the object tree structure is
created. This option is selected by default,
when SCD file is selected for import.
Overwrite Alarm and Event On selecting this option, all configured alarm
settings and event settings are overwritten and the
default settings are assigned to them. Select
this option only when you have customized
alarm and event settings on your current
configuration.
This option is selected by default, when SCD
file is selected for import.
Overwrite limit settings On selecting this option, all configured unit
and limit configurations are overwritten and
the values from the SCL file are assigned to
them.
9ARD171384-600 227
Table 8. Communication Options field details
Subnetwork Field Labels Description

Do not import DO's without On selecting this option, none of the data
protocol configuration (sAddr) objects without communication information
are created to the object tree.
Check RCBs for Client Identity On selecting this option, IEDs are imported
from the given file in which the client identity
of the Report Control Blocks matches the
selected OPC Server.
Check Configuration Revisions On selecting this option, configuration revision
attributes of the project are compared to the
SCL file to be imported.
After successful import, all the IEDs, LDs and LNs are created for the selected
subnetwork.
Figure 248. CET Tree Structure
228 9ARD171384-600
a. Verify the OPC client in CET tree structure.
Figure 249. OPC Client Name in CET
This client name should be entered in the Report Control Identity field of OPC
Server object properties.
This defines the client for OPC Server and OPC attributes get updated on data
change automatically.
9ARD171384-600 229
b. Select OPC Server object. Right-click and select Properties.
Figure 250. Report Control Identity in CET
230 9ARD171384-600
8. Right-click the Computer Node and select Management to specify the

configuration details (that is, the SCD file and OPC client name) for the OPC
Server.
Figure 251. Open Computer Node Management Window
9. In the Management dialog box, click Update configuration and then click
Reload configuration.
Figure 252. Management Window
9ARD171384-600 231
The configuration (which is actually an XML at the back end) is written to the OPC
Server. The OPC sever starts and requests the IED for all the data defined in
datasets.
10. Right-click the IED and select Online diagnostic.
Figure 253. Online Diagnostic Window of IED
11. When IED is providing the requested data to OPC Server, the status is visible in
Online diagnostic window as shown in Figure 254.
Figure 254. IED Status while OPC Initialization
232 9ARD171384-600
12. If the IED is not connected, the status shown in Figure 255 is visible in the
Online diagnostics window.
Figure 255. IED Status Offline
13. When OPC Server reads all the OPC items, the status is visible in the Online as
Figure 256. IED Online Status in CET
9ARD171384-600 233
14. Check the Online diagnostics for data objects to see the online values. For
example, Figure 257 shows the OPC item values for XCBR.pos.
Figure 257. Online View in CET
OPC Server configuration is complete when the data quality is shown 'GOOD'.
To view the error logs in CET IEC 61850 OPC Server, open the EventLog.txt log
file located in C:\Program Files (x86)\ABB\61850 OPC
Server\OPC_61850\bin\OPCS_IEC61850_instance number\
For more information on Redundancy OPC Server, refer to System 800xA IEC
61850 Connect Configuration (9ARD171387*) Manual.
IEC 61850 OPC Server Alarm and Event Configuration

Perform the following steps to configure IEC 61850 OPC Server Alarm and Event
in 800xA System.
1. Configure the Alarms and Events in CET for 800xA system.
234 9ARD171384-600
2. Refer to the signal list provided by customer to find the signals for which the
customer needs Alarms and Events and with what priority.
Figure 258. Signal List with Alarm and Event Requirements(1)

(1) For illustration purpose, only the IED Name is used. For example: BC101(for REC_670 IED Type), TC102 (for
RET_670 IED Type), in realtime projects the IED Name is in the following format: Substation>Voltage>Bay+ IED.
Name.
3. Map the table as shown in Figure 258 into the CET for Alarm and Event
configuration.
9ARD171384-600 235
4. For example, to generate alarm when Circuit Breaker trips, navigate to the
Circuit Breaker object in CET and select Pos. Open Object Properties
window of Pos.
Figure 259. Pos Data Object Properties
5. Select Indication Event as SwitchPosition. This means alarms and events

should be generated based on circuit breakers position.
236 9ARD171384-600
6. Define the properties of this indication Event SwitchPosition. Select

Computer Node > Process Event Definition > Indication Events >
SwitchPostion.
Figure 260. Object Properties for Switch Position
7. Object properties of event definition indicate the following:

a. When circuit breaker is in state 1 and state 2, that is, only events are
generated when it is either open or closed.
b. When circuit breaker is in state 0 and state 3, that is, both alarms and
events generated when it is in intermediate or in faulty position.
9ARD171384-600 237
c. Acknowledgement required is true, that is, alarms that require

acknowledgement from operator are generated.
The description for each states definition are visible in the alarm list.
d. All these fields can be changed according to the requirement.
8. After mapping customer requirement to object properties of event definition,
the resulting output is as shown in Figure 261.
Figure 261. Alarm and Event Text Customizing
9. Reload this configuration to OPC Server. Now OPC Server generates the
alarms and events for the circuit breaker position. Similarly, define the
configuration for other signals.
For detailed information on configuring Analog Alarms in IED / OPC Server,
System and Process Alarm, SCD Consistency Check, Area Name and
Description, and Event templates Export/Import, refer to System 800xA, IEC
238 9ARD171384-600
Section 2 Substation Engineering 800xA Control and Functional Structure Configuration
800xA Control and Functional Structure Configuration

Goal:
To create object types in Plant Explorer and also to configure 800xA alarm and
event.
Inputs:
SCD file and signal list.
Output:
Object types are configured in 800xA. Live values are visible in control connection.
800xA Alarm and Event is configured, which shows the generated alarms and
events.
Tools used:
CET, IEC 61850 Uploader and 800xA System.
Prerequisite:
OPC Sever configuration is done and OPC Server is up and running.
Workflow:
1. Open the workplace and navigate to Control Structure.
2. Right-click the Root, Domain and select New Object to create a new object.
Figure 262. Creation of New OPC Object
9ARD171384-600 239
800xA Control and Functional Structure Configuration Section 2 Substation Engineering
Sample Figure 263 shows the list of Conducting Equipments configured in

Object Type library.
Figure 263. Object Type Library - Conducting Equipment Objects
240 9ARD171384-600
Figure 264. Library Structure - Alarm Collection Definition
9ARD171384-600 241
Configuring 800xA IEC 61850 OPC Server Object

1. Select IEC 61850 OPC Server object and rename it and click Next.
The OPC Server name should be same as the Subnetwork name.
Figure 265. OPC Server Object Name in Plant Explorer
242 9ARD171384-600
2. Click Add and select a Connectivity Server from the Select Connectivity
Server(s) window as shown in Figure 266.
Figure 266. Connectivity Server Selection
9ARD171384-600 243
3. In the Additional Arguments window, select the OPC Server from Selected
OPC Server, ProgID field and click Create as shown in Figure 267.
Figure 267. OPC Server ProgID Selection
4. OPC Server object is created under Root object in Plant Explorer.
Figure 268. Uploader Aspect on OPC Server Object in Plant Explorer
5. Select the aspect IEC 61850 Uploader.
244 9ARD171384-600
6. Browse the SCD file and select the Subnetwork name in the Uploader window
Ensure that the same subnetwork that is imported in the OPC Server (to which the
OPC data source definition aspect of OPC Server object is pointing) is chosen
here as well.
Figure 269. Standard Tab of Uploader
9ARD171384-600 245
7. Select the library in the Advanced tab.
Figure 270. IEC 61850 Uploader Advanced Tab
For more information on IEC 61850 Uploader Aspect, refer to System 800xA IEC
246 9ARD171384-600
8. After successful upload, click Apply.
Figure 271. Object Upload Success Message
9. Observe that OPC control connection shows the quality of data items as Good
in the Control Structure after upload as shown in Figure 272.
9ARD171384-600 247
All the IEDs, LDs, and LNs created.
Figure 272. Control Connection Aspect Online
Using the control connection data, the faceplates and trends for the signals can be
created.
The Primary Equipment in the Function Structure does not contain any default
Faceplates. Use the available Control Connection properties to create and
customize faceplates.
Faceplates for Primary Equipment are available as an add-on installation
package. For more details, refer to System 800xA Operation Library for
Substation Equipment (2PAA108626*) Manual.
248 9ARD171384-600
800xA IEC 61850 Alarm and Event Server Configuration

Perform the following steps to configure Alarm and Event in 800xA Plant Explorer.
1. Define an Event collector Service. Go to Service Structure in Plant Explorer
and select Event Collector, Service.
2. Right-click Event Collector, Service and select New Object to create a new
service group.
Figure 273. New Event Collector Service Group Creation
9ARD171384-600 249
3. Enter a name for the service group. It is recommended to enter the subnetwork
name as the event collector service group name.
Figure 274. Event Collector Service Group Name
4. Select the newly created service group and select the Service Group
Definition aspect. In the aspect preview, add a service provider.
Figure 275. Service Provider Node Name
250 9ARD171384-600
5. For the service provider, select the Node name in which this service runs (that
is, connectivity server node).
Figure 276. Event collector Service Provider
6. Select the Service Group Definition aspect of the required service group.
Select the Special Configuration tab in the aspect preview.
Figure 277. Special Configuration Tab on SG of Event Collector
9ARD171384-600 251
7. Select the OPC AE server and click Apply.
Figure 278. OPC AE Server Selection
8. In Collection Mapping, click New for alarm collection definition.
Figure 279. Creation of Alarm Collection Definition
A New collection definition is created.
Figure 280. Selection of Alarm Collection Definition
252 9ARD171384-600
9. In Source Object Handling, select Tracking Source Object Interceptor from

Source Configuration list.
Figure 281. A/E Object Handler
10. Select IEC 61850 Connect Source Name Interpreter from the Source
Translator drop-down list.
Figure 282. AE Source Object Handling
9ARD171384-600 253
11. Figure 283 shows the final configuration. Click Upload.
Figure 283. Special Configuration Tab on SG of Event Collector
12. Click OK.
Figure 284. Upload OPC Categories
254 9ARD171384-600
IEC 61850 Alarm Priority Mapping

Perform the following steps to configure IEC61850 Alarm Priority Mapping.
1. Define the Alarm Severity in OPC Server mapping to the Priority in 800xA.
Figure 285. OPC Server Alarm Severity
2. Navigate to Library Structure.
9ARD171384-600 255
3. Select the Alarm Collection Definitions object and select the Alarm Priority
Mapping aspect.
Figure 286. OPC Priority Mapping in Library Structure
4. Map the table according to customers requirement.
Figure 287. OPC Priority Mapping
256 9ARD171384-600
Alarm severity is defined in CET for circuit breaker tripping as 800/600 and for
circuit breaker Operation (open or close) as 400. Together with this mapping table it
results in Alarm of priority 1 when CB trips and an Event of priority 2 when CB
operates.
5. Define the Alarm and Event Configurations in the Library Structure.
Figure 288. Library Structure
6. Create separate configurations for alarms and events.
Figure 289. Alarm and Event Configuration in Library Structure
9ARD171384-600 257
Alarm and Event List Configuration

Perform the following steps to create Alarm and Event list in 800xA Plant Explorer.
1. In the Alarm list configuration, generate the IEC 61850 related alarms.
2. Set the configuration for Alarm list as shown in Figure 290.
Figure 290. Configuration of Alarm List
258 9ARD171384-600
3. Set the configuration for Event list as shown in Figure 291.
Figure 291. Configuration of Event List
4. Create Alarm and Event lists.
Figure 292. Alarm and Event Lists
9ARD171384-600 259
5. Select the corresponding configuration for alarm list and event list.
Figure 293. Selection of Alarm List Configuration
Figure 294. Selection of Event List Configuration
6. When the circuit breaker trips, the alarm appears in the alarm list as shown in
Figure 295.
Figure 295. Alarm List When Fault is Present
260 9ARD171384-600
Section 2 Substation Engineering Summary
7. After resolving the problem triggered by the alarm, the alarm appears as shown
in Figure 296.
Figure 296. Alarm List After Fault Cleared
8. Right-click the alarm to navigate to the source object, that is, Logical Node.
Configuration of MMS communication, and Alarms and Events in 800xA system is
complete.
Summary
In this use case, from the beginning of the engineering workflow, following tasks
were performed:
• Collecting Project inputs
• Configuring CI868 IED in Control Builder
• Configuring Other IEDs
• Generating SCD file using CCT 600/IET600
• PCM600 Engineering
• Control Builder M Engineering
• IEC 61850 Connect Engineering
The procedure to handle complexity at various levels is not explained in this
document. For example, the steps to configure redundant OPC Server or steps to
handle two CI868 modules in an AC 800M Controller.
For advance configuration, refer to AC 800M IEC 61850 Configuration for CI868
(9ARD171385*) and System 800xA, IEC 61850 Connect Configuration
(9ARD171387*) Manual.
9ARD171384-600 261
Summary Section 2 Substation Engineering
262 9ARD171384-600
Section 3 Handling the Changes at Different
Levels of Engineering and Commissioning
The use cases mentioned in this section are applicable for a configured substation
and updates are required during commissioning or run-time.
Following use cases are explained in this section:
1. Addition of a LN, for example, SPGGIO in one of the IED.
2. Addition of new 3rd party IED in the configuration.
3. Addition of new signal through MMS.
4. Addition of new GOOSE signal between AC 800M and an IED.
5. Modification in the IED name and its IP address.
6. Modification in LN name.
7. Replace burnt out IED with a new one.
8. IED application logic change.
9. Alarm and Event related modification - Addition/Deletion, severity change,
Alarm text change.
Use case 1 is referred throughout while discussing all use cases. It is
recommended to understand use case 1 perfectly before proceeding further.
9ARD171384-600 263
Addition of a LN, for example, SPGGIO in one of the IED Section 3 Handling the Changes at
Addition of a LN, for example, SPGGIO in one of the IED

Goal:
How to handle the situation when there is a requirement of adding an extra LN to
the configuration.
Inputs:
Configuration is already done as per use case 1.
Output:
LN is added to the configuration and live values might be seen for this LN.
Tools used:
CCT600, PCM600, CET, Uploader
This use case is applicable incase LN is required to be removed from the
configuration.
Workflow:
1. Take IED “AA1FP1” as an example and add the LN "SPGGIO" to it.
2. Open PCM600 and modify the application. Insert a function block SPGGIO in
the application. Perform the required IO connection to this LN.
Figure 297. SPGGIO
3. Compile and download the application to IED. Close Application window.

4. Generate the new CID file which contains this LN.
5. Export the CID file. Use version numbered folders to store the file.
264 9ARD171384-600
Section 3 Handling the Changes at Different Levels of Engineering and Commissioning Addition of
6. Open CCT600 and at the IED level, import the new CID file. After importing
the CID file, notice the new LN created in CCT.
Figure 298. New LN in CCT
7. This newly created LN is not assigned to the Bay. Drag and drop this LN to the
Bay.
Figure 299. New LN to Bay
Once the CID file is imported in CCT, the GOOSE client configuration is lost for
this IED. Goose client configuration needs to be performed again. Drag and Drop
the IED “AA1A1”as client to GCB configuration. (This was the case before
importing the CID file)
9ARD171384-600 265
Figure 300. GOOSE Dataset Assignment
Figure 301. GOOSE Control Block
8. Follow the same steps of Update data flow > Compile > Generate SCD file,
as described in use case 1.
266 9ARD171384-600
9. The SCD file containing new LN is ready. Import the SCD file in CET for OPC
Server configuration. Notice that new LN appears under the IED.
Figure 302. New Logical Node in Plant Explorer
10. Update the OPC Server configuration and download to OPC.

11. In Plant Explorer, select the IEC 61850 Uploader aspect at OPC Server object
and import the SCD file. The Uploader verifies the differences in previous SCD
file and latest SCD file, and uploads the differences.
9ARD171384-600 267
12. After successful upload, notice the LN created in the Plant Explorer.
Figure 303. LNs in Plant Explorer
13. New LN is now added to the configuration. Check the online values in Control
Connection aspect of this LN. Now, the faceplates and trends can be created.
268 9ARD171384-600
Addition of a New Third Party IED in the Configuration

Goal:
Add a new IED third party IED to the configuration.
Inputs:
Substation is configured as defined in use case 1 and CID file for new IED.
Output:
IED integrated to the configured system.
Tools used:
Control Builder, CCT600, PCM 600 and third party tool.
Workflow:
1. Table 9 describes new IED information.
Table 9. New IED Information
SL. IED
IED Type Vendor Purpose Remark
No. Name
1 BC101 REC670 V1.1 ABB Bay Protection and Control Preconfigured IED
2 TC102 RET670 V1.1 ABB Transformer Protection and Preconfigured IED
Control
3 PC103 AC 800M PM864 + ABB DCS command and control
CI868
4 TP104 387E SEL Over current Protection Preconfigured IED
In this use case, SEL IED is considered. It can also be any third party IED.
9ARD171384-600 269
Addition of a New Third Party IED in the Configuration Section 3 Handling the Changes at Different
2. Notice the Generic IED listed in CCT. Right-click the IED and select Import
SCD File to IED to import the CID file.
Figure 304. Importing CID file for Third party IED
3. After the CID import, notice the LDs and LNs listed under the IED.
Figure 305. LNs of Third Party IED
4. Drag and drop (that is, assign) all the LDs for this IED to the Bay.
5. Complete the required communication engineering, that is, define Dataset,
GCB, and RCB configuration as explained in use case 1. In this example, the
270 9ARD171384-600
GOOSE communication between SEL IED and ABB IED, SEL IED and
CI868 IED, both receiving and sending has been defined.
6. Save, compile, and generate the SCD file.
7. Import the file using IEC61850 Wizard in Control Builder. Download to AC
800M Controller. Notice that CI868 IED has sent GOOSE data to both SEL
IED and ABB IED.
Figure 306. GOOSE Outputs in Control Builder
8. Import the file to PCM 600, open Signal Matrix and download to IED.
9ARD171384-600 271
After import of SCD file in PCM 600, tree structure contains SEL IED as shown in
Figure 307.
Figure 307. Third Party IED in PCM 600
When the Signal Matrix is opened, the message shown in Figure 308 is displayed.
Figure 308. Data Synchronization Report Status Window
272 9ARD171384-600
In Signal Matrix, the entries for SEL IED are also present.
Figure 309. Signal Matrix Window
9. Import the SCD file in the SEL IED configuration tool, and download to SEL
IED.
10. Import the SCD file in CET, and download the configuration to OPC Server.
Figure 310. Third Party IED Logical Nodes
9ARD171384-600 273
11. Import the SCD file in Uploader and create the object types in Plant Explorer.
Figure 311. Object Types in Control Structure
12. The system is configured with third party IED.
274 9ARD171384-600
Addition of New Signal through MMS

Goal:
Customer requirement is that the signal list provided earlier needs small
modifications. The user might require to add new MMS signals to the signal list.
Configure the system for this requirement.
Inputs:
Modified signal list for MMS.
Output:
System is configured as per new signal list.
Tools used:
CCT.
This use case is applicable also in case signals are removed or replaced from the
signal list.
Workflow:
1. Get the modified signal list.
19 Transformer Tap TTP-PA-C-TR1 Tap control Position of TC102 Event 410

Control Position TR1
20 Transformer Voltage TVC-PA-C-TR1 Voltage control TC102 Event 410
Control Position Position of TR1
21 Directional Over TDOC-PA-P- TR1 over current TC102 Alarm and 910
Current Protection TR1 protection status Event
22 Rate of Change of ROF-PA-P-TR1 TR1 ROF protection TC102 Alarm and 810
Frequency status Event
23 Instantaneous OC IOC-PA-P-TR1 TR1 Instantaneous TC102 Alarm and 910
protection Over Current Event
Protection Status
9ARD171384-600 275
Addition of New Signal through MMS Section 3 Handling the Changes at Different Levels of
2. Open CCT and navigate to the LN which contains this signal. This signal is
under LN PHPIOC1 for device AA1FP1, that is, TC102.
Figure 312. IED Data Model Window
3. Click Add to add this signal to the Dataset.
Figure 313. Data Set Entries List
4. Save, compile, and generate SCD file.
276 9ARD171384-600
5. The SCD file containing the new signal in the RCB is ready. Import this SCD
in CET tool for OPC Server configuration and then in Plant Explorer using IEC
61850 Object Type Uploader.
6. Create the faceplates and trend logs which use this signal.
Addition of New GOOSE Signal between CI868 and an IED

Goal:
Customer requirement is that the signal list provided earlier needs small
modifications. The user might require to add a new GOOSE transaction between 2
IEDs. Configure the system for this requirement.
Inputs:
Modified signal list.
Output:
System is configured for new GOOSE transaction.
Tools used:
CCT600, PCM 600, IEC 61850 Wizard.
Workflow:
1. Get the modified signal list.

10 Transformer Voltage Control Position TC102 PC103
11 Directional Over Current Protection TC102 PC103
12 Rate of Change of Frequency TC102 PC103
13 Instantaneous Over current Trip status TC102 PC103
14 Load shed trip command PC103 TC102
9ARD171384-600 277
Addition of New GOOSE Signal between CI868 and an IED Section 3 Handling the Changes at
The last two rows (13 and 14 in the above table) with GOOSE signals intend that
when IED reports overload condition, CI868 sends the trip command.
2. Open CCT600 and add these signals to respective GOOSE dataset. Add only
signal and its quality. Do not add time.
Figure 314 shows the dataset of CI868, that is, PC103.
Figure 314. Dataset Entries in CCT
278 9ARD171384-600
Figure 315 shows the dataset of IED AA1FP1, that is, TC102.
Figure 315. Overtrip Dataset Entries in CCT
3. Update the dataflow. Notice the message in the CCT output window.
Figure 316. CCT Info Log File
24 GOOSE signals are transferred between all the IEDs involved. In this example,
there must be 20 signals (10 actual signals and corresponding 10 quality attribute)
before this update because four more signals (two actual signals and their quality)
are added.
4. Compile and generate the SCD file.
5. Both CI868 and IED must be made aware of this new GOOSE transaction.
First, perform it for CI868.
6. Open Control Builder and import the new SCD file.
9ARD171384-600 279
7. The TreeView Comparator window of the Import Wizard shows the changes.
Figure 317. Wizard Tree View Comparator
8. Click Create.
Figure 318. Click Create
280 9ARD171384-600
9. After the import, the hardware tree structure in Control Builder is updated.
Notice the signals in Hardware editor.
Figure 319. GOOSE Output in Control Builder
Figure 320. GOOSE Input in Control Builder
10. Download the project to AC 800M Controller.
9ARD171384-600 281
11. Go online with the Controller to notice a red triangle on the IED.
Figure 321. Control Builder Showing IED Status
Figure 322. Diagnostic in Control Builder
The red triangle on IED indicates that the IED AA1FP1 is still not aware of new
GOOSE configuration. The configuration revision of GCB is now changed, and new
SCD to IED needs to be downloaded.
12. Open PCM 600, and import the SCD file.
282 9ARD171384-600
13. Open Signal Matrix to see the report as shown in Figure 323. Click Close.
Figure 323. Data Synchronization Report
14. In Signal Matrix, assign the receiver for the new GOOSE signal from CI868.
Figure 324. Signal Matrix Tool in PCM 600
15. Save and download Signal Matrix to IED. After download, IED restarts.
16. In the Control Builder, verify that the red triangle on the IED does not appear.
IED and CI868 IED are in GOOSE communication with new signal.
9ARD171384-600 283
Figure 325. Control Builder Window with Online Status
284 9ARD171384-600
Section 3 Handling the Changes at Different Levels of Engineering and Commissioning
Modification in Name at Different Levels

Goal:
How to handle Substation, Bay or Voltage level name changes. Also there might be
requirements to change IED name.
Inputs:
Substation already configured as per use case 1.
Output:
Substation configured as per changes required.
Tools used:
CCT, PCM 600, CET, Uploader, IEC 61850 Wizard.
Workflow:
1. Take the example of Bay name change and IED name change.
a. Bay name Q1 changed to QBB.
b. IED AA1FP1 name changed to AA1RET670.
2. Open Control Builder and right-click the Bay. Select Rename Bay.
Figure 326. Rename Bay Option
9ARD171384-600 285
Modification in Name at Different Levels Section 3 Handling the Changes at Different Levels of
3. The Bay is changed to new name.
Figure 327. New Bay Name in Control Builder
4. Open Substation Configuration Diagram. Select the IED and change its name
in Properties window.
Figure 328. IED Name Change in Control Builder
5. Export the communication configuration to CCT (that is, Control Builder

database transferred to CCT database).
286 9ARD171384-600
6. Open CCT and notice that the new IED name is effective.
Figure 329. New IED Name in CCT
7. Notice the new Bay name.
Figure 330. New Bay Name in CCT
8. Update dataflow > Compile > Generate SCD.

9. Import the SCD file into PCM 600 project. Before importing the SCD file,
ensure that a back up of PCM 600 project is taken.
9ARD171384-600 287
Modification in Name at Different Levels Section 3 Handling the Changes at Different Levels of
10. Rename the Bay and IED in PCM 600 tree structure.
Figure 331. Renaming IED in PCM 600
11. Import the SCD file.

12. Open the Signal Matrix tool and download (This downloads changes into the
IED).
13. Import the SCD in Import Wizard. Observe the Comparator window. It shows
the changes it finds in new SCD file.
14. Download the Control Builder project into the Controller. After the hardware
initialization of CI868 module, IED and AC 800M starts communicating
GOOSE.
15. Perform MMS configuration. Open the CET. Observe IEDs online diagnostic
status in CET to see the status as IED not connected.
Figure 332. IED Not Connected in CET
This is because the IED name is changed irrespective of the OPC Server.
16. Rename the IED in CET configuration and upload the SCD file.
17. Update configuration and download to OPC Server.
288 9ARD171384-600
18. The status of IEDs in CET appears as OK and Ready.
Figure 333. CET IED Online Status
19. Save the present configuration using AFW import/export tool.

20. Upload the SCD file into Plant Explorer for creating new structure.
The user should not rename the IED. The uploader deletes the old IED from the
structure and inserts the new IED.
Figure 334. IED Renaming
If the name of the Logical Nodes is customized, save the configuration before
importing the new SCD file. The changes may not be recovered after the import.
9ARD171384-600 289
Replace Burnt Out IED with New One Section 3 Handling the Changes at Different Levels of
Replace Burnt Out IED with New One

Goal:
In the running condition, one IED may grow defective for some reasons. A similar
IED is available as spare. Replace the faulty IED with new one.
Inputs:
IP address of IED
Output:
New IED in Operation. Configuration of previous IED in operation is downloaded
to new IED.
Tools used:
PCM 600.
Burning of IEDs occur sometimes. In this case, it is recommended to save the
Application logic, Signal Configuration, Parameters and LCD Graphical display
when IEDs are in operation. If the IED should be replaced, all the settings can be
downloaded to new IED.
Workflow:
1. Set the IP address of new IED same as set for faulty IED. For example, for
IED670 series it can be done through LCD panel.
Settings > General Settings > Communication > TCP-IP configuration > Front
Port
Figure 335. IED IP Address
2. Ping the IED to check if it is online.
290 9ARD171384-600
Section 3 Handling the Changes at Different Levels of Engineering and Commissioning IED
3. Open PCM 600 and download IED application logic using CAP531.
4. Open Signal Matrix and download.
5. Open Parameter setting tool from context menu and select to download all the
parameters.
6. Download Graphical Display.
7. New IED is in Operation now.
IED Application Logic Change

Goal:
There are modifications required in IED application logic.
Inputs:
Substation configured according to use case 1.
Output:
IED configured with new application logic.
Tools used:
PCM 600
The following are the two situations for this use case:
a. Application changes which do not reflect on IEC 61850 communication.
b. Application changes which result in IEC 61850 communication changes.
For situation (b) above, the workflow steps are same as use case 2. In use case 2,
there was modification in application logic of IED which resulted in a new LN on
IEC 61850 side.
9ARD171384-600 291
IED Application Logic Change Section 3 Handling the Changes at Different Levels of Engineering
For more information on the Function block that corresponds the respective IEC
61850 LN, refer to the IED user manual.
Figure 336. IED Documentation in PCM 600
For situation (a), open PCM 600 and then the application logic. Do the required
modification, compile and download to the IED.
Figure 337. IED Logic Change
292 9ARD171384-600
Section 3 Handling the Changes at Different Levels of Engineering and Commissioning Alarm and
In this case, generating new SCD file is not required.
Alarm and Event Related Modification

Goal:
To reconfigure OPC Server with alarm and event related changes.
Inputs:
System configured as per use case 1, and changes related to alarms and events noted
down.
Output:
Alarm and event list reflect the changes.
Tools used:
CET.
Alarm and event related modification could be for example, Severity changes,
Alarm Message change, or addition or deletion of particular signal for alarm
generation.
Workflow:
1. Get the change list.
20 Transformer TVC-PA-C-TR1 Voltage control TC102 Event 410

Voltage Control Position of TR1
Position
21 Directional Over TDOC-PA-P-TR1 TR1 OverCurrent TC102 Event 910
Current Protection Protection Status 410
22 Rate of Change of ROF-PA-P-TR1 TR1 ROF protection TC102 Alarm and 810
Frequency status Event
9ARD171384-600 293
Alarm and Event Related Modification Section 3 Handling the Changes at Different Levels of
2. Select the LN which contains the signal. Open the properties of the signal.
Figure 338. Object Properties Window of Data Object
3. This signal generates an alarm and event based on the Indication event
'TripSignalFromGeneral".
294 9ARD171384-600
Section 3 Handling the Changes at Different Levels of Engineering and Commissioning Alarm and
4. Open Properties of this indication event and execute the changes.
Figure 339. Properties of Indication Event
5. Update and reload the configuration to OPC Server.
9ARD171384-600 295
Alarm and Event Related Modification Section 3 Handling the Changes at Different Levels of
6. In Plant Explorer, change description for this LN and click Apply.
Figure 340. Alarm Description Change
When there is a trip condition for this signal, alarms/events are displayed according
to the configuration.
296 9ARD171384-600
Index
A T
About 7 Terminology 11
About This Book 7
Addition of a LN 264 W
Addition of a New Third Party IED 269 Warning, Caution, Information, and Tip Icons 10
Addition of New GOOSE Signal 277
Addition of New Signal 275
Alarm and Event Related Modification 293
Assumption 8
C
Classification 17
Communication Engineering in CCT 119, 160
I
IED Application Logic Change 291
Inputs Required 22
Introduction 15
M
Methodology/Approach 9
Modification in Name 285
O
OPC Server Configuration 221
R
Replace Burnt Out IED 290
S
Sample Inputs 23
Single Line Diagram 24
9ARD171384-600 297
Index
298 9ARD171384-600
Contact us
Copyright© 2014 ABB.
9ARD171384-600
www.abb.com/800xA
www.abb.com/controlsystems All rights reserved.
Power and productivity

for a better worldTM

9ARD171384-600 - en System 800xa 6.0 IEC 61850 Engineering Workflow

Uploaded by

Copyright:

Available Formats

You might also like

9ARD171384-600 - en System 800xa 6.0 IEC 61850 Engineering Workflow

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9ARD171384-600 - en System 800xa 6.0 IEC 61850 Engineering Workflow

Uploaded by

Copyright:

Available Formats

System 800xA

Power and productivity

System Version 6.0

Copyright © 2003 - 2014 by ABB.

Release: August 2014

About This User Manual

Section 2 - Substation Engineering

Communication Engineering using IET600 ...................................................... 119

Section 3 - Handling the Changes at Different Levels of

• Useful tools for commissioning and testing the IED.

User Manual Conventions

<Feature Pack Content>

Feature Pack functionality included in an existing table is indicated using a

Warning, Caution, Information, and Tip Icons

System 800xA only supports IEC 61850-Ed1(Edition1).

Released User Manuals and Release Notes

IEC stands for International Electrotechnical Commission. IEC 61850 (Ed1) is an

Doma i n Cont r ol l e r AC 8 0 0M Engi ne e r i ng

I EC 6 1 8 5 0 GOOSE & MMS

Figure 1. Sample system configurations for combined 800xA based Process

– CI868 IED for Horizontal Communication with GOOSE/MMS Client

I CD Fi l e for I HMI Subs ta ti on Automa ti on Engi ne e r i ng

Thi r d Par ty CID Fi l e, speci fi ed by

Figure 2. IEC 61850 Engineering Workflow - Step 1 & 2

 Upl oad SCD Fi l e for IEC 61850

CET for IEC 61850 OPC Ser ver

Contr ol Builder for CI 868 IED

PCM600 for ABB IEDs

 Downl oad Confi gur ati on to IED

Figure 3. IEC 61850 Engineering Workflow - Step 3

5. Preconfigured IED files.

ABB Engineer or Project Inputs

Sample Inputs with Signal List

Single Line Diagram

Bay B 1_MC 21_1

Figure 4. Single Line Diagram

Table 1 provides the description of SLD specified by the customer. It is assumed

Table 1. Sub Station Primary Equipment List

SLD of a Primary Equipment

Table 2. IED List (Secondary Equipment)

Table 2. IED List (Secondary Equipment) (Continued)

An ABB Engineer designs the network topology as shown in Figure 5 after

Figure 5. Network Topology

Table 3. GOOSE Signal List

Sl.No. Signal From IED To IED

Table 4. MMS Signal List

Sl No. Signal From IED To IED

Table 4. MMS Signal List (Continued)

Sl No. Signal From IED To IED

Table 5 Lists the MMS Signals with Alarm and Events.

Table 5. MMS Signal List with Alarm and Event

Sl. Process Object Process Object IED Alarm and

Table 5. MMS Signal List with Alarm and Event (Continued)

Sl. Process Object Process Object IED Alarm and

Table 5. MMS Signal List with Alarm and Event (Continued)

Sl. Process Object Process Object IED Alarm and

Configuring CI868 IED