8VZZ001288T2120 A en SPlus Operations 2.1 SP2 Release Notes

—
PO WE R GE NE R ATI ON & WATE R
ABB Ability™ Symphony® Plus

S+ Operations 2.1 Service Pack 2
Release notes
—
PO WE R GE NE R ATI ON & WATE R
ABB Ability™ Symphony® Plus

S+ Operations 2.1 Service Pack 2
Release notes
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 intellectual 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 com-
mitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected and to communicate infor-
mation and data through network interfaces, which should be connected to a secure net-work. It is the sole
responsibility of the system/product owner to provide and continuously ensure a secure connection between
the product and the system network and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not limited to,
the installation of firewalls, application of authentication measures, encryption of data, installation of antivirus
programs, and so on, to protect these products, the network, its system, and interfaces against security
breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information.
ABB performs functionality testing on the products and updates that we release. However, system/product
owners are ultimately responsible for ensuring that any product updates or other major system updates (to
include but not limited to code changes, configuration file changes, third-party software updates or patches,
hardware change out, and so on) are compatible with the security measures implemented. The system/ prod-
uct owners must verify that the system and associated products function as expected in the environment in
which they are deployed.
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 hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission 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 2014/30/EU and in Low Voltage Directive 2014/35/EU.
TRADEMARKS
Symphony and Symphony Plus are registered or pending trademarks of ABB S.p.A.
Ability is a trademark of ABB.
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2011-2018 ABB.
All rights reserved.
Release: October 2018
Document Number: 8VZZ001288T2120
Revision: A
I N T R O D U CT I O N O VE R VI E W
Table of Contents
1 INTRODUCTION ........................................................................................................................... 2
1.1 Overview ............................................................................................................................ 2
1.2 Executive Summary .......................................................................................................... 3
1.3 Getting Access to 2.1 Service pack 1 ................................................................................ 3
1.4 License change.................................................................................................................. 3
1.5 Revision Record ................................................................................................................ 4
1.6 Compatibility.................................................................................................................... 4
1.7 Requirements ....................................................................................................................5
1.7.1 General thoughts on hardware requirements ................................................5
1.7.2 Summary Table .................................................................................................6
1.7.3 Software Requirements Details.......................................................................6
1.7.4 Hardware Serverless Configuration ................................................................ 7
1.7.5 Hardware Server based Configurations.......................................................... 7
1.7.6 Hardware clients .............................................................................................. 8
2 DATA SHEET ................................................................................................................................ 9

2.1 Serverless architecture.....................................................................................................9
2.2 Server based architecture ................................................................................................9
2.3 Version Compatibility .......................................................................................................9
2.3.1 Harmony ............................................................................................................9
2.3.2 AC800M .............................................................................................................9
2.3.3 Freelance ...........................................................................................................9
2.4 Features: Sizes ..................................................................................................................9
2.5 Features: Details ............................................................................................................. 19
3 Virtualization.............................................................................................................................25
3.1 Number of Symphony Plus Servers to provide the required DCS
function ........................................................................................................................... 25
3.2 Redundancy architecture ............................................................................................... 27
3.3 Network connectivity .....................................................................................................28
3.4 Equipment Lifecycle .......................................................................................................28
3.5 Equipment Maintenance ................................................................................................ 29
3.6 Cybersecurity ................................................................................................................. 30
3.7 Virtual System Architectures – Matching Physical Machines Resources ................... 30
3.8 Virtual System Architectures – Resource Pooling Architecture ................................... 32
3.9 Summary and Conclusion...............................................................................................36
4 MODIFICATIONS IN THIS RELEASE .......................................................................................... 37

4.1 New Functions ................................................................................................................ 37
4.1.1 SOE Configuration Tool.................................................................................. 37
4.1.2 Diagnostics Support of SPENM01 ................................................................. 37
4.2 Improvements ................................................................................................................. 37
4.2.1 Extended Redundancy....................................................................................38
4.3 Fixed Problems ............................................................................................................... 41
4.4 Known Problems and Workarounds .............................................................................. 51
5 INSTALLATION ...........................................................................................................................61
5.1 Installation....................................................................................................................... 61
5.2 Upgrading ....................................................................................................................... 61
5.3 Backup and Restore ........................................................................................................ 61
8 VZ Z 0 0 12 8 8T 2 12 0 A 1
OVE RVI E W I NT RO DUC TI O N
1 INTRODUCTION
This document represents the release notes for S+ Operations 2.1 Service Pack 2. This docu-
ment provides a brief overview on functionality. It enumerates known problems encountered
in the final testing of this product release and identifies workarounds that help overcome
those problems. The document contains additional notes that may be valuable to customers
and service personnel working with the product.
1.1 Overview
Operator effectiveness is fundamental to a plant’s performance. However, with fewer plant
operators, a generational shift in the operator workforce, and increasing complexity of plant
operations, this is becoming ever more challenging, but not insurmountable. Symphony Plus,
with its intuitive, easy-to-use human machine interface (HMI), leads operators to greater
awareness, faster response and better decisions. S+ Operations is designed for high perfor-
mance in every aspect involved: human machine interface, integrated operations, seamless
life cycle management, information management, alarm management, security, process opti-
mization, and flexible, scalable fault tolerant design.
Figure 1-1: Power Explore Overview
Defined for high performance

S+ Operations provides operators with distraction free, state-of-the-Art, process information
and access.
Integrated operations
S+ Operations seamlessly integrates all plant devices and systems.
Seamless life cycle management

S+ Operations allows for seamless and incremental integration of new products, technology
and functionality without the time and expense of re-engineering and retraining.
2 8V ZZ 0 01 2 88T 2 12 0 A
I N T R O D U CT I O N E XE C UT I VE S U M M A R Y
Information management
S+ Operations transforms data into meaningful information and presents it in intuitive user
specific desktop displays.
Alarm management
S+ Operations superior integrated alarm management system includes the industry’s leading
EEMUA191 – compliant alarm management analysis system.
Security
S+ Operations provides users with a secure and reliable operations environment with its
built-in security features.
Process optimization
S+ Operations combined with OPTIMAX® Performance Package improves over all plant
productivity.
Flexible, Scalable, fault tolerant design

S+ Operations unique system architecture easily adapts to any power and water applications.
1.2 Executive Summary

S+ Operations is the Symphony Plus Human System Interface for the supervision and opera-
tion of Symphony based control systems.
This release adds support for Windows 10 LTSC 2016 Operating System. It also includes reso-
lution to several known issues along with remaining bug fixes of S+ Operations 2.0.x line for
Harmony. Refer to Fixed issues section for more details.
This release supports various connectivity’s but does not include support for Melody, Con-
tronic E, CLIF function codes of Harmony, Procontrol 13 and Procontrol 14.
AC800M Connectivity is supported. This release also reintroduces the support for Freelance
Connectivity. All generic drivers of previous connectivity such as OPC, Modbus, IEC 104, IEC
61850 etc. are supported.
Applications such as the Shiftbook is reintroduced in this release, while the features GIS and
Takadu integration are not included.
This release also supports PRP Duo Driver for HMI Network redundancy. For details on Duo
Driver please refer the release note (1KHL506789).
1.3 Getting Access to 2.1 Service pack 1

The distribution of S+ Operations 2.1 Service Pack 2 is available by either ordering the Media
pack from the feeder factory or by download from ABB Library (internal)/Solutions bank (ex-
ternal).
This version can be used as an upgrade pack for existing versions of 2.x or 1.1 or as a full in-
stallation of S+ Operations where no pre-installation of previous versions of S+ Operations is
required. The full installation of 2.1 Service Pack 2 is delivered as an ISO image. Please take
into consideration that the image for download is large.
1.4 License change

S+ Operations 2.1 Service Pack 2 is available free of charge to all valid Sentinel subscription
holders. If upgrading an existing project from S+ Operations 1.1.x or 2.x to this release a new
license file is required.
8 VZ Z 0 0 12 8 8T 2 12 0 A 3
RE VI SIO N RE CO RD I NT RO DUC TI O N
1.5 Revision Record

Rev. No. Description Date
A First version is published for October 2018

S+ Operations 2.1 Service
Pack 2 release
Table 1-1 Revision Record
1.6 Compatibility
The compatibility related information with respect to S+ Operations software are as follows:
– This release is compatible with S+ Engineering 1.4 provided installed in different ma-
chines, and cannot be installed in the same machine
– This release is compatible with S+ Engineering 2.1 provided installed in same machine or
different machines.
4 8V Z Z 0 01 2 88T 2 12 0 A
I N T R O D U CT I O N RE Q UI RE M E NT S
1.7 Requirements
1.7.1 General thoughts on hardware requirements
The hardware requirements for S+ Operations are dependent on the following factors:
– Number of tags in the HSI real-time database
– Total number of clients
– Special applications
– Number of transactions/sec, configuration of signals, process dynamic, etc.
– Expected response time for the users
The table below provides a summary of hardware configurations that were found to produce
good performance during the testing of S+ Operations.
Note: It is not allowed to run any other non-Symphony Plus software packages on the below
mentioned configurations to ensure the stability, security and performance of the system.
S+ Operations computer recommendations place a high emphasis on performance in order

to allow the system’s hardware to meet the needs of future releases of S+ Operations with-
out the need for exchanging hardware components. Lower performance hardware may pro-
vide adequate results but this hardware has not been tested and it does not ensure perfor-
mance provisions for the future.
Hard disk requirements:

RAID system (RAID 1: mirroring) can improve the computers reliability. Please keep in mind
that RAID disks can slow down the computer’s performance in particular if no hardware RAID
controller is used. It is recommended to use dedicated hardware RAID controllers. When using
RAID 5, performance improvements are seen only if a high number of disks are used (at least
8 discs are required).
History server:
For the History Server in large applications and in those demanding high historian perfor-
mance, it is required to use separate disks for programs, separate disks for the alarm/event
database and separate disks for real-time value database. In case a RAID is used this means 3
independent RAID 1 with at least 6 disks in total or a RAID 5 with at least 8 disks. For high
speed historians SSD disks shall be used. Further performance improvements can be archived
using separate RAID 10 for each of the databases.
Fast display call-up times:

If fast display call-up times are expected than it is essential to use high performance opera-
tions networks (at a minimum 1 Gbit) and high CPU cycle time (> 3 GHz) for operator PCs and
servers. Please follow CPU suggestions that by the release of the product were tested for
high performance. SSD disks also for clients will speed up the performance on startup and
also call-up times.
CPU recommendation for fast call-up time use:
- For operator workstations or Serverless:

e.g. Intel Core Intel Xeon E3-1225 v5, 3.3Ghz or Intel® Xeon® Gold 5122, 3.6GHz
- For large servers:

e.g. Intel® Xeon® Gold 5118, 2.3GHz
8 VZ Z 0 0 12 8 8T 2 12 0 A 5
RE Q UI REM E NT S I NT RO DUC TI O N
1.7.2 Summary Table
HSI Server History Serverless Operator Full Office Application

Server Client Client Client Server
CPU Small: Intel® Small: Intel® Intel® Xeon® Intel® I3 proces- Small: Intel®
Xeon® E3- Xeon® E3- Silver 4112, Xeon® Sil- sor Xeon® E3-
1270 v6, 1270 v6, 2.6GHz or ver 4112, 1270 v6,
3.8GHz 3.8GHz, In- Intel Xeon 2.6GHz or 3.8GHz, Intel®
Large: In- tel® Xeon® E3-1225 v5, Intel Xeon Xeon® Silver
tel® Xeon® Silver 4114 3.3Ghz E3-1225 v5, 4114 2.2GHz
Silver 4114 2.2GHz or In- 3.3Ghz or Intel®
2.2GHz or tel® Xeon® Xeon® Gold
Intel® Gold 5118, 5118, 2.3GHz
Xeon® Gold 2.3GHz
5118,
2.3GHz
RAM Small: 8 GB 8 GB Small: 8 GB 8 GB 4 GB Small: 8 GB

