Protection and Control IED Manager 1MRS756450

PCM600 Issued: 11.12.2007

Version: S/18.02.2019

INSTALLATION GUIDE
Related items
PCM600 Ver. 2.10 Installation DVD

PCM600 Ver. 2.10 Setup can be downloaded from https://www143.abb.com/SoftwareLibrary

Content on DVD
• PCM600 Setup
• PCM600 Ver. 2.10 Readme file
• PCM600 Ver. 2.10 Installation Guide
• PCM600 Ver. 2.10 Product Guide

PCM600 Setup includes the following software:

• Protection and Control IED Manager PCM600 Ver. 2.10
• Generic IEC 61850 IED Connectivity Package Ver. 2.5
• Wavewin Tool for Disturbance Analysis
• PCM600 Update Manager

System requirements PCM600 requires Microsoft SQL Server 2014

Operating system: Windows 8.1, Windows 10 (see
note about Windows 10), Windows Server 2012 R2,
Windows Server 2016, Windows Server 2019
Windows must be up-to-date to support the
required runtimes and software components
required by PCM600. It is recommended to run
Windows update before installing PCM600.
Hardware requirements,
minimum/recommended:
Physical RAM memory: 8 GB / 16 GB
Free hard disk space: 4 GB / 8 GB
If working with large projects, it’s recommended to
have 24 or 32 GB of physical RAM.
Windows compatible pointer (e.g. mouse)
How to install PCM600 Ver. 2.10
a) DVD Installation:
Insert the installation DVD into the DVD-drive. If the
setup doesn’t start automatically, execute
setup.exe in the root folder of the installation DVD.
Express edition. The correct SQL Server instance
will be installed automatically. If the correct SQL
Server instance is already installed, PCM600
installation will skip this step.
PCM600 installs .NET 4.8 if required. The .NET
Framework might require a reboot.
Installation requires administrator rights. In all
versions of Windows, it might be necessary to
switch off or configure antivirus software to not
block the installation and operation of PCM600 (e.g.
McAfee Host Intrusion Prevention).
Uninstalling
PCM600 can be uninstalled from Apps and
Features (Programs and Features). The name is
“ABB Protection and Control IED Manager
PCM600”. Some included programs and runtimes
can only be uninstalled separately (they could be
used by other programs). Examples are ABB IED
Connectivity Packages, Wavewin ABB and ABB
PCMSERVER2014 SQL Instance.
Windows 10

b) Downloaded from ABB Software Library: When upgrading operating system from an earlier
After free registration, you will get an email with a Windows version to Windows 10 with PCM600
link to download the executable installation. Start already installed, an additional reboot might be
the installation and follow the instructions. required to start all needed services.

After the installation starts, select the needed soft-

ware components and follow the instructions to
complete the installation.

1
 Protection and Control IED Manager 1MRS756450
PCM600 Issued: 11.12.2007
Version: S/18.02.2019

Prerequisites for using PCM600 Ver. 2.10

