—

RELION® 670 SERIES

Data Migration Instruction

PCM600 version 1.5 configuration to
PCM600 version 2.4 SP1 (or later)
configuration
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Contents

About These Instructions........................................................................................... 3

General ...................................................................................................................................... 3
Use of Warning, Caution, Information and Tip Icons .................................................................. 3
Document Conventions .............................................................................................................. 4
Terminology ............................................................................................................................... 4
1. Introduction ......................................................................................................... 5
1.1 General overview............................................................................................................... 5
2. Product Overview ............................................................................................... 5
2.1 Features of the Product ..................................................................................................... 5
2.2 Features List...................................................................................................................... 5
2.3 Intended Audience / Users / Groups.................................................................................. 5
3. Administration & Configurations Details ......................................................... 6
3.1 Application Framework / Product Architecture................................................................... 6
3.2 User Interface .................................................................................................................... 6
3.3 Offline Migration Process .................................................................................................. 7
3.4 Online Migration Process ................................................................................................ 14
3.5 Functionality .................................................................................................................... 21
3.6 Performances, Fine Tuning and Optimizations................................................................ 22
 Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

About These Instructions

General

This instruction describes the process of migrating configurations created in PCM600 Ver.
1.5 to PCM600 Ver. 2.x in detail. For latest information see also the Release Notes of IED
Connectivity Packages ver. 2.1.5 for Relion® 670 series (1MRG008089).

Use of Warning, Caution, Information and Tip Icons

This publication includes Warning, Caution, and Information where appropriate to point out
safety related or other important information. It also includes Tips to point out useful hints to
the reader. The corresponding symbols should be interpreted as follows:

Caution icon indicates important information or warning related to the concept

discussed in the text. It might indicate the presence of a hazard, which 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

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, comply fully with all Warning and
Caution notices.
 Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Document Conventions

This section should explain about the Conventions used and other value added information
that are relating to this Documentation.

Terminology

Term Meaning
ACT Application Configuration Tool
CDS Configuration Data Server
CMT Communication Management Tool
ConnPack Connectivity Package
CP Common Platform
DHT Disturbance Handling Tool
EVT Event Viewer Tool
GDE Graphical Display Editor Tool
HWT Hardware Configuration Tool
IED Intelligent Electronics Device
LHMI Local Human Machine Interface
MON Signal Monitoring Tool
PCM600 Protection and Control IED Manager
PST Parameter Setting Tool
SMT Signal Matrix Tool
SCL Substation Configuration Language
GCB GOOSE Control Block
GOOSE Generic Object Oriented Substation Events
RCB Report Control Block
 Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

1. Introduction

1.1 General overview

Because the format of data used by PCM600 ver. 2.x and newer versions is different
from the older versions, there is a need for a Data Migration utility that can migrate data
from PCM600 ver. 1.5 to PCM600 ver. 2.x. The Data Migration functionalities is bundled
into a library to be used by PCM600 ver. 2.x and IED Connectivity Packages ver. 2.1.5
for Relion 670 series and this is embedded in the IED ConnPack ver. 2.1.5 for 670
series installation package.

2. Product Overview

2.1 Features of the Product

 Migration of the Configuration data from PCM600 Ver.1.5 file.
 Migration of the Parameter data from PCM600 Ver.1.5 file.
 Migration of the Graphical data from PCM600 Ver.1.5 file.
 Migration of the Signal Matrix data and DNP3 point list from PCM600 Ver.1.5
file.
 Migration of the Configuration data from a CAP 531 Configured IED.
 Migration of the Graphical data from CAP 531 Configured IED.
 Migration of the Signal Matrix data from CAP 531 Configured IED.
 Migration of the Parameter data from CAP 531 Configured IED.

2.2 Features List

 SMT with Binary Output, Binary Input and Analog Input Migration
 PST with changed value
 CAP to ACT Conversion
 GDE Migration
 Goose Migration in offline scenario
 DNP 3.0 migration in the offline scenario
 Online Migration
 LED Handling

2.3 Intended Audience / Users / Groups

 System and Commissioning Engineers: use the PCM600 to configure the

IEDs and commission them. The Engineers could use the DMT for importing a
file exported from PCM600 Ver.1.5 and then edit the configuration, signal
mapping etc and save it back in the new format.
 Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

3. Administration & Configurations Details

3.1 Application Framework / Product Architecture

DMT operates in two scenarios which are Online and Offline.

Offline scenario – This scenario comes into picture, when user tries to import
PCM600 1.5 project in PCM600 2.x. PCM600 1.5 exports the IED information into a
file. PCM600 2.x runs in 2 phases: Import and Conversion. Whenever the user tries to
open an old file in PCM600 2.x, during the Import phase it imports type data and then
invokes the DMT. The DMT copies the necessary files which are available only during
this phase for processing in the next phase. In the conversion phase, the DMT is
invoked again. This is when the actual conversion takes place. The DMT reads and
interprets the information present in the PCM600 1.5 files. It retrieves the required
information and populates the object model by utilizing the available instance data. It
retrieves any missing instance data from the IED modules.