Large: 16 Large: 16 GB Large: 16 GB
GB
OS Windows 10 Windows 10 Windows 10 Windows Windows Windows 10

LTSC 2016: LTSC 2016: LTSC 2016 10 LTSC 10 LTSC LTSC 2016
up to 5 up to 5 users Windows 2016 2016 Windows
computers Windows Server 2016 Windows Windows Server 2016
Windows Server 2016 Server Server
Server 2016 2016 2016
Hard As required Min. 3x 100 As required As re- As re- As required

disk by applica- GB, by applica- quired by quired by by applica-
tions As required tions applica- applica- tions
by capacity tions tions
Video Recommen- Recommen- Recommen- Recom- Recom- Recommen-

dation dation dation mendation mendation dation
1920x1200 1920x1200 1920x1200 1920x1200 1920x1200 1920x1200
Table 1-2 Hardware requirement summary table
1.7.3 Software Requirements Details

S+ Operations 2.1 Service Pack 2 supports the following operating systems:
– Windows 10 Enterprise LTSC 2016, 64 bit, English
– Windows Server 2016 Standard Edition, 64 bit, English
3rd party software as the following:
– Microsoft Office 2016, 2013 SP1 Standard or Professional 32 bit
– Microsoft SQL Server 2016 Standard Edition, 64 bit
– Microsoft Internet Explorer 11
6 8V Z Z 0 01 2 88T 2 12 0 A
I N T R O D U CT I O N RE Q UI RE M E NT S
– All referenced operating systems, Office, Internet Explorer and SQL Server should always
include the latest security patches and service packs as well as antivirus qualified by ABB.
Please refer to Field Alert document “2VAA001442 Security Updates Validation Status for
Symphony Plus” for the latest information on approved security patches and antivirus def-
initions. This document is accessible in ABB Solutions Bank for registered users with valid
Sentinel subscription.
Note: To prove that you are eligible to install SQL Server 2016 please make sure that you
received with your order the SQL license stickers. As a proof of legal license, you are sup-
posed to attach them to all client computers.
- for AC800M connectivity

For AC800M Connectivity Only System 800xA 6.0.3.2 is supported and required
package can be downloaded from respective location of ABB Library
- for Freelance Connectivity
Freelance 2016 SP1 with latest rollup under Windows 10/Windows Server 2016 as
Operating System is supported. The required package can be downloaded from
respective location of ABB Library
1.7.4 Hardware Serverless Configuration
1.7.4.1 Small (<1000 tags) Workstations
Workstations should have at least 4 real cores, be either a Xeon processor v5 or later with at
least 3.5 GHz. At least 8 GB RAM. Hard disks size as required for application size and history
length1.
1.7.4.2 Large Workstations
Workstations should be using Xeon Silver processors with at least 2.6 GHz. At least 8-16 GB
RAM as required by number of tags. Hard disks as required for application size and history
length1.
1.7.5 Hardware Server based Configurations
1.7.5.1 Small system servers <1000 tags
Servers with Intel Xeon v6 or later with at least 2.3. At least 8 GB RAM. Hard disks as required
for application size and history length1.
1.7.5.2 Large systems servers with or without separated history
Servers should be a Xeon Silver or Gold processor with at least 2.3 Ghz and 16 GB RAM. Hard
disks as required for application size1. In case of integrated history more hard disks are re-
quired. Please refer to section on historian below. But typically, such a server needs 1 system
disk and 2 separate physical (not just partitions) hard disks for historical data storage. In
case of RAID configuration disks are typically doubled.
1
See the section on Volume estimation of hard disks for History Server
8 VZ Z 0 0 12 8 8T 2 12 0 A 7
RE Q UI REM E NT S I NT RO DUC TI O N
1.7.5.3 Large systems servers with integrated history
Servers or workstations should be either a Xeon v6 processor with at least 2.4 Ghz or Xeon
Silver or Gold processors with at least 2.2 Ghz. For large Alarm/Event databases 16 GB RAM is
recommended. Hard disks as required for application size and history length 1.
For maximum performance systems should have separated disks for programs, separate
event history and separate real-time values (3 separate hard disks, not only partitions).
If a high volume of clients (office and PowerExplorer clients) or a high demand of history
functions is expected then the performance can be improved by:
– Processors with faster cycle times
– Usage of solid state disks
Solid state disks usage: optimize on those with a high reliability and throughput (read/write).
In case a high number of alarms and events must be recorded (100k/day), it is recommended
that the event database is stored on SSD disks.
RAID usage:
RAID 1 (or RAID 10) can be applied by doubling the amount of hard disks (so min. 6 disks for
high performance historian server or RAID 10 then 12 disks). RAID 5 must use a high number
of disks to be effective in terms of performance and reliability (at least >8 disks).
1.7.5.4 Volume estimation of hard disks for History Server
Real-time value history:

S+ History only records signals when a value change occurs that exceeds a defined tolerance
band.
The maximum possible signal-recording rate relates to the sum of all changes of all tags per
second. Typically, a power plant unit with 20k tags and well-defined dead bands (0.1%-0.5%
dead band and 0.5-1 seconds scan rate) uses about 50-200 GB/year disk space.
Event history:
As a calculation basis, S+ Operations Historian consumes approximately 1.2 GB of storage
space for every 1 million events. A typical power station with 10,000 alarm & events/ day con-
sumes about 4.4 GB of disk space per year.
1.7.5.5 Application server
Servers should be a Xeon E3 v6 with 3.6 GHz, or Xeon Silver or Gold processor with at least 2.3
GHz and 8-16 GB RAM. Processor, hard disk and memory type must be determined by applica-
tion size.
1.7.6 Hardware clients
1.7.6.1 Operator clients for server based configurations
Workstations should have at least 4 real cores, be either a Xeon processor v5 or later with at
least 3.5 GHz. At least 8 GB RAM. Hard disks size as required for application size.
For high performance clients optimizing display call-up times please use processors with
high cycle speed such as Intel Core Intel Xeon E3-1225 v5, 3.3 GHz or Intel® Xeon® Gold 5122,
3.6GHz.
1.7.6.2 Full office client
Workstations should be at least I3 processor with a minimum of 4 GB RAM.
8 8V Z Z 0 01 2 88T 2 12 0 A
D ATA SH E E T S ER VE R LE SS A RC HI T E CT URE
2 DATA SHEET
2.1 Serverless architecture

Serverless clients are always stand-alone. No interaction may occur between clients for HSI
server functions.
However, history functions can be configured to be on a single/redundant History server

only.
Controller Limitation Serverless on Client OS
Harmony 10 k Harmony Tags
AC800M 12 Controllers
Table 2-1 Serverless architecture
For Serverless on Server OS, limits of Server based architecture applies.
2.2 Server based architecture

For architectures following the server based architecture, the below general limits apply.
Controller Limitation Server based
Harmony 100 k Harmony Tags.
AC800M 12 Controllers
Table 2-2 Server based architecture
2.3 Version Compatibility

2.3.1 Harmony
Harmony Connectivity is supported for Harmony API 3.3.0.2
2.3.2 AC800M
AC800M Connectivity is supported for 800xA System Version 6.0.3.2
2.3.3 Freelance
Freelance Connectivity is supported for Freelance 2016 SP1
2.4 Features: Sizes

Minimum, default and maximum values of sized features of the package are described below.
In most cases values listed as “Unlimited” are only limited by disk capacity or memory.
8 VZ Z 0 0 12 8 8T 2 12 0 A 9
F E AT UR ES : SI Z E S DATA S HE E T
All facts below are as recommended, tested and rationalized during standard test proce-
dures. Exceeding requirements are sometime possible and shall be discussed with product
sales.
Category Parameter or Min. Default Max.

Feature
Architecture Recommended
and tested con-
figurations
Redundancy RT Server 1 1oo2 1oo4

level
History Server 0 1 1oo2
Web Server 0 1 Parallel
Application 0 1 2
Server
Front-end Server 0 1 1oo3
Composite Ar- 0 1 1oo2

chitecture
Hierarchical ar- 0 1 1oo2

chitecture
Composite
Clusters 1 2 4
Data exchange 300 1000 2000

exceptions/s
Hierarchical
Clusters 1 2 4
Data exchange 300 1000 2000

exceptions/s
continuously
Table 2-3 : Sizes: Category Architecture
10 8V Z Z 0 01 2 88T 2 12 0 A
D ATA SH E E T FE AT UR ES : SI Z E S
Category Parameter or Feature Min. Default Max.
Hardware
Clients Number of operations clients 1 32

per server (Power Explorer cli-
ents)
Servers Number of Servers in one Sys- 1 256

tem
Table 2-4 : Sizes: Category Hardware
Database
Tags Number of Analog Tags 100 5,000 256,000
Number of Digital Tags 100 5,000 256,000
Number of Database Tags 200 10,000 512,000
Number of Characters in Tag 0 20 In SPO – 50. In

Name Composer Har-
mony – 32.
Number of Atoms per Tag 1 N/A 50
Number of Atoms per Server 0 N/A 1,000,000
Eng. Units Number of Descriptors 0 128 512
Alarm Com- Number of Comments 0 100 1,024

ments
Table 2-5 : Sizes: Category Database
8 VZ Z 0 0 12 8 8T 2 12 0 A 11
Alarm Handling
Tags Number of Handled Alarms N/A N/A 512,000
No. of Analog Alarm Levels N/A 8 8
No. of Rate of Change Levels N/A 2 2
No. of Deviation Levels N/A 2 2
Groups Number of Alarm Groups 0 1024 1024
Priorities Number of Alarm Priorities 0 16 31
Number of Alarm Colors 0 8 20
Tones Number of Audible Tones 0 32 1024
Table 2-6 : Sizes: Category Alarm Handling
Transfer Proper- Property transfer from one tag

ties to another
Output Transfer No. of Tags to transfer 0 0 50

Tags
Cycle time Cycle time of transfer mecha- 1000ms 2000ms N/A

nism
Table 2-7 : Sizes: Category Transfer Properties
RT Calculations
Tags No. of Tags per Calc. Block 0 100 2,000
Blocks No. of Calculation Blocks 0 100 10,000
Statements Statement Length N/A 256 256
Table 2-8 : Sizes: Category RT Calculations
12 8V Z Z 0 01 2 88T 2 12 0 A
S+ Calculations
Calculation Number of Calculation Groups 1 1 10

Groups
Number of Cal- Number of Calculations per 1 1 100

culations each Calculation Group
Number of Number of Variables/Tags per 1 1 1000

Tags/Variables each Calculation
Table 2-9 : Sizes: Category S+ Calculations
Operator Inter-
face
Displays Number of Displays N/A N/A 2500
Windows Number of Power Explorer per 1 1 4

Client
No. of Menu Items in the main N/A 50 100

toolbar of Power Explorer
No. of Items in the Alarm List N/A 100 280

toolbar
No. of Items in the Display N/A 5 20

Mimic toolbar
No. of Items in tree View (Fly N/A 100 2500

out Menus)
No. of simultaneous faceplates N/A 8 32
Workplaces Number of different workplaces 1 50 256
Table 2-10 : Sizes: Category Operator Interface
8 VZ Z 0 0 12 8 8T 2 12 0 A 13
Pocket Portal
Number of Pocket Portal clients 0 40

per Server
Number of Pocket Portal Server 1 2
Process Number of SVG Elements per

Graphics Display:
Internet Explorer 1000
Chrome 2000
Trends Trends lines per Display 20
Alarm List Number of Alarm per Display 1 N/A 100

Page
Event List Number of Events per Display 1 N/A 100