During installation, the user logged in is
To operate with PCM600, there must be at least one
automatically added to “PCMSERVER2014
IED Connectivity Package installed and selected to
Users” group. If additional users are required, they
be used with PCM600 Ver. 2.10.
must be added to the user group manually. This can
be done by using lusrmgr.msc (“Local Users and
License Groups (Local)”). This function provides a
possibility to add both local and network user
There is no license required for PCM600 Ver. 2.10.
accounts to PCMSERVER2014 Users Group.
IEC 61850 communication configuration
In some cases, the user needs to logout and login
again for all functionality to be available to PCM600
Separate IEC 61850 communication configuration
due to the user group addition.
software can be purchased through ABB sales
representatives.
SQL Server 2014 Express
Previous versions of PCM600 PCM600 2.8 and later versions are using Microsoft
SQL Server 2014 Express. This instance is
PCM600 2.10 can be installed in parallel with a
separate from and doesn’t interfere with the SQL
previous version. If you only want to use PCM600
instance in PCM600 2.7 and older versions that use
2.10, you should uninstall the previous version of
SQL Server 2008 Express. The two instances can
PCM600 before installing PCM600 2.10. It is
co-exist. It is however recommended to install the
recommended to install PCM600 versions in
older SQL Server before the newer one; thus,
ascending order. PCM600 2.7 and older shouldn’t
installing PCM600 2.7 and older versions before
be attempted to install on top of PCM600 2.10.
installing PCM600 2.8 and later versions is
recommended.
If PCM600 2.8 or 2.9 is installed on top of PCM600
2.10, a warning will be shown that the SQL Server
SQL Server 2016 and later versions
was found, but the data directory is different. The
change of data directory has been done by purpose PCM600 is not compatible with SQL Server 2016 or
in PCM600 2.10 and this warning message can be later versions of the SQL Server. PCM600 SQL
ignored. Server 2014 instance should not be upgraded to
SQL Server 2016 or later.
If PCM600 2.5 or an older version is uninstalled
after PCM600 2.10 has been installed, PCM600 Distributed setup
2.10 could be broken and must be repaired. This
PCM600 2.10 supports having SQL Server and
can be done through Control Panel and Uninstall a
PCM600 installed on different machines. It allows
Program (Apps & Features in Windows 10).
using PCM600 projects from multiple PCs, but
multiple machines can’t open same project at same
When opening projects in PCM600 2.10 that have
time. Using distributed setup has effect on
been created with previous versions of PCM600,
performance because SQL Server is accessed over
the projects will be converted automatically. After
the network.
project conversion, the projects can't be opened
with older PCM600 versions anymore.
To make a distributed installation select “Options” in
PCM600 installation wizard. First PCM600 should
To migrate IED 670 configuration from PCM600
be installed on server machine using option “Install
Ver. 1.5 to 2.10 (the whole PCM600 project
only SQL Server”.
including all IEDs in the project), please refer to the
document “1MRG002586 - Configuration Migration
After server installation you need to share folder
for 670 series in PCM600 User Manual", that can
defined by “PCMDATADIR” system environment
be found on the 670 series ConnPack DVD.
variable. If you have installed PCM600 without
specifying the path manually from command line, it
SQL Server access rights
is “[drive]:\ProgramData\ABB\PCMDatabases\” by
In PCM600 2.8 and later versions, data security has default.
been enhanced, and for that reason every Windows
user using PCM600 must be given privileges to Share this folder with full privileges for Windows
PCM600 project data. These privileges are given by user group “PCMSERVER2014 Users” on server
adding the Windows user to the new machine. Use the name “PCMDataBases” for the
“PCMSERVER2014 Users” user group. shared folder. Each Windows user using PCM600
2
 Protection and Control IED Manager 1MRS756450
PCM600 Issued: 11.12.2007
Version: S/18.02.2019

must be added to “PCMSERVER2014 Users”

group, refer to PCM600 Cyber Security Deployment
Guideline.

Then PCM600 can be installed on client machine.

Select “Options” and “Install only PCM600” in the
PCM600 installer. Give the IP address or computer
name of the server machine. It is assumed that the
shared folder on server is named “PCMDataBases”.

If shared folder name is something else than

“PCMDatabases”, you need to edit the System
Environment variable PCMDATADIR on the client
and set the correct path to the server folder. Note
that the path must be given as UNC path (e.g.
\\server\PCMDatabases\) when using distributed
setup.

In order to use the Scheduler service on the client

machine, you also need to change the Log On
account for the service. This can be done from
Services.msc, PCMSchedulerService_v210 and
Log On tab. The account needs to be the same that
is using PCM600.

To avoid time synchronization related problems,

please make sure that all PCM600 machines have
same system time.

Disclaimer
The information in this document is subject to change without
notice and should not be construed as a commitment by ABB
Oy. ABB Oy assumes no responsibility for any errors that may
appear in this document.

© Copyright 2020 ABB Oy

All rights reserved.

Trademarks
ABB is a registered trademark of ABB Group. All other brand or
product names mentioned in this document may be trademarks
or registered trademarks of their respective holders.