Online scenario – Online scenario is invoked when IED that has been configured
using PCM600 1.5, is being read to PCM600 2.x. In this scenario, ConnPack will
invoke the Data Conversion Layer of DMT to convert the data to PCM600 2.x format.

3.2 User Interface

The Data Migration Tool is invoked by PCM600 during offline migration and it is
invoked by ConnPack during Online migration. No separate user interface exists for
Data Migration Tool itself.

Error Messages: The standard PCM error messages are used

Other Messages: The standard PCM message interface is used for other informative /
debug messages.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

3.3 Offline Migration Process

If the project is created with the PCM600 Ver.1.5 and is opened in PCM600 2.x , the
project conversion Wizard is opened. After the project is converted, it can be used
with the latest version of PCM600.

When the project conversion wizard is open, follow the instructions and click next.
After reviewing the summary, click next to continue the conversion. During the
conversion, the upper progress bar shows the total progress and the lower progress
bar shows the progress of the current phase. Finish the conversion and close the
dialog by clicking finish.

Step 1: Select the PCM600 1.5 Project to Migrate.

Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

With this Phase 1 of the migration is completed.

Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Step 2: Once the project is imported, double-click the imported project. Project
Conversion Wizard will open and follow the steps by clicking the next button.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Step 3: Review the summary and click next.

Step 4: Conversion started.

Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Step 5: Click finish button to complete the conversion.

NOTE!
Before reading or comparing configurations with an online IED, you should
always write the migrated configuration to IED using PCM600 2.x ().
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Known issues and Limitations for Offline Migration

1. Importing of PCM600 1.5 pcmi files is not supported, only PCM600 1.5 pcmp files will
be considered for Migration.

2. Cancelling the operation during the Conversion is not supported in PCM. Currently
the cancel operation is only supported before the conversion is started.

3. When creating new IED in a migrated project, change SCL technical key from
Substation to bay level according to the SCL specification.

4. Placement of FB will be in the same page as of CAP531 in PCM600 2.x ACT, but not
in the same co-ordinates.

5. If the PCM600 1.5 Project has LDCM Analog Module, then after migration it will
appear in the first main application.

6. PCM600 2.x and thereafter supports only one substation. If there are multiple
substations in the PCM600 1.5 project, please select the substation you want to use.

7. After Offline migration, the user has to write the migrated configuration from PCM600
2.x to the IED before performing any compare/read/write operation.

8. After migration the maximum dataset attributes is set to 330, if any dataset contains
more than 330 dataset attributes, the user has to delete them manually. Re-migrate
the project. If the SCD file import fails during migration, the user has to export the
PCM600 2.x SCD file and change the maximum dataset attributes to 330 and re-
import the SCD file.

9. Caption of IEDs in PCM600 Ver.1.5 project should be unique before migrating.

10. After migration IEC 61850 model can have some differences.

11. If you get the following error in PCM600 output window before read/write “Item no
longer available in the server address space”. Update the OPC Server Configuration
manually in the communication structure.

12. After migration from PCM600 Ver.1.5 to PCM600 Ver.2.x, in CMT, the SPGGIO
output signal “OUT” will appear in place of “IN” of PCM600 Ver.1.5.

13. After migration from PCM600 Ver.1.5 to PCM600 Ver.2.x, for non 61850 functions, if
the signals are specified in the CMT rules, then those will appear in the mapped/non
mapped signals list.

14. After migration from PCM600 Ver.1.5 to PCM600 Ver.2.x, for non 61850 functions, if
the complete function Block is specified in the CMT rules, for signals to appear in the
mapped/non mapped list, those signals must be connected.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

15. In CMT, the UserDefined Names on DNPFREC FB is not propagated from PCM600
Ver.1.5 to PCM600 Ver.2.4 SP1

16. LED Handling is different between PCM600 Ver.1.5 and PCM600 Ver.2.x. In PCM600
Ver.1.5, if the user has connected input signal to LED in Binary Input tab, in PCM600
Ver.2.x, it will appear under Binary Output tab.

17. In PCM600 Ver.1.5, SMT, Goose Tab, the "q" needed to be explicitly connected and
was visible. In PCM600 Ver.2.x, this is connected automatically and is not visible in
Goose tab.

18. If the project in PCM600 Ver.1.5 has been created using different layout other than
the default one, during migration the DMT will take only the default layout, if CAP531
is not installed in the system. Due to this there may be some difference in the number
of pages and FB placement between CAP531 and ACT.
 Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

3.4 Online Migration Process

When an IED has been configured using PCM600 1.5 and is being read in PCM600
2.x, the ConnPack will identify that the IED has been configured using old version of
PCM and it invokes the DMT. The user will not get any dialog boxes during the
conversion since the conversion is happening in the background and also no user
interaction is required for online migration. The user can get to know status of the
migration in the PCM600 2.x output window.

Step 1: Configure an Online IED.

Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Step 2: Read the Configuration from IED.

Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Step 3: Online Migration is started.

Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Step 4: Online Migration is completed.

Step 5: Before doing a compare configuration in ACT, the user will be informed to
write the migrated configuration to IED using PCM600 2.x.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Known Issues and Limitations for Online Migration