Page
GIS View Number of GIS elements 1 N/A 100000
Dashboard Number of Dashboard elements 1 N/A 50

per Display Page
Signal List Number of Signals per Display 1 N/A 100

Page
Web Browser Number of Pages 1 N/A 50
Table 2-11 : Sizes: Category Pocket Portal
Security
Users Number of Individual Users As defined in Windows
User Name Number of Characters As defined in Windows
Password Number of Characters As defined in Windows
Security Level Number of Security Levels N/A N/A 16
Security Groups Number of Security Groups N/A N/A 32
Table 2-12 : Sizes: Category Security
14 8V Z Z 0 01 2 88T 2 12 0 A
Harmony Pro-
cess Events
SOE with SEM Number of SOE devices 0 0 256/SER
Number of SOE tags 0 0 1500/SEM
Number of SOE reports 0 2 10
SOE with HPC Number of SOE tags 0 0 5000/HPC
Number of SOE devices 0 0 256
Number of Triggers 0 0 3/tag
Number of concurrent SOE re- 0 2 10

ports
Table 2-13 : Sizes: Category Harmony Process Events
Summaries
Tags Real-time Tag Summaries N/A N/A Unlimited
Tag Operating Parameters N/A N/A Unlimited
Table 2-14 : Sizes: Category Summaries
Short term Hist.
No. of lifetime days 1 90 90
Number of History Logs 0 N/A Unlimited per

system, 100k
per server
History resolution 1ms 1ms Event based
Data retrieval time 100ms 1s Query based
Console trends Number of Trends N/A N/A Unlimited
No. of Tags per Trends 1 20 20
No. of Colors for Trend Curves 15 N/A Unlimited
8 VZ Z 0 0 12 8 8T 2 12 0 A 15
Maintenance Number of Digital totalizers 0 100 1,000
Totalizers Number of Analog totalizers 0 100 1,000
Table 2-15 : Sizes: Category Short Term Hist.
Long Term Hist.

Process data
Number of History Logs 0 N/A Unlimited per

system, 100k
per server
History resolution 1ms 1ms Event based
Data retrieval time 100ms 1s Query based
Office Trends Number of Trend N/A N/A Disk Size
No. of Tags per Trend 1 20 50
No. of Colors for Trend Curves 1 N/A 256
Report storage Max Days N/A N/A Disk size
Max Number of Files N/A N/A Disk size
Report genera- Max Number of Report sched- 0 50 150

tion uled
Storage rate Continuous exceptions per s 0 1000 1000

Exceptional exceptions per s 0 15.000 15.000
Reading rate Reading rate exception/s 0 5000 30.000
Capacity Disk size usage 10 MB 250 GB 1 TB
Long Term Hist.

Event Data
Storage rate Continuous Events per day 0 100.000 100.000

Exceptional storage rate 0 100.000 2.000.000
Reading rate Reading rate events/s 100 1.000 5.000
Capacity Disk size usage 500 MB 100 GB 400 GB (10 y)
OPC
OPC HDA
Server
16 8V Z Z 0 01 2 88T 2 12 0 A
Requests Requests / min n.a 60 100
Record length Data records per request n.a 1000 10.000
Max clients Number of clients per HDA 0 1 10

server
Time range Time range per request 1s 1h 1 month
SQL Transmit-
ter
Cycle time Cycle time 5 min 15 min 1 month
Signals Signals per class 1 Cycle Cycle

time/1000ms time/500ms
Table 2-16 : Sizes: Category Long Term Hist.
Printing
Printers Number of Printers 0 N/A 10
Table 2-17 : Sizes: Category Printing
Communication
Drivers Number of parallel drivers per 0 N/A 200

Server
Harmony Driver Number of ICI connections per 0 1 8

Server
Number
Virtual PNI Number of VPNI Connections 0 0 1

per Server
Number of Tags per Server 0 N/A 30000
OPC DA Number of connections 0 0 100
Modbus TCP Number of devices per Server 0 0 150

Number of servers 0 0 256
Signals per device 0 0 1000
Min Cycle time 200ms 1000ms
8 VZ Z 0 0 12 8 8T 2 12 0 A 17
Modbus TCP – Number of devices per driver 0 N/A 1000

Multi-device Number of servers 0 0 256
Driver Signals per device 0 0 200
Atoms per Tag 1 1 50
Modbus serial Number of devices per connec- 0 0 100

tion 0 0 256
Signals per device 200ms 1000ms
Min Cycle time
AC500 Number of AC500 / OPC server 0 N/A 30

Number of Servers 0 0 64
Number of OPC items per 0 N/A 10,000
AC500 0 N/A 20,000
Number of OPC items per OPC
Server
IEC 61850 Number of IEDs 0 0 160

Number of connections per 0 0 1
server 1 1 4
Number of subnetwork per 0 0 80
server 0 0 64
Number of IEDs per subnetwork 0 0 150
Number of servers
Changes per second on stack
IEC 104 Number of devices per Server 0 0 150

IEC 104 – Multi- Number of devices per driver 0 N/A 1000

device Driver Number of servers 0 0 256
Atoms per Tag 1 1 50
Table 2-18 : Sizes: Category Communication
Information
Management
Full Clients Number of concurrent clients 0 N/A 50
Web Clients Number of concurrent web cli- 0 N/A 200

ents
Tag Length Number of Characters 0 N/A 30
Table 2-19 : Sizes: Category Information Management
18 8V Z Z 0 01 2 88T 2 12 0 A
D ATA SH E E T FE AT UR ES : D ETAI L S
2.5 Features: Details

Category Parameter or Feature Current
Database
General Configuration On-line and Off-line.
Tags Standard Format Excel (XLSX), XML, TEXT
Compatibility to ... Win Tools
Eng. Units Standard Format Composer (conversion to or from MDB

file).
Compatibility to ... Excel (XLS) or CF File.
Alarm Com- Standard Format Win Tools (CF File), Excel (XLSX)
ments
Table 2-20 : Details: Category Database
Alarm Handling
General Alarm Acknowledgment Global (user restricted), per Individual

Tag,
Alarm Inhibit Per database or individually.
Page Acknowledgement Acknowledges whole alarm page.
Alarm Action Program Automatic per Individual Tag, Manual

per Individual Tag.
Alarm Shelving Manual per Individual Tag.
Alarm out of service Manual per group
Alarm latching Manual per Individual Tag.
Alarm removal Manual per Individual Tag.
Tags Variable Alarm Levels Activation configurable per individual

tag and per alarm condition.
Alarm Dead-band The Alarm Action Program must be

separately implemented.
RTN as New Message Configurable per individual tag.
Remove Alarm Message on Configurable per individual tag.

Acknowledge
Groups Group Tree Configurable.

Default: 16 main groups and 16 sub-
groups for each main group.
8 VZ Z 0 0 12 8 8T 2 12 0 A 19
FE AT UR ES : D ETAI L S DATA S HE E T
Nodes Acknowledgment Broadcast Configurable (default NO).
Tones Types of Audible Tones Beep, Wave file (one shot or continu-
ous), Horn (via external activation).
Audible on Alarm Configurable per individual tag.
Audible on RTN Configurable per individual tag.
Alarm Audible Silence Global.
Disable Audible on Configurable (default YES).

Acknowledge
Pages Alarm Display Alarm Page per group and Unacknowl-

edged Alarm Window.
Alarm Filtering Individually by choosing displayed col-

umns
Alarm Summary Summary always on view and One click

to display.
Message Format Font Height and Weight of Configurable.

Message
Multiple customizable alarm Configurable and runtime selectable

views
Alarm Comments on Alarm Configurable (default NO).

Display
Value Updated within Alarm Configurable (default YES).

Display
Milliseconds within Date/Time Configurable (default YES).
Time of Alarm Resolution 1 Millisecond.
Date and Time Configurable.

Standard: dd-mmm-yy or
Alternate: according to Regional Op-
tion settings.
International Date Configurable according to Regional
Table 2-21 : Details: Alarm Handling
20 8V Z Z 0 01 2 88T 2 12 0 A
Human Interface
General Language Multi-language supported. Default

English. Other languages e.g. Japanese
supported if translation files are pro-
vided.
Displays Graphic Editor Embedded Editor
Import Existing Mimics SLGM (via conversion)
Update Frequency of Dynamics Selectable 1 Sec. or 5 Sec.
Standard Input Format Dbase III/IV (DBF) or Excel (XLSX).
Windows Multi-screen Configurable (default NO).
Drag able Windows Configurable (default NO).
Process Control SP and CO Increment Configurable (default 0.2%).
SP and CO Fast Increment Configurable (default 4%).
Double Click to Select Popup Configurable (default NO).
Table 2-22 : Details: Human Interface
Security
General Access Windows users.
Technology Windows Single Sign On.
Log In Log In Windows Username and Password.
Username Case sensitivity by Windows policy.
Password Case sensitivity by Windows policy.
Default Log-in User Current Logged In Windows User.
Log-in Display Configurable.
Log Out Log Out Manual on demand or Automatic on

time-out.
Log-out on Time-out Configurable.
Table 2-23 : Details: Security
8 VZ Z 0 0 12 8 8T 2 12 0 A 21
Process Events
General Sequence of Events Standard and distributed.
Sequence of Events Resolution 1 Millisecond.
Tags Number of SOE Events Configurable.
Duplication of SOE to Digital In- Configurable (default YES).

puts
Logs Multiple SOE Logs Kept individual or merged.
Table 2-24 : Details: Process Events
Summaries
Tags Real-time Tag Summary Multiple filtering criteria.
Table 2-25 : Details: Summaries
Online Hist.
General Types of Data Playback
Trends Types of Historical Trends Instantaneous Value, Minimum, Maxi-

mum, Total, Count, Monitor and Ratio.
Trend Displaying Formats Trend or Table.
Trend Time Displaying Real-time or Historical.
Curve Highlight on Trend Bolding of Selected Tag.
Tag Engineering Unit Scale on Default: 0 - 100 % or

Trend E.U. Scale of Selected Tag.
Trend Curve Analysis Pause Real-time trending, Zoom and

Pan Functions, Drag Cursor.
Trend Configuration On-line or Off-line.
Category Parameter or Feature Details
Trend Display Configurability On-line.

Tag Scale, Curve Color and Display
22 8V Z Z 0 01 2 88T 2 12 0 A
Statistic Data of Trend Curves On Demand.

Average, Minimum and Maximum, Time
of Minimum and Maximum.
Chronol. Alarms Alarm Summary Multiple Filtering Criteria.
Table 2-26 : Details: Online Hist.
Long Term Hist.
General Type of Data Real time analogue and binary data,

Chronological Alarm Messages, reports,
Post Trip logs
Archival Storage On-line hard disk, SSD supported
Automatic Archiving on Time Configurable.

Basis
Manual Archiving Supported.
Media Archive to BD, DVD, CD, Disk, File.
Logs Data Logging Custom Excel Work-sheet.
SOE Sequence of Events Logging SQL DB, Standard Text File, Custom Ex-
cel Work-sheet
Table 2-27 : Details: Long Term Hist.
Ext. Interfaces
OPC OPC Interface OPC Server and OPC Client (DA 1.x, 2.0,
AE1.x, HDA 1.x)
WEB WEB server HTTP and HTTPS, Graphics, trends, alarm

& events, reports, signal explorer
Hardware
Hosts Architecture Serverless, Client/Server
Host PC Custom
(Dell and HP suggested).
Clients Client Switch-over to Server Automatic or Manual.
Server List for Clients Configurable.
8 VZ Z 0 0 12 8 8T 2 12 0 A 23
Nodes Redundancy Multi-Master Nodes.
Field Field Hardware Symphony Plus, Infi 90
Table 2-28 : Details: Ext. Interfaces
Communication
Standard Supported C-Net, Infinet.
Scanner Suite Capability to Host Drivers for Foreign Protocols.

Suite provided for support.
Embedded Drivers for Modbus Protocol Modbus TCP, OPC
Table 2-29 : Details: Communication
24 8V Z Z 0 01 2 88T 2 12 0 A
VI RT UA LIZ AT I O N N UM B E R O F S YM PH ON Y P LU S SE RVE R S T O P RO VI D E T HE R E Q UI R E D D CS F U NC TI O N
3 Virtualization
When planning to run S+ Operations in a virtual environment, the following sizing of servers
and network components that will provide the underlying foundation to run the application is
required.
– The following dependencies must be considered:
– Number of Symphony Plus Servers to provide the required DCS functions
– Process workload which will consume Symphony Plus resources
– Redundancy architecture
– Network connectivity
– Equipment Lifecycle
– Equipment Maintenance
– Cybersecurity
This section provides information and guidelines for engineers designing a S+ Operations
system in a virtual environment. Due to the dynamic nature of virtualization, evolving tech-
niques for its deployment and the special requirements imposed by a Distributed Control
System that at its core has personnel and equipment safety embedded at the forefront, it is
highly recommended that ABB be engaged early on in any virtualization design.
3.1 Number of Symphony Plus Servers to provide the

required DCS function
Although defining the number and functions of Symphony Plus servers within a DCS architec-
ture is beyond the scope of this section, it must be said that their number impacts the design
of the infrastructure that will run the virtual machines.
The number of Symphony Plus servers is typically determined by the functionality required to
monitor and control the process. As such, typically the following servers are used:
– S+ Operations
– S+ Operations Historian
– Symphony Plus Alarm Management
– Symphony Plus Optimization
– Symphony Plus Scanner
– At times, these functions may be combined into a single server, such as:
• S+ Operations Historian and Alarm Management
The benefits are obviously a reduction in the number of physical machine components, at the
expense of increasing its computing resources. Similarly, this also has an impact on the virtu-
alization architecture, which would run a reduced number of virtual machines, but each de-
fined with an increased set of resources.
When configuring and defining physical machines to run these functions, the capabilities and
limitations of the physical sub-systems in a server are taken into account. In a virtual environ-
ment, however, it is the performance of the virtual machine's resources which are used. To
properly account for such, it is advisable to list all the Symphony Plus servers and note their
8 VZ Z 0 0 12 8 8T 2 12 0 A 25
N UM BE R O F S YM P H ON Y P L US S E RVE R S TO P RO VI D E T HE R E Q UI R ED DC S F U NC TI O N VI RT UA LI Z ATI O N
functionality. This will account for the resources required by each of the Operating Systems,
plus the resources required by each of the Symphony Plus servers for their intended function.
Actions:
– Count number of Symphony Plus Servers
– List their functions
– From the appropriate Symphony Plus manual determine what resources are needed if
they are to be satisfied by a physical machine.
From the above, determine:

– Number of Operating Systems to run
– Number of nodes that will be virtualized
– Minimum HW requirements for O/S
– Minimum HW requirements for 3rd party SW|
This is a first approximation since plant characteristics will be determined next.
Process workload which will consume Symphony Plus resources
This refers to determining the degree to which the plant will require resources of the Sym-
phony Plus system. Although determining system sizing is beyond the scope of this manual,
some examples are shown below:
S+ Operations Server:
– Number of tags
– Number of alarms per hour
– Number of Operator Stations
S+ Operations History Server:
– Number of analog cyclical data to be stored
– Number of digital cyclical data to be stored
– Number of alarms and events to be stored
Calculation Engine:
– Number of calculations
– Scanner Servers:
– Number of scanned tags
Operations Workstations:
– Number of monitors
– Types of graphics (High Performance, Gray Scale, etc.)
From this plant characterization, a given set of physical resource requirements will be deter-
mined. These requirements are to be added to the requirements for each of the nodes deter-
mined in step one.
26 8V Z Z 0 01 2 88T 2 12 0 A
V I R T UA LIZ AT I O N RE DUN DA N CY A RC HI T E CT URE
From the appropriate Symphony Plus manual, determine what resources are needed, as if
they are to be satisfied by a physical machine.
– These include:
– Number of CPUs required for each server
– Amount of RAM for each server
– Amount of storage required for each server
– Network speed for each server's Ethernet interface
– Number of network connections for each server
3.2 Redundancy architecture

Almost all DCS systems are designed with redundancy in such a manner that no single point
of failure would render the DCS unavailable.
This means that duplicating the servers is a mandatory requirement.
Duplicating the system in a virtual architecture is akin to duplicating the number of physical
servers, should have the system been designed as a physical system in which all server func-
tions are carried out by individual physical machines. It must be noted that Symphony Plus is
not only a highly available system, but also a real-time redundant system in which a single
failure does not cause loss of data, even in the face of real-time operation.
This design requirement has been thoroughly tested within the redundancy mechanisms of
the Symphony Plus application, in a design that is either entirely physical, or which mimics
the physical deployment. In other words, real-time redundancy via mechanisms other than
those provided by Symphony Plus are not supported, such as vMotion, High Availability or any
other similar technologies.
This does not mean that vMotion, High Availability or other techniques cannot be applied to
further increase the resiliency and availability of the system. It means that these technolo-
gies are to be thought of for different reasons, such as increasing the system availability, eas-
ing maintenance, or other non-real-time requirements.
Based on Symphony Plus documentation, determine what resources are needed to imple-
ment the desired redundancy. Some redundancy schemes are N+1, N+2, etc.
– These determine the number of host servers:
– N+1 = One extra host server
– N+2 = Two extra host servers
– N+N = Double servers needed for operation
8 VZ Z 0 0 12 8 8T 2 12 0 A 27
N E T W O RK CO NN E CTI VIT Y VI RT U A LI Z ATI O N
3.3 Network connectivity

In a physical environment, there are at least two different networks that must be accounted
for: The Operations Network, where clients and servers exchange data for (as an example)
display purposes, and the Control Network, where the servers and controllers exchange data
for receiving field data and sending commands to plant equipment. In a typical design, these
networks are separate and require separate ports. They also require different performance
levels. For instance the Operations Network requires gigabit speeds, while the control net-
work may satisfy the architecture's needs at 100 mbps speeds.
At other times, other ancillary functions may also be desired, such as Out-Of-Band manage-
ment or Disaster Recovery. These requirements all add to the architecture of a virtual envi-
ronment, just like it does in a physical environment. However, because of the possibility of
aggregation, it is important to define what type of network design will be implemented in
the virtual environment, and tally the traffic expected on each interface. This traffic is also
the result of the plant's characterization, discussed in the previous section.
To properly design the system, it is to be noted that some traffic which in a physical environ-
ment necessarily leaves and enters a network interface, may, in a virtual environment remain
within the host. This improves performance of the system as a whole, for some operations.
But for some operations, it places more requirements on the physical network interface, be-
cause of the aggregated traffic. Thus a tally of what traffic comes into and out of the net-
work interfaces is required:
From the appropriate Symphony Plus manual, determine network requirements and tally:
These include: |
– Expected network interfaces being aggregated
– Number nodes participating in a given interface
This will determine if a single network interface is required, or whether multiple interfaces
need to be aggregated, or even if ports of high speed are needed, such as 10 Gbps, or 40
Gbps, etc.
Finally, although almost all network switches have the required fabric speeds required for
systems of the type typically deployed in a DCS, it is important to make sure the bandwidth
calculated within this section matches up with the specifications of the network switch.
3.4 Equipment Lifecycle

One reason to replace servers is because of failures or obsolescence of its components. This
is most common with mass storage, which is the weakest of all components in a server.
When it comes to storage however, it doesn't need to be replaced just because of failures. At
times, a server's disks need to be replaced not because they have failed, but because they
cannot be upgraded or retrofitted to perform additional functions desired of the system -
such as because more virtual machines are to be deployed or because additional strain is
placed on the DCS.
In a virtual environment, there are several ways to deal with this need. One is to replace com-
ponents with more up-to-date specifications. This method, however, may require that the
virtual system be taken offline. To avoid such, another avenue is available: to have additional
resources added to the system. This is possible because in a virtual environment, the modifi-
cation of the host does not mean that any of the virtual machines is modified. In this case,
they are simply given more resources. It is the underlying hypervisor's function and ability to
treat its resources as components that can easily be added.
28 8V Z Z 0 01 2 88T 2 12 0 A
V I R T UA LIZ AT I O N EQ U I P M E N T M AI N T E NA NC E
However, resources cannot be added to a host, unless the host is prepared to receive them.
Thus, the virtual machine host must be sized properly for the desired lifecycle.
Identify long term plant requirements and determine what additional features will be re-
quired throughout the life expectancy of the system. Then determine storage, network and
memory requirements as per the sections above
Tally these requirements and add them as required resources that the Virtual Machine host
will be required to support in the future.
– These include: |
– Processors
– Memory
– Storage
– Network bandwidth requirements
3.5 Equipment Maintenance

All systems require maintenance, whether to replace failed hardware, to move onto upgraded
equipment, or for expansion or added functionality. During these periods of maintenance,
the system must be powered down. Most of the time, during which the hardware is main-
tained, the underlying application remains the same. Virtualization allows for easier mainte-
nance of the system, by moving the virtual machines from one server to another. More gener-
ically, it can be said that the virtual machines can be moved from one resource to another,
such as from one storage resource to another.
In this case, one must account for the required storage to relocate the virtual machines.
From each application's specifications, determine the amount of storage required and tally
it:
These requirements include:
– Operating System requirements for installation
– Operating System requirements for operation
– Symphony Plus Application requirements for installation
– Symphony Plus Application requirements for operation
– Third Party Application requirements for installation
– Third Party Application requirements for operation
– Symphony Plus Data Storage requirements
8 VZ Z 0 0 12 8 8T 2 12 0 A 29
C YB E R SEC U RI T Y VI RT U A LI Z ATI O N
3.6 Cybersecurity
In particular, this section refers to Disaster Recovery. ABB's standard Disaster Recovery appli-
cation is Rapid Recovery, which creates on-line periodic backups of all nodes. This recurrent
and permanent on-line backup method relies on a reliable and agile network, which is best
served by a separate network infrastructure specifically for Disaster Recovery. Determining
the amount of data to be backed up is very complex because Disaster Recovery software pro-
vides two algorithms to reduce the amount of data being stored in their backup repositories:
Compression
Performs compression on the data being stored, by removing most redundant data and in-
stead adding error correction and data protection.
De-duplication:
Avoids having to store multiple copies of the same data from different nodes on the system.
Because of these two mechanisms, computing the amount of data to be stored is extremely
complex. At times, compression and de-duplication can achieve compression ratios close to
90% and so it is best to follow the recommendations for storage of the Disaster Recovery ap-
plication separately.
However, the main requirement for Disaster Recovery is to have a resilient and agile network,
with plenty of bandwidth to quickly supply data to the Disaster Recovery backup server. It is
this requirement which (for optimal operation) mandates the use of a separate network with
enough bandwidth to transfer data quickly. It is best to have at least a 1 Gbps network di-
rectly from the virtual machine hosts to the Disaster Recovery server.
From the previous section, determine the approximate amount of storage required and ag-
gregate it.
Affect the total storage requirement by a factor of 50%. This conservative figure is the
amount of data that will be stored in the Disaster Recovery server repository.
However, only a fraction of this data will be sent over to the Disaster Recovery server. That
is because the Disaster Recovery agent only sends the data that has changed and not every
disk sector or bit. It is this value which will determine network bandwidth requirement.
A conservative figure of 10% of the 50% is recommended.
3.7 Virtual System Architectures – Matching Physical