1. Goose Migration is not supported in Online scenario since PCM600 Ver. 2.x doesn’t
support the read of the IEC 61850 data.

2. Default Main Application will be created in Online scenario.

3. Writing configuration to IED using PCM600 Ver.1.5 to an IED configured with

PCM600 Ver.2.x and read the configuration from IED will start the online migration
but not work properly. This use case is not supported.

4. Placement of FB will be in the same page as of CAP531 in PCM600 Ver.2.x ACT, but
there might be some overlap of FBs and variables

5. If the IED has LDCM Analog Module in it, after online migration the LDCM Transmit
FB will appear in the first main application.

6. After Online migration, the user has to write the migrated configuration from PCM600
2.x to the IED before performing any compare/read/write operation.

7. If the project in PCM600 Ver.1.5 has been created using different layout other than
the default one, during migration the DMT will take only the default layout, if CAP531
is not installed in the system. Due to this there may be some difference in the number
of pages and FB placement between CAP531 and ACT.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

Known Issues and Limitations for IEC 61850 and System Engineering

Below cases results in SCL model changes after migration from PCM600 Ver. 1.5 to
PCM600 Ver.2.x.

1. In PCM600 Ver.1.5 the StatUrg dataset are named as StatUrg_A, StatUrg_B.... When
a project is migrated from PCM600 Ver.1.5 to Ver.2.x, the dataset StatUrg will be
created and some signals will be moved to this dataset. However, the corresponding
RCB will not be created which the user has to add it manually.

2. In PCM600 Ver.2.x SCL file, additional DAIs such as vendor, q, t will be added to
LPHD LN.

3. In PCM600 Ver.2.x SCL file, additional DOIs such as Health, NamPlt are added to
some LN like CMMXU etc.

4. There is a change in the internal SCL format between PCM600 Ver.1.5 and
PCM600 Ver.2.x. Due to this re-engineering is required if the user uses IEC
61850 interface on the IED. This means that the SCL information (ICD, CID)
should be exported from PCM600 Ver.2.x after migration and imported to the
System Engineering Tool. System re-engineering needs to be done in the
System Engineering Tool for data flow consistency.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

After this a new updated SCD shall be generated and exported from System
Engineering Tool, which shall be loaded to all IEC 61850 devices (servers and
clients) that exist in the system. The original scd file of PCM600 Ver.1.5 shall
never be used anymore.

Export ICD/CID from

PCM600 Ver.2.x

Import into System

Engineering Tool

Update dataflow in System

Engineering Tool

Export SCD from System

Engineering Tool

Import SCD into PCM600

Ver.2.x

Update all IEDs (Servers and

Clients in S/S &
Communication Structure)

The above steps are not required if the user uses only PCM600 as the engineering
tool.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

3.5 Functionality
The DMT converts the following:

1. Configuration Data
a. Logical Data
DMT will migrate the logical data with respect to configuration. IED configuration
specific files, the types and instances of function blocks used, and the
connections between them. In PCM600 Ver.1.5, the CAP is used for configuring
the IEDs, whereas in PCM600 Ver.2.x, the ACT is used.
b. Graphical Data
DMT will migrate the graphical data comprising the exact layout of function blocks
and the connections, variables etc.

2. Signal Matrix (I/O) Data

DMT will migrate the signal matrix data. Signal matrix specifies the connections
between the function blocks and hardware modules or GOOSE inputs. The input
channels on the hardware modules will be connected to the input signals on the
function blocks, and the output signals on the function blocks will be connected to
the output channels on the hardware modules. The Data Attributes on the
GOOSE inputs could also be connected to the input signals on the function
blocks.

3. Graphical Display Data

DMT will migrate graphical display data, which is related to display on the HMIs.
This comprises several pages with different nodes (electrical / electronic
component symbols) and connections between them, and captions.

4. Parameters Data
DMT will migrate parameters data. The behavior of function blocks and hardware
modules is determined by different parameters. All these parameters have default
values based on the parameter type. Only those parameters which have their
values modified are saved and will be involved during migration.

5. CAP 531-Configured IED

When ConnPack reads from an IED, it obtains the connections in the IED using
SPA codes. It also obtains some files from the IED. Once it is determined that the
IED was configured using PCM600 Ver.1.x, it invokes the DMT and provides the
read data.
The DMT verifies that the files obtained are valid by checking it against the data
directly read by ConnPack from the IED. The DMT will obtain graphical
information from the files provided by the ConnPack and provide this to the ACT
along with all the connections. It will obtain the HMI display information and
provide this to the CDS.
Data Migration June 15, 2017
Instruction 1MRG000507
Rev. I

3.6 Performances, Fine Tuning and Optimizations

A response time of 30 seconds per IED is expected when the DMT is invoked by
the PCM600.
—
ABB AB
Grid Automation Products
721 59 Västerås, Sweden
Phone: +46 (0) 21 32 50 00

abb.com/protection-control
1MRG000507-UEN

© Copyright 2017 ABB. All rights reserved. Specifications

subject to change without notice.