Machines Resources
From the above it can be seen that the starting point for designing a virtualized system are
the requirements for deploying a physical system.
A possible architecture then is to design and apply resources based on the requirements laid
out for a physical infrastructure.
30 8V Z Z 0 01 2 88T 2 12 0 A
V I RT U A LIZ AT I O N VI RT UA L S YST E M A R CHI T EC T URE S – MAT CHI N G P H YSI CAL M A CH IN E S RE SO URC E S
Figure 3-1 A single host based architecture
The hardware resources (shown within the orange box) are identified and managed by the
Hypervisor. The configuration of each Virtual Machine (shown as vertical stacks of resources)
mimics what would be an otherwise physical system, with actual disk resources defined
within the software as individual RAID containers, each assigned to a given virtual machine.
This approach, has the following benefits:
– The same principles and calculations applied to select hardware for physical machines can
be used to design the virtual machines,
– Simple to configure the virtual host, because its specifications are the sum of the specifi-
cations of each individual physical server or workstation,
– Provides ample resources for sudden, unexpected, random and hard to determine work-
loads,
– Because no specialized hardware is used, the system is very cost effective and compact in
size, especially for small virtual deployments,
– It is easy to determine expansion requirements because it follows a physical model, easy

to replicate in a virtual environment, and
– All resources are contained in the same host, making it simple to deploy.
However, this approach, also has some drawbacks:
– Hypervisor efficiencies, are not taken into account and as a result, the system becomes
over-designed,
– The hosting server’s physical limits become a limiting factor in system growth,
– The hosting server’s physical limitations also impose an upper limit on the size of the vir-
tual infrastructure,
– The advantages of overprovisioning cannot be realized, and
– The advantages of more specialized disk technologies, with higher efficiencies, reliability
and resiliency cannot be realized.
8 VZ Z 0 0 12 8 8T 2 12 0 A 31
VI RT UA L S YST E M A R CHI T EC T URE S – R E SO U RC E P O O LI N G A R CH ITE CT UR E VI RT U A LI Z ATI O N
3.8 Virtual System Architectures – Resource Pooling

Architecture
A different alternative is to design the virtual machine host server to provide the needed re-
sources, regardless of what requirements or what architecture a purely physical design would
have required.
In this approach, the virtual machine host is considered as a pool of resources, which will be
made available to each of the virtual machines. These resources are then consumed as the
virtual machines run, and as each virtual machines workload varies over time. Furthermore,
this architecture does not need to follow any particular design technique, which in an individ-
ual physical server would be considered.
Pooling resources requires then having information on the capabilities, not of each compo-
nent that makes up a sub-system, but rather of the sub-system as a whole. This approach
has the merit of using each sub-system’s state of the art performance and capabilities to the
fullest.
It also allows taking full advantage of the highly specialized capabilities of the hypervisor op-
erating system, such as overprovisioning of the system, as will be described later.
The following sub-systems are considered:
– CPUs: Processing power is pooled on the host and assigned to each virtual machine on an
as-needed basis. This sub-system is highly linear in nature and requires simply adding up
all available cores to determine available capability. As cores are utilized, they are sub-
tracted from the pool.
– Memory: Amount of DRAM and bandwidth is pooled on the host and, similarly to what
happens with the CPUs, it is assigned to each virtual machine as needed. This is a linear
resource which means that total memory on the host determines maximum capability of
the system as a whole, and as it is consumed it is subtracted from the pool.
– Disks: This sub-system is significantly more complex than CPU and RAM. There are two
main specifications that must be considered: performance and storage.
• Performance: This resource determines the capability of the virtual machine to per-
form. It is the main factor that determines what workload each application can sus-
tain.
To understand the required disk performance, a complete understanding of each applica-

tions needs is required. This requires understanding the boundaries of the workload that will
be imposed on each application and the desired or needed response times users expect to
experience.
Disk performance is specified by IOPS and Mbps figures, with each of these figures being ad-
ditive to determine maximum system capabilities.
As IOPS and Mbps resources are utilized, they are subtracted from the pool.
The difficulty with this particular resource is not how much is available (because that is calcu-
lated by simple addition), but how much of it is used, how it varies over time and how much is
required to be in reserved for peak conditions.
• Storage: This resource determines amount of data that can be held and number of ap-
plications that can be installed on the virtual machines. It does not determine how well
the system operates.
32 8V Z Z 0 01 2 88T 2 12 0 A
V I R T UA LIZ AT I O N VI RT UA L S YST E M A R C HI T EC T URE S – R E SO URC E P OO L I N G A RC HI T E CT UR E
Total storage capacity is simply the sum of all available disks, and becomes the pools
total available resource. As storage is consumed by applications storing data or appli-
cations being installed, capacity is subtracted from the pool.
There is some degree of randomness and non-determinism in required storage capac-

ity, stemming from storage used by the Operating System and applications during op-
eration – such as for memory paging, caching or other such dynamic techniques. How-
ever, this is minimal compared to actual storage requirements for data and
applications and can be easily accounted for.
The disk sub-system now, can be design in such a manner as to not require any specific type
of configuration, so long as it provides the level of performance needed by the applications.
The following techniques can be used to design the disk sub-system (list is not exclusive nor
exhaustive):
– On server storage (also called “Direct Attached Storage”, or DAS)
– Off server storage
• Storage Area Network
– iSCSI
– Fiber Channel
• Network Attached Storage
It is important to note that in all cases, virtual machines are neither aware nor require to be
constrained by a particular design. All that is required is that the performance and storage
requirements be satisfied by the disk sub-system.
– Network: Because of the nature of Ethernet this is one resource that is not additive. Hav-
ing additional Network Interface Cards (NICs) does not provide additive receive or trans-
mit bandwidth. But neither is the need for this resource additive either.
Because in the virtual host all virtual machines are (or can be) “connected” via the hypervi-
sor’s virtual switch, what in a physical environment is traffic into and out of the server, be-
comes data exchanged internal in the virtual machine host – data which never leaves the
boundaries of the hosting server. The more virtual machines running in the virtual machine
host, the less traffic must traverse the physical NIC.
This does not mean there isn’t traffic into or out of the virtual machine host. Such traffic is
(or may be) traffic to thin clients, operator workstations, redundant servers or any other ma-
chine which consumes or provides data to virtual machines running in the host. It is this traf-
fic which must be accounted for when considering how much will traverse the NIC.
Latency of the network can be minimized by increasing the number of NICs, by providing mul-
tiple paths for different virtual machines to have greater access to network resources outside
of the physical host. Other network techniques such as Link Aggregation can also be used,
which will provide greater resources to the pool.
The dynamic and random nature of the utilization of Ethernet network resources means
these resources are not linear. However, techniques similar to those used for physical net-
work systems can be used to determine required network resources available to the host
pool, to be made available to virtual machines within the host.
– Power Supplies: Power supply capacity and power consumption of the system is linear,
which means the resource is additive and the consumption of each virtual machine can
simply be subtracted from the pool. However, predicting the exact power consumption of
the system is extremely complex.
8 VZ Z 0 0 12 8 8T 2 12 0 A 33
V I RT U A L S YST E M A R C HI T EC T U RE S – R E SO U RC E P O O LI N G A R CH I T E C T U R E VI RT U A LI Z ATI O N
Because this is not a sub-system than can be easily modeled, it is best to consult with the
manufacturer of the physical host, to determine power supply requirements.
This approach, has the following benefits:
– The virtual machine host architecture can be designed independently of the architecture
of each virtual machine, without regard for the requirements of early physical systems,
– Because of this independence, each virtual machine host sub-system can take full ad-
vantage of state of the art techniques for making resources available to the virtual ma-
chines,
– Without the constraints of a design philosophy, hypervisor efficiencies are fully realized,
such as the overprovisioning of any resource within its pool. This is especially useful for
improved memory, CPU and disk resource utilization,
– The hosting server’s physical limits do not limit system growth.
However, this approach, also has some drawbacks:
– Designing the virtual machine host becomes more complex. This also translates to an in-
creased learning curve for maintenance,
– Care must be exercised to no overprovision the system to the point where it is not capable
of addressing sudden, increased peak workloads,
– Over the life of the system, operating and maintenance expenses are significantly lower,
but, in the short term, capital expenses may be higher.
One possible architecture showing DAS:
34 8V ZZ 0 01 2 88T 2 12 0 A
V I RT U A LIZ AT I O N VI RT UA L S YSTE M AR C HI T EC T URES – R E SO URC E P OO L IN G A RCHI TE CT UR E
Figure 3-2 Resource pooling architecture
The above architecture shows an coupe of servers where all resources are local to the server.
However, a different architecture is also possible, where the disk resources are located out-
side of the servers, as a shared sub-system.
This is shown below:
Figure 3-3 A single host based architecture, external storage
8 VZ Z 0 0 12 8 8T 2 12 0 A 35
S UM M A RY A N D CO N CL USI O N VI RT U A LI Z ATI O N
The above architecture shows the conceptual layout of a virtual system utilizing off-server
shared storage. The shared storage may be designed as a completely independent sub-sys-
tem, with state of the art techniques.
Some of these techniques include:
– Any type of RAID array, designed to meet the requirements of the application and its
workload,
– Any type of off-server storage connection, be it iSCSI, Fiber Channel or Network Attached
Storage (NAS),
– Shared storage built into converged infrastructure servers, or standalone chassis specifi-
cally for hosting disks and disk controllers.
3.9 Summary and Conclusion

Symphony Plus is supported in a virtual environment, where advanced architecture tech-
niques can be used to great benefit in areas of cost reduction, increased lifecycle, improved
maintenance and easy growth.
Although many different virtualization techniques can be used, care must be exercised to re-
tain the real-time capabilities of Symphony Plus without compromised. For this reason, it is
recommended that ABB be engaged early on in the development, design and implementation
of any virtualization architecture.
36 8V Z Z 0 01 2 88T 2 12 0 A
M O DI F I C AT I O N S I N T H I S R E LE A SE NE W F UN CTI O NS
4 MODIFICATIONS IN THIS RELEASE
4.1 New Functions

4.1.1 SOE Configuration Tool
SOE Configuration Tool is an MS excel based utility that reads S+ Engineering 1.4 *.ebp file
and automatically generates SOE tag database and necessary SOE Driver configuration files
(Registry settings).
Figure 4-1 SOE Configuration Tool
For more information on SOE Configuration Tool, refer SOE Configuration Tool section of S+
Operations Harmony Connectivity guide.
4.1.2 Diagnostics Support of SPENM01

This release supports the diagnostics of SPENM01 module using Module status tag.
Also, Harmony Status Viewer is extended to support SPENM01 module that includes Event
resetting, loop & node topology, module status, problem report, and loop related diagnostics
such as event and error counters, exceptions statistics, and performance statistics
4.2 Improvements
Following improvements are done compared to previous release and also various Power
help/VSM cases reported to ABB’s support line are fixed in this release.
• Security Improvements
– IPSec Support
• Usability improvements
– Trend: Decimal places of value shown in the Scooter is now user defined and follows
the tag configuration
– Trend: Trend Statistics window that displays Min and Max value of tags along with
timestamps, and also displays average value.
8 VZ Z 0 0 12 8 8T 2 12 0 A 37
I M P RO V E M E NT S M O DI FI CAT I ON S IN T HI S R EL E A SE
– N90STA Tags alarm messages now includes the status bytes as well
4.2.1 Extended Redundancy

The Command mastership for extended redundancy is changed with this release. For this
new mechanism to work reliably it is important to have IET/PNI firmware version to be up-
dated to A8 or later. Also note that this release implements an intense check on establish-
ment of all points on PNI/IET with HMI, this results into delay on ICI status to go Online in
comparison to previous releases.
In previous release of S+ Operations, when extended redundancy feature is ON, the command
mastership as well as the mastership of data transfer is demanded to the server that owns
the connection with a specific connect (e.g a controller) since longer. This is to avoid sending
double command to the field, that according to the type of command could create unwanted
and inconsistent behavior (e.g Toggle commands or inc\dec percentage)
Figure 4-2 Current mastership
So, it is possible that a client connected to SPO-B trying to issue a command will be routed to
another server like SPO-A in order to be executed.
38 8V Z Z 0 01 2 88T 2 12 0 A
M O DI FI CAT I ON S I N T HI S R E LE A SE I M P RO V E M E NT S
This create a possible issue in command availability if for any reason ever the communication
between SPO-A and SPO-B is unreliable, moreover even into normal working situation it intro-
duces a delay into executing the command due to the propagation between the two servers
when in theory the command could have been sent from SPO-B directly.
This behavior is changed in order to let the connected server to execute the command if pos-
sible (e.g. the connected server have connection with the device).
Figure 4-3 New behavior
Note:
– in case of clients connected to remote servers that do not have connection to the field,
the command will move to a server with longer valid connection
– the new algorithm will be applied to commands only not on data transfer (that will keep
current algorithm)
The command propagation will not happen until absolutely necessary and the local server will
execute the command. If the local server is unable to execute the command because either is
not enabled by the architecture or by a fault, then extended redundancy will find the “best in
class” for executing the required command e.g. the server that have a stable connection to
the device since longer will execute the command.
Scenario 1: Client connected to SPO-C server that have no connection to device in this case,
Command is sent to all servers, but only one will execute which have longer period of connec-
tion to device, the others will drop it.
8 VZ Z 0 0 12 8 8T 2 12 0 A 39
I M P RO V E M E NT S M O DI FI CAT I ON S IN T HI S R EL E A SE
Figure 4-4 Example of remote server
Scenario 2: Client is connected to a server with device connection failure, the command is
propagated to another server
Figure 4-5 Example of server with failed connection
40 8V Z Z 0 01 2 88T 2 12 0 A
M O DI FI CAT I ON S I N T HI S R E LE A SE FI XE D P R OB L E M S
4.3 Fixed Problems

Tracking number Title Description
OPC Atoms re- Modification in tag (Ex. Edit tag description)

ports Not Initial- ServerA, leads it’s OPC atoms becomes Not Ini-
20170722-178931
ized after modifi- tialized state in Server-B and doesn’t update un-
cation in tag til Off/On Scan
Thin client
Thin client graphics goes out of alignment if
graphics resolu-
20170724-193182 viewed in lesser resolution than the designed
tion management
one
issue
ApmsNetworker ApmsNetWorker startup leads sometimes Mutex

20170725-194829
Mutex creation and Operations closes itself
Issues with hot-

Hotkeys based faceplate launch from a graphic
20170727-197629 keys based face-
display sometimes does not work
plate launching
PowerExplorer
Client is switched to full screen; any additional
20170816-218607, does not work
tabs open aside from primary tab cease work-
20180129-405406 properly in Full
ing.
Screen
ICI fails to start

when TextStrings
ICI fails to start when TextStrings tag types are
20170818-221522 tag types are in-
included in the tag database
cluded in the tag
database
Alarm list foreground color does not follow the

defined priority color
Solution:
In alarm list, by default system displays alarm

texts using black.
This behavior can be customized by system set-

ting called “EnableAlarmTextColor” (BOOL) un-
Alarm list fore- der APPS\Alarms,
20170905-238352 ground color
problem NO = This is by default and texts are display in
black YES = Text color displayed as per the color
definitions of Battdeck.xml. In case background
and foreground color of an entry in alarm list is
being equal or similar, text may not be legible.
Hence, system automatically calculates the color
value of foreground to make the text legible
which may not be user configured color.
8 VZ Z 0 0 12 8 8T 2 12 0 A 41
FI XE D P R OB LE M S M O DI FI CAT I ON S IN T HI S R EL E A SE
Modbus RTU
if configured with more than one device, discon-
Scanner: CF issue
20170907-241157 nection of the device does not lead the tag qual-
when configured
ity to Channel Failure
with multidevice
MSDD tag type

20170915-250736, atoms are de-
MSDD tag type atoms are decoded erroneously
20180125-401333 coded errone-
ously
Modbus RTU
Scanner: datatype Scanner does not support data type 4
20170920-254588
4 is not sup- (FIELD_AD4)
ported
Mismatch of ex- The Tag values exported from trend into CSV
20170929-285079 ported trend val- format does not match with the trace values
ues shown in trend
Unable to com-
municate few sig-
20171004-288998 nals from third Unable to communicate few signals from third
party IED’s using party IED’s using IEC61850 connectivity
IEC61850 connec-
tivity
Station tags are

not aligned Station tags are not aligned across servers dur-
20171117-336739
across servers ing startup
during startup
Memory Leak in Memory Leak in NpowerInterop’s Marshalling

20171123-342613
NpowerInterop functions.
Legends are
empty beneath
Legends are empty beneath the embedded
20171220-369560 the embedded
trends in Web portal
trends in Web
portal
No SOE report
can be created af-
No SOE report can be created after an ICI dis-
20180124-399793 ter an ICI discon-
connect and ICI reconnect
nection and re-
connect
42 8V Z Z 0 01 2 88T 2 12 0 A
Inverted function of Printscreen does not work

properly
Solution:
“smooth edges of screen fonts” must be disa-

bled in OS. Follow the steps to disable the same.
Navigate to Start > Control Panel > System and

Security > System, click Advanced System Set-
ting from the left pane.
Printscreen: In-
20180129-404472 verted color does
not work properly Select Advanced tab and then click Settings in
Performance. Select Visual Effects, and uncheck
Smooth edges of screen fonts and then Apply
8 VZ Z 0 0 12 8 8T 2 12 0 A 43
Modbus TCP
Issues related handling of word/bytes of Mod-
20180222-434624 Scanner: Commu-
bus pocket handling
nication issues
TntXmlVwr re-
20180313-455825 TntXmlVwr returns error
turns error
Sometimes Pow-
erexplorer
Sometimes Powerexplorer crashes during visual-
20180313-455877 crashes during
ization of historical trends
visualization of
historical trends
Quality related is- In OPC Tags, only Mainatom is set to CF (Chan-

20180418-499863 sues with OPC nel Failure) and other atoms remains in Good
tags quality when OPC Client is dis-connected
CpowerInterOp Memory leakage related issue causing Cpower-

20180503-518530
fault InterOp fault
In alarm list, mouse right click action (Operator

Powerexplorer
20180503-518900 Action) after selecting more than an alarm
crash issue
causes Power Explorer to crash
44 8V Z Z 0 01 2 88T 2 12 0 A
S+ Operations OPC DA Server, respected the con-

nected OPC Client that requests Asynch and Synch
writes operations. It could happen sometimes that 3rd
Party OPC Client does not fully comply OPC specifica-
tions and does not provide proper timeout for com-
mands. This may lead in slow command execution on
S+ Operation OPC DA Server (since server try to grand
requested timeout)
Solution:
This release introduces few system settings under

APPS\OPC in order to allow user to override above
stated possible wrong timeout that allows mapping of
wrong timeouts to meaningful timeouts.
OPC DA Server: Srv_DA_rateReplacement (DWORD), YES/NO. This ena-

Problem in calcu- bles update frequency replacement functionality
20180525-550014
lating in update Srv_DA_rateReplacement_key (DWORD) 999999, This
frequency defines the “key” value, rate value that must be re-
placed with definition of Srv_DA_rateReplace_value
Srv_DA_rateReplacement_value (DWORD) 1000, rate
to be used when S+ Operations OPC DA Server re-
ceives a AddGroup/SetState with requested rate that is
equal to value defined in Srv_DA_rateReplacemetn_key
Note:
This is not a mandatory configuration, however if pro-
ject experiences slow execution of commands from 3rd
party OPC client to S+ Operations OPC DA OPC
Server, it might be possible this problem exists and
timeout expressed by OPC Client must be realized. The
above stated system settings must be configured ac-
cordingly.
All default values are mentioned in BOLD letters.
Powerexplorer: The icons on the toolbar disappear sometimes

20180529-553008 Icons disappear when a server is turned off or server switched
sometimes using “Change Server” option
Connections is-
sues between Op- Connection issue with S+ Operations Server and
20180530-555740 erations Server Operations History servers leading to data
and Operations losses on the Operations History
History
Task Moni-
tor/PwMoni-
torSrv - does not Task Monitor/PwMonitorSrv - does not restart
190349
restart the com- the computer on a process crash
puter on a pro-
cess crash
8 VZ Z 0 0 12 8 8T 2 12 0 A 45
AC800MImporter
doesn’t support AC800MImporter doesn’t support System
ABB2015111500014
System 800Xa 5.1 800Xa 5.1 FP4 and 6.0.3
FP4 and 6.0.3
Node database
alarm does not
Node database alarm does not show proper cur-
ABB20160202E0304 show proper cur-
rent value when Return to Normal
rent value when
RTN
Textstr not working right - when we enter data

into the dataexport faceplate pop-up on the S+
console, it does not successfully update the da-
Text String tags taexport block in the controller.
ABB20160215E0179
does not work
ABB2017042000070 Solution:
properly
This scenario noticed only when PPB and S+ Op-
erations consoles coexist in a system. Text
string command issue has been fixed.
ApmsNetworker
ABB2016030200067 ApmsNetworker crashes at startup
crashes at startup
Improper shut-
Reboot of computer without proper shutdown
down of S+ Oper-
of S+ Operations server leads data difference
ABB2016031100008 ations server
between playback and Operations History, thus
causes trend
trend curve zooming problems realized.
curve problems
SNMP Trap Driver

ABB2016032900044 SNMP Trap Driver Documentation
Documentation
Bad Quality
alarms are never Bad Quality alarms are never get set to
ABB20160517E0191
get set to unacknowledged
unacknowledged
N90STA diag tag N90STA diagnostic tag of PNI800 does not re-
ABB2016060300192 of PNI800 related port alarm/warning when one of the ethernet
problem cable is disconnected
Solution:
Status byte of
ABB2016060800326 N90STA tag into This release captures status bytes received from
alarm message modules are captured as part of alarm message
of the status tag
46 8V Z Z 0 01 2 88T 2 12 0 A
Scrolling down on alarm page is not possible on

some clients due to automatic jump back to top
alarm function.
Solution:
This release introduces below mentioned sys-

tem setting under APPS\Alarms
“AlarmPageAutoScrollUpOnNewAlarm”
Alarm page scroll (DWORD), YES/NO
ABB2016102800025 down related is- In case there are more alarm in alarm page than
sue visible ones, scroll bar is enabled. If the user in-
specting alarms in the list by scrolling down, and
meanwhile a new alarm arrives causing alarm
page to automatically scroll up to first line.
Incase this setting is set to NO, on the arrival on

new alarm automatic scrolling does not take
place and remains at current user position. The
alarm page header blinks in order to notify the
event, until the user won’t scroll up again.
Possibility of visualizing number of active alarm

at Operator Station regardless of Ack/Unack
status. In such cases, color the alarm group shall
be follow the highest priority alarm regardless
of Ack condition.
Solution:
Follow the settings below to achieve such visual-

ization,
Welcome_DALL:
Edit the Workplace Layout database of the de-
Possibility of visu-
sired user and customize the “Top Navigation
alizing no. of ac-
ABB2016102800026 View” to WELCOME_DALL_TOTAL.
tive alarms by
group and total Set “AlarmSummaryOnUnackedAlarms”
active alarms (DWORD) value to 1 under APPS\Alarms.
If value set as 1: Count of alarms will be of items

with unacknowledged state.
If value set as 0: Count of alarms will be of all ac-

tive alarms regardless of Ack state.
Note:
Restart of Operations Server is required for

changes to take effect.
Data hanging up on Server after loss of power.

Data hanging up
Erroneously frozen values on some servers dur-
ABB20161111E0063 on Server after
ing network outage. Should be BQ values during
loss of power.
network outage.
8 VZ Z 0 0 12 8 8T 2 12 0 A 47
New SOE Report SOE report missing when Max Xrp time is
ABB2016113000001
issues greater than SOE signal change frequency
Compatibility of S+ Operations with Freelance
Solution:
Compatibility of
Freelance 2016 SP1 with latest rollup under Win-
ABB2016120200163 S+ Operations
dows 10/Windows Server 2016 as Operating Sys-
with Freelance
tem is supported. The required package can be
downloaded from respective location of ABB Li-
brary
Missing docu-
mentation about Missing documentation about Timer ON and
ABB2016120600025
Timer ON and Timer OFF alarm
Timer OFF alarm
Millisecond resolution is displayed in the trend

scooter.
Solution:
Millisecond reso-
By default, when the trend area shows less than
lution is not avail-
ABB2017012700023 30 seconds as the threshold, the scooter in-
able in the trend
cludes millisecond in time indication.
view
The threshold seconds can be configured using
following system setting under APPS\TREND
ScooterMsecMoveThresholdInSec (DWORD)
Quality codes are

reported in HEX
Quality codes are reported in HEX after export-
ABB2017012700025 after exporting
ing the data to MS Excel
the data to MS Ex-
cel
Power explorer crashes while using mouse scroll

wheel in alarm groups
Solution:
Power explorer
crashes while us- To avoid any crash on Power Explorer while
ABB20170201E0039 ing mouse scroll scrolling a system setting introduced and can be
wheel in alarm configured using following system setting under
groups APPS\PowerExplorer
WatchdogMsgBoxAlarmGroup_msec" (DWORD)
and by default 0 which keeps this functionality
diabled. Recommended value is “500” msec.
48 8V Z Z 0 01 2 88T 2 12 0 A
DANG atoms for showing HH, HHH, LL, and LLL

reports RTN when Inhibit is set
Solution:
DANG: Incorrect Alarm Level L and H are received from Controller

ABB2017020800023 reporting of while HH, HHH, LL, and LLL and calculated inter-
Alarm Levels nally by S+ Operations.
The above is modified in this release and all six

alarm levels (H, HH, HHH, L, LL, and LLL) are ob-
tained from controller only and reported cor-
rectly.
Tag going from Acknowledged Alarm state to

BQ state, BQ alarm doesn’t blink rather alarm
color is updated as per BQ and Timestamp re-
Tag going from
mains same.
Acknowledged
Alarm state to BQ Solution:
state, BQ alarm
ABB2017020900016 Considering BQ as a sub-condition, as per
doesn’t blink ra-
EEMUA the Active Time of the event is preserved
ther only alarm
until end of alarm life cycle and Tag is reported
color is updated
as Active Unacked one that leads the blinking of
as per BQ
alarm in alarm list. Also, such sub-condition
change reported as event with changed event
time so that user can refer it.
Alarm inhibit does not work if tag is in Channel

Failure state
Solution:
By, default Bad Calculation, and Channel Failures

Alarm Inhibit does are not considered for Alarm Inhibition. In order
ABB2017020900036 not work if tag is to treat them like other alarm conditions for
in CF alarm inhibition, and let the alarm inhibition
function inhibit Bad Calculation, and Channel
Failure, it is necessary to set the following Sys-
tem Settings under OPTIONS,
BadQualityAlarms (BOOL) to YES.
OPC AE Server:
ABB2017032700053 Wrong event type OPC AE Server: Wrong event type for RTN
for RTN
Enhanced Analog
Enhanced Analog and Digital faceplate’s User in-
and Digital Face-
put enable/disable command buttons works
ABB2017032900100 plates: User ena-
only with master nodes, and doesn’t work non
ble/disable re-
master nodes
lated issues
8 VZ Z 0 0 12 8 8T 2 12 0 A 49
Thin web client does not display the curves/val-

ues of the embedded trends.
Solution:
Serialization of graphic items in XML is finished

Thin client does before retrieving trend data from server causing
not display the above issue. A system setting introduced as de-
ABB2017040600076
curves/values of fined below under APPS\Trend that defines the
embedded trends maximum wait (in msec) time for server re-
sponse containing trend data during XML seriali-
zation.
XmlCurvesExportingServerTimeout (DWORD),
default 6000.
Trend scooter
value does not Trend scooter value does not show decimal
ABB2017042600082
show decimal places
places
ApmsNetWorker saturates the RAM when Sys-

tem Setting “UseOPCComputerForExtendedRe-
dundancy” is Set to YES and Alias.xml is used for
Process Ap- OPC communication
ABB2017042600082 msNetwork satu-
Solution:
rates the RAM
It recommended that “UseOPCComputerForEx-
tendedRedundancy” must be set NO under
APPS\Netserver when Alias.xml is in use.
Unable to save
ABB2017071400006 print preview as Unable to save print preview as BMP from client
BMP from client
Table 4-1 Fixed Problems
50 8V Z Z 0 01 2 88T 2 12 0 A
M O DI FI CAT I ON S I N T HI S R E LE A SE K NO W N P RO B LEM S A N D W O R K A R OU ND S
4.4 Known Problems and Workarounds
Tracking Title Description

number
126914 Windows 10 Under following settings, resizing window containing trend

LTSB 2015 causes to freeze Windows OS.
Operating
System [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ABB
freezes with Symphony Plus\Operations\General]
Japanese lan-
guage fonts "CurrentLanguage"="Japanese"
when resized
Solution:
Microsoft has released the fix which must be applied. Fix

can be downloaded using below link:
<http://www.catalog.update.microsoft.com/Search.aspx?q=KB40489
56>
ABB2016081 User input For enhanced analog and digital tags, faceplate's enable user
6E0365 disable/ena- input/disable user input command buttons work only on cli-
ble command ents connected to the “Master” server. The redundant serv-
buttons do ers which are not “Master” do not receive the enable/disable
not work button command when issued from clients.
from non-
master S+ Workaround:
Operations
Server Set the weight of ServerA to be 1 Higher than the ServerB
(For example ServerA node weight = 10 and ServerB node
weight = 9), and then just operate with clients connected to
ServerA (With reconnection connection policy of always con-
necting back to ServerA in case of Online), This way if Serv-
erA goes down, ServerB would be the “Master” and there
would be no Issue, and if ServerA is back to online, all the cli-
ents would connect back to it so they can remain connected
to the “Master” server.
170347 Auto log out In case Auto logout is configured, after defined timeout log-
does not out does not work successfully.
work
8 VZ Z 0 0 12 8 8T 2 12 0 A 51
K NOW N P RO B LEM S A N D WO RK AR OU NDS M O DI FI CAT I ON S IN T HI S R EL E A SE
169862 ExImNew Configure Export class windows doesn’t display “EventEx-

Tool: Event port” column
Export col-
umn not Workaround:
available in
'Configure Following system setting must be set:
Export Clas-
ses" tab HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Hart
mann & Braun\PlaCoEM = “MS”
112686 Return to Aud_rtn definition in the Battdeck.xml doesn’t work

Normal audi-
ble does not Workaround:
work
Create Batt2deck.xml and modify attribute aud_rtun = Y,
then build the file.
123225 Engineering Off alarm check and Off Scan do not work for Engineering
Role unable Role even with privileges enabled.
to request
Off Scan or
Off Alarm
Check
117052 Bad Quality S+ Operations Server reports Bad quality alarm for all INFI
alarms are tags when S+ Operations servers loses its connection with
not cleared ICI (In redundant environment both Server losing connection
from Alarm with ICI). When Server ICI connection is restored, INFI tags in
List when Servers directly connected to ICIs are back to good quality
tags are back but S+ Operations servers which receives the same INFI Tags
to Good through network communication remains with bad quality
Quality. alarms status.
Workaround:
User need to login as System manager in S+ Operations

server and manually remove alarm (Bad quality) from alarm
list.
52 8V Z Z 0 01 2 88T 2 12 0 A
102565 Extended Re- In Extended Redundancy, Limit value changes in controller

dundancy: configuration are not populated into Operations servers,
Specification causing the display of different values in Operations servers
changes on that may not be current limit value as per controller configu-
controllers ration.
are not repli-
cated into Workaround:
Operations
servers. Specification propagation must be enabled, to enable the
propagation of limits to other servers, below mentioned set-
ting is required
APPS\INFINET INTERFACE\PropagateSpecs = 1. This need to

be set in order to propagate the specifications properly in a
hierarchical system.
The following setting is optional,
APPS\INFINET INTERFACE\PropagateSpecsOnlyIfMaster =1
This is to manage the possible high traffic due to the fact

that multiple servers are reading specification and propa-
gating to remote servers.
108157 Menu Icons On a quad view monitor, when client switches from the
missing stopped server to the available running server, power ex-
when Client plorer does not display menu icons.
automatically
switches be- Workaround:
tween Serv-
ers. No of items that are supported in Menu database is 1000.
Problem occurs if number of displays are configured in fly-
out is more than < 150 Nos. It is recommended to size the
menu items considering above stated figures and also
based on the size of the menu, adjust the TcpIp-
CallTimeoutSec setting
102556 Extended Re- At ICI restart, ICI comes online prior to the establishment of
dundancy for all tags. The server in which ICI is restarting (Not the server
Harmony Not restart) may report quality as bad for tags, causing unavaila-
working bility of control from the connected clients. Commands on
Properly those clients are not available if data is bad, but is available
on another client connected to a different server where qual-
ity is good.
Workaround:
Clients connected to other server where data is good can be

used to send commands.
8 VZ Z 0 0 12 8 8T 2 12 0 A 53
108153 APMSMoni- Extended Redundancy table in APMSMonitor will close out

tor automati- the APMSMonitor, if the mouse went over an undefined ta-
cally closes ble entry or row.
while hoover-
ing mouse on
extended re-
dundancy ta-
ble.
105946 Alarm Portal Graphs in Alarm Portal are not displayed in Internet Explorer
Graphs are while they work fine in Operations Explorer.
not displayed
in Internet Workaround:
Explorer 11
Enable Compatibility view settings in Internet Explorer.
Press the Alt key to display the menu bar

Click the Tools menu and choose Compatibility View Set-
tings Add Alarm Portal URL.
105817 Power Ex- If a new display is created with a XYPlot object and another
plorer display with Horizontal Bar object with same tag assigned
crashes if a then at runtime while using reference from the display
reference Power Explorer crashes.
from a XY
plot display
is used.
102655 Alarms not In case of very high number of active alarms (>2000) in an
aligned be- alarm group, it may happen that they are not propagated
tween serv- properly to other servers. There might be misalignment is-
ers sues.
Workaround:
Alarms may be required to acknowledge from multiple serv-

ers.
106042 Composer Full deploy using wizard (Single Server Configuration) for the
Operations first time fails.
Full Deploy
fails for the Workaround:
first time
with default Do not set HSIServer property in CO before a full deploy.
wizard con-
figuration Leave it blank, do a full deploy and then set it afterward either
manually or using CO with an action set including the follow-
ing two actions:
- "Configure ClientServer Settings: Set HSI Servers"
- "Configure ini file (LifeCheck): Server
54 8V Z Z 0 01 2 88T 2 12 0 A
89841 Partial Re- Bulk edit operation is carried out for changing Alarm Priority,
place option Alarm High Priority and Alarm Low Priority using Partial Re-
for Tags with place option with System Setup does not work properly.
System
Setup does Workaround:
not work
properly. For such a bulk operation, it is required to re-initialize the
whole Tag DB using System Setup in order to apply the
changes correctly.
ABB20151113 Diagnostic Workaround:

E8941/ Driver keeps
104368 restarting it- Do not create diagnostic tag using this option, if necessary
self if default create and restart S+ Operations Server.
diagnostic
tags are cre-
ated online
using option
“Reload Diag-
nostic Tag” in
ApmsMoni-
tor.
102132 Harmony DANG tag type does not update Alarm Active Time when go-
DANG tag ing from H to HH/HHH or from L to LL/LLL. This is to con-
type does form the Industry Standards.
not update
Alarm Active
Time when
going from H
to HH/HHH
or from L to
LL/LLL.
102009 PNI Shows When S+ Operations loses connection to the IET/PNI and re-
Online prior stores the connection again, SPO Server goes online without
to all Points all points being established with good quality. So, Clients at-
being estab- tached to Server may show Bad Quality until established.
lished
Workaround:
After the start-up of PNI, wait until all the points are not es-
tablished.
Additionally, value of
“\APPS\PwMonitor\DelayExtRedMonitoring_sec” setting
can be tuned higher number (for e.g. 600 sec from 300 sec),
if there are high number of tags connected to SPO Server.
This setting introduces the delay before SPO Server shows
online status.
8 VZ Z 0 0 12 8 8T 2 12 0 A 55
N/A Harmony: Workaround:

Time synch is
not working S+ Operations console can be used as time synch master.
properly
when PPB or
CNT Con-
soles are the
time synch
masters
67263 Historian Di- Workaround:

agnostic Por-
tal: In a do- Login using a local user which belongs to one of the following
main windows groups:
environment,
diagnostic – SpOAdmins
portal login – SPlusOAdmins
does not
work.
58868 AC800M Workaround:

Connect: The
import of If multiple databases are required to import to remote ma-
multiple da- chine. Import one database at one time and repeat import
tabase on re- process for each database one by one.
mote ma-
chine fails for
some data-
bases with
error
N/A Logical col- Workaround:

ors defined
with RGB Logical colors with the RGB value as 0,0,0 can be listed by
value as 0,0,0 creating the following registry key:
are not listed
in Display \ABB Symphony Plus\Operations\Options\De-
Builder’s log- faultUndefinedColor = 16646398
ical color list.
Restart S+ Operations for changes to take effect.
46232 Login of win- If Windows User is logged in to another user without logging
dows user off from the current session using Switch User functionality
into S+ dif- then the behavior of the users are not deterministic.
ferent for cli-
ents with dif- Workaround:
ferent higher
priority serv- This behavior is not supported by design. To avoid prob-
ers lems disable Switch User functionality of windows. Refer to
configuration guide for detailed steps.
56 8V Z Z 0 01 2 88T 2 12 0 A
51097 Power Explo- Power Explorer freezes if system is used with 16 bpp color
rer Frozen depth.
Workaround:
Always use 24 or 32 bpp color depth settings or monitors.
ABB20120718 Additional There are always some additional thick line frame in blue on
-0052 Thick line the graphic. It covers some display area, may cover useful in-
frame in blue formation.
around the
graphic ob- Workaround:
jects
The feature can be disabled setting the registry
APPS\PowerExplorer\SelectedFrame=NO
54508 Historian Historian Server diagnostic web page can only be accessed
Web page is using (http://localhost:89). This is default configuration.
only accessi-
ble from local Workaround:
machine
In case it is required to access the diagnostic page from re-
mote machine, an RDP connection to host machine can be
used.
ABB2014021 Inconsistent Sometimes it may happen that HISINDEX gets lost.

9-0282 HISINDEX As-
signment for Workaround:
Historian
Tags If the HISINDEX of tags or atoms have been lost, they can be
restored with the TagSync service in 2 ways:
1) Change the entry "recreatetags" to 1 in the INI file of the

TagSyncService (\\Program Files (x86)\ABB Symphony
Plus\Operations\History\PlantConnect.BIN\PwTagSync
\PwTagSync.ini).
recreatetags=1
In the next cycle TagSync recreates the indexes (no restart

necessary)
2) Simply restart the TagSync service. At start TagSync rec-

reates the indexes automatically.
ABB2012092 History Sys- On RDP connection Historian Server shows in “System Diag-
8-0126 tem Diagno- nostic ": "Check Failed Code: Dongle_Not_Installed".
sis shows
Failed license Workaround:
check: “Don-
gle Not In- Validate license directly on the history server, not using re-
stalled” mote connection (RDP)."
8 VZ Z 0 0 12 8 8T 2 12 0 A 57
51384 General It may happen that after running general setup from system
Setup proce- setup utility, S+ Operations HSI Service gets removed.
dure removes
Operations Workaround:
HSI service
There are two ways to install the service again:
Run PGPPostInstallation.exe located in S+ Bin folder.
OR
Execute command “apmssvc –i” from command prompt un-

der Symphony Plus Bin folder.
ABB20140317 S+ Event Ex- Workaround:

-0189 plorer Events
are different In case events are not synchronously stored during normal
on both Op- operations, then the Events will be automatically synchro-
eration nized after every 30 minutes.
Server - miss-
ing events
N/A Harmony String length (Spec 4) is not reported as atom.

connect
FC194(DATAE Workaround:
XPT) support
User can use block details utility to view string length and
ensure the entered string length is well within the limits of
Spec 4.
ABB20150112 Alarm List In Alarm Group database, Primary display field supports
-0367 Primary Dis- only 18 characters.
play Limited
to 18 Charac-
ters
163932 Unable to In case of standard menu database file is used to build the
open user menu and toolbar of the PowerExplorer, It is not possible to
documenta- launch User Documentation from PowerExplorer toolbar but-
tion ton.
Workaround:
Edit the command line for the program of menu label “User
Documentation” to “$Documents\2VAA001150-210_-
_en_S+_Operations_2.1_Operations_User_Guide.pdf”
58 8V Z Z 0 01 2 88T 2 12 0 A
166525 System Set- System settings tool doesn’t show sizes related registry keys
tings Tool while comparing loaded registries and REGCONF.xml
doesn’t show
sizes Workaround:
In the node where system settings tool is being used, edit the
REGCONF.xml file and remove “Install=NO” flag from follow-
ing,
<REGENTRY path="Startup\<ProgramName>"
name="CommandLine" descr="##internal## Command line
for the defined program" type="STRING" server="Y" install
="NO"/>
169346 OPC Client OPC client running under low privilege doesn’t work
running un-
der low privi- Workaround:
lege user
Refer to Operations Configuration Guide in section 3.8 and
configure the DCOM settings as mentioned in the table, then
Add/Update the registry key called AppID (Type = REG_SZ)
with the value of “{F5A1DB28-D938-4E0A-9A1E-
65658D093CA8}” in the following path,
Com-
puter\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow64
32Node\CLSID\{E39AEE68-B6A3-4FBE-BBF0-
2B7666EC7F13}
Note: After configuration restart the S+ Operations Server
8 VZ Z 0 0 12 8 8T 2 12 0 A 59
169823 Server In case of ABB S+ Operations HSI service running under SPlu-
doesn’t work sOServiceUser, some of the feature\application doesn’t
properly in- work properly.
case HSI ser-
vice running Workaround:
under SPlu-
sOServiceUs It necessary to grant DCOM permissions to SPlu-
er sOServiceUser for the OpcNodeServer and IciServer applica-
tions as follows,
Execute “dcomcnf” using Windows Run Prompt, navigate to

Console Root > Component Services > Computers > My Com-
puter > DCOM Config, select above mentioned application
Properties and choose Security Tab to customize the follow-
ing permissions in “Launch and Activation Permissions” for
the “SPlusOServiceUser” user.
Local Launch
Remote Launch
Local Activation
Remote Activation
169827 Historian Life Workaround:

check for
event import It is necessary to grant access to Windows Performance
doesn’t work Counter related user groups. Follow the steps below to grant
access to Writer and Reader users of Historian Life check
· Add “SPlusIMServiceUser” (Writer) user to “Perfor-

mance Log Users” windows user group
Add “SPlusOServiceUser” (Reader) user to “Performance
Monitor User” windows user group
170080 Harmony AUTO/MANUAL button of pop_harm_bias_station_r2 is

Connect Dis- grayed out and not operable
play Library:
pop_harm_bi
as_station_r2
faceplate
Table 4-2 Known Issues and Workarounds
60 8V Z Z 0 01 2 88T 2 12 0 A
I N STA L L ATI O N I N STA L LATI ON
5 INSTALLATION
5.1 Installation
Please follow the detailed instructions mentioned in installation section of configuration
guide
5.2 Upgrading
Please follow the detailed instructions mentioned in configuration guide
5.3 Backup and Restore

Please follow the detailed instructions mentioned in configuration guide
8 VZ Z 0 0 12 8 8T 2 12 0 A 61
Revision History
Rev. Page Change Description Date / Initial
- all Initial release 2018-10-15/

IAPG
—
Visit us
www.abb.com/powergeneration
Document Number: 8VZZ001288T2120 Rev. A

www.abb.com/water
www.abb.com/symphonyplus

8VZZ001288T2120 A en SPlus Operations 2.1 SP2 Release Notes

Uploaded by

Document Information

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

8VZZ001288T2120 A en SPlus Operations 2.1 SP2 Release Notes

Uploaded by

Copyright:

Available Formats

—

PO WE R GE NE R ATI ON & WATE R

ABB Ability™ Symphony® Plus

ABB Ability™ Symphony® Plus

Ability is a trademark of ABB.

Copyright © 2011-2018 ABB.

All rights reserved.

Release: October 2018

Document Number: 8VZZ001288T2120

2 DATA SHEET ................................................................................................................................ 9

4 MODIFICATIONS IN THIS RELEASE .......................................................................................... 37

Figure 1-1: Power Explore Overview

Defined for high performance

Seamless life cycle management

Flexible, Scalable, fault tolerant design

1.2 Executive Summary

1.3 Getting Access to 2.1 Service pack 1

1.4 License change

1.5 Revision Record

A First version is published for October 2018

Table 1-1 Revision Record

– Number of tags in the HSI real-time database

– Total number of clients

– Number of transactions/sec, configuration of signals, process dynamic, etc.

– Expected response time for the users

S+ Operations computer recommendations place a high emphasis on performance in order

Hard disk requirements:

Fast display call-up times:

CPU recommendation for fast call-up time use:

- For operator workstations or Serverless:

- For large servers:

1.7.2 Summary Table

HSI Server History Serverless Operator Full Office Application

RAM Small: 8 GB 8 GB Small: 8 GB 8 GB 4 GB Small: 8 GB

OS Windows 10 Windows 10 Windows 10 Windows Windows Windows 10

Hard As required Min. 3x 100 As required As re- As re- As required

Video Recommen- Recommen- Recommen- Recom- Recom- Recommen-

Table 1-2 Hardware requirement summary table

1.7.3 Software Requirements Details

– Windows 10 Enterprise LTSC 2016, 64 bit, English

– Windows Server 2016 Standard Edition, 64 bit, English

3rd party software as the following:

– Microsoft Office 2016, 2013 SP1 Standard or Professional 32 bit

– Microsoft SQL Server 2016 Standard Edition, 64 bit

– Microsoft Internet Explorer 11

- for AC800M connectivity

1.7.4 Hardware Serverless Configuration

1.7.4.1 Small (<1000 tags) Workstations

1.7.4.2 Large Workstations

1.7.5 Hardware Server based Configurations

1.7.5.1 Small system servers <1000 tags

1.7.5.2 Large systems servers with or without separated history

1.7.5.3 Large systems servers with integrated history

– Processors with faster cycle times

– Usage of solid state disks

1.7.5.4 Volume estimation of hard disks for History Server

Real-time value history:

1.7.5.5 Application server

1.7.6 Hardware clients

1.7.6.1 Operator clients for server based configurations

1.7.6.2 Full office client

Workstations should be at least I3 processor with a minimum of 4 GB RAM.

2.1 Serverless architecture