Uniformance®

PHD Server
Specification Sheet
R321
 Copyright, Notices, and Trademarks
© Honeywell Inc. 1998 – 2014. All Rights Reserved
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.

In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.

Honeywell, Experion, TotalPlant, Uniformance PHD, and Business.FLEX are U.S. registered
trademarks of Honeywell Inc.

Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions

1860 W. Rose Garden Ln
Phoenix, Arizona 85027-2708 USA
 Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website
at: http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your feedback to:
hpsdocs@honeywell.com
Use this email address to provide feedback, or to report errors and omissions in the
documentation. For immediate help with a technical problem, contact your local Honeywell
Process Solutions Customer Contact Center (CCC) or Honeywell Technical Assistance Center
(TAC) listed in the “Support and other contacts” section of this document.

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or weakness
that can be exploited to reduce the operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and
services.
To report a potential security vulnerability against any Honeywell product, please follow the
instructions at: https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:

• Send an email to security@honeywell.com.

or

• Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or
Honeywell Technical Assistance Center (TAC) listed in the “Support and other contacts”
section of this document.
 Support and other contacts
For support and other contact details, go to http://www.honeywell.com/ps.

World Wide Web

Honeywell Process Solutions website: http://www.honeywellprocess.com/support

Elsewhere
Contact your nearest Honeywell office.

Training Classes
Honeywell Automation College: http://www.automationcollege.com
 Contents

1. Architecture Overview ..................................................................................... 9

Architecture examples ......................................................................... 9

2. Important Considerations in PHD System Sizing ......................................... 11

2.1 Introduction.......................................................................................... 11
2.2 PHD Server ......................................................................................... 12
2.3 Calculations and Virtual Tags............................................................... 15
2.4 Roles ................................................................................................... 16
2.5 Data Collection and RDI Server ........................................................... 16
2.6 Standard RDIs Available ...................................................................... 17
2.7 Remote Peer Interface ......................................................................... 18
2.8 PHD OPC Server ................................................................................. 19
2.9 PHD Applications ................................................................................. 23
Consolidated Event Journal (CEJ) ..................................................... 23
EJC RDI for Consolidated Event Journal (CEJ).................................. 23
EPKS RDI for Consolidated Event Journal (CEJ) ............................... 23
OPCAE RDI 1.10 for Consolidated Event Journal (CEJ) .................... 23
PHD to Relational .............................................................................. 24
Peer Tag Sync .................................................................................. 24
Experion Tag Sync ............................................................................ 24
 Figures
Figure 1 - Small scale PHD system ............................................................................. 9
Figure 2: Medium scale PHD system ......................................................................... 10
 1. Architecture Overview
A PHD implementation may consist of many different integrated hardware and software
components depending upon the needs of the customer. The following architecture
examples represent two of the many possible topologies that can comprise a PHD
implementation. The architecture is highly scalable and not all nodes are necessary or
required. In some cases, it may be advisable to combine multiple functions on a single
Windows server; while in other cases; distributing functions across multiple servers may
provide the best system security and scalability. The following guidelines apply to PHD
310 and subsequent releases.

Architecture examples

Small scale system

Figure 1 - Small scale PHD system

Uniformance - PHD Specification Sheet • 9

1 Architecture Overview
2.1 Introduction

Medium scale system

Figure 2: Medium scale PHD system

10 • Uniformance - PHD Specification Sheet

2. Important Considerations in PHD System Sizing
2.1 Introduction
The following tables outline the supported maximums for the PHD system. The ability
of a customer to reach one or more of these limits depends on numerous considerations
including, but not limited to the following:
• Server physical memory
• Processor speed
• Number of processors
• Disk space
• Number of system limits being stressed
• Network capacity
• Configuration and system tuning
• Amount of server load imposed by other applications.
This Specification Sheet also identifies the recommended hardware. In the case of
heavily loaded systems, it is recommended that Honeywell Services be consulted to plan
an appropriate server configuration.
As each installation will be uniquely tailored to the site’s needs, there may be
configurations that exceed specified limits. While these configurations may be
acceptable; it is recommended that the site contact Honeywell to review the
configuration. Some of the limits may be attained only when using high-end hardware -
Honeywell Services should be consulted when in doubt. It is important to remember that
PHD has been designed to take full advantage of all available hardware resources (such
as number of processors, hyper threading, and memory) to provide maximum
performance and capacity.

It is important for all ‘large scale’ system configurations, that the site validate
performance and capability on the target configuration.

Uniformance - PHD Specification Sheet • 11

2 Important Considerations in PHD System Sizing
2.2 PHD Server
2.2 PHD Server
Parameter Specification
Total number of tags 2,000,000
Data types supported Type ‘I’ – 32-bit Integer
Type ‘L’ – 64-bit Integer
Type ‘F’ – Single precision
Type ‘D’ – Double
precision
Type ‘C’ – ASCII String
Type ‘U’ – Unicode String
Type ‘B’ – Binary Data
Maximum BLOB tag 32,500
size
12 • Uniformance - PHD Specification Sheet
Comments
For higher-end
systems or if a larger
number of tags is
required, it is
recommended that
Honeywell Services be
consulted when
planning or configuring
these system.
-
Maximum data size is
controlled by two PHD
parameters:
MAX_USEVALLEN
which defaults to 255.
This controls the
maximum amount of
memory PHD allocates
for each value in
processing requests.
MAX_ARCRECSIZE
which defaults to 2048.
This controls the
record size within the
archive files and must
 2 Important Considerations in PHD System Sizing
2.2 PHD Server

Parameter Specification Comments

be changed if larger
data sizes are
required.
Maximum string tag 32,500 characters See above.
size
Number of connected 8192 While PHD permits up
archives (memory permitting) to 1024 open archive
files, the actual
number of open
archives is constrained
by the available
system memory.

Maximum archive 32GB In general, larger

size archive sizes are
recommended for
optimal data retrieval
response times.
Concurrently 10,000 The number of
connected users concurrent requests is
limited by the system
resources and by the
number of available
pool threads which, by
default, is 256

Default limit imposed

by APIServer is 100.

Uniformance - PHD Specification Sheet • 13

2 Important Considerations in PHD System Sizing
2.2 PHD Server

Parameter Specification Comments

PHD Server and RDI 65535 Calculate the number
cross reference table of RDIs times the
number of servers
running those RDIs.
For example, if an RDI
is running on dual
RDC collectors and
two shadow servers, it
should be counted four
times. If the machine
in question is one of
the hosts, then
subtract one (1).
Default maximum is
256, but can be
increased using the
Registry setting
RdiHostTableSize.

maximum tagname 32 characters

length
maximum source 40 characters
tagname length

maximum extended 300 characters

source tagname
length
maximum RDI name 10 characters
length
maximum logical 10 characters
archive name length
maximum physical 14 characters
archive name length

14 • Uniformance - PHD Specification Sheet

 2 Important Considerations in PHD System Sizing
2.3 Calculations and Virtual Tags

2.3 Calculations and Virtual Tags

Parameter Specification Comments

Number of functions 128,000 Includes 1D, 2D, and

3D lookup tables
Default limit is 100 and
is controlled by the
PHD parameter
MAX_PRCFUNC.

Number of modules 128,000 Default limit is 1,000

and is controlled by
the PHD parameter
MAX_PRCMODULE.

Levels of nested 32 for calculations Nested GetData

virtual tags requests are limited to
64.
Number of function 128 -
arguments
Calculation registers 64 -
Number of characters 300,000 Includes 1D, 2D, 3D
in a virtual tag lookup tables, PHD
definition functions, and virtual
tags.
Length of a 2047 -
calculation string

Number of input tags 2048 -

Uniformance - PHD Specification Sheet • 15

2 Important Considerations in PHD System Sizing
2.4 Roles

2.4 Roles
Parameter Specification Comments

Number of PHD 287 -

roles
Maximum roles per 287 Always uses INTS in
user 320

2.5 Data Collection and RDI Server

Parameter Specification Comments

Number of RDI 25 -
Servers per physical
server
Number of RDIs per 25 for Shadow Servers While the default is
RDI Server with Active and Standby approximately 25, this
nodes configured number can be fine
tuned using system
100 registry settings (with
the consultation of
Honeywell Services)
Fastest collection 1 second The number of tags
rate that can be collected
at this rate is typically
constrained by the
capacity of the data
provider.
Slowest collection 1 day -
rate

16 • Uniformance - PHD Specification Sheet

 2 Important Considerations in PHD System Sizing
2.6 Standard RDIs Available

Parameter Specification Comments

Maximum tags per 400,000 While an RDI may be
RDI assigned 400,000
Typically 25,000 - 50,000 tags, it is typically
advisable to have
more RDIs with a
lower tag count and
collection offsets to
balance load against
the data provider.

2.6 Standard RDIs Available

Honeywell Model Name Comments
Number
Type “A” Interfaces - -
TP-RDIN52 Experion Link Used with Experion
R310 and later
TP-RDIN01 Remote LxS RDI Runs on an APP
node, and collects
data from a TPS
system (LCN)
TP-RDIN06 Experion/PlantScape RDI Used with
PlantScape and
Experion releases.
Beginning with PHD
210 and Experion
300, Experion Link is
the preferred
interface.
TP-RDIN12 OPC RDI -
TP-RDIN14 OPC RDI for Honeywell -
systems
TP-RDIN30 File Access/FTP -

Uniformance - PHD Specification Sheet • 17

2 Important Considerations in PHD System Sizing
2.7 Remote Peer Interface

Honeywell Model Name Comments

Number

TP-RDIN31 File Access/FTP for -

Honeywell systems
Internal RDIs - These interfaces are
included in the PHD
server license.
Gateway RDI -

Shadow RDI -
Manual Input RDI -
Virtual Tag RDI -

Test RDI Sine wave simulation

interface

ATTENTION
All RDIs are licensed per “area”, which is roughly equivalent to a PHD
collector and shadow “system”.

Numerous additional RDIs have been developed on a project basis.

Contact Honeywell if an interface is required for a system that is not listed
here.

2.7 Remote Peer Interface

Parameter Specification Comments

Number of remote 20 if run as a specific user -

peers on a PHD
server 100 if run under the local
System account

18 • Uniformance - PHD Specification Sheet

 2 Important Considerations in PHD System Sizing
2.8 PHD OPC Server

2.8 PHD OPC Server

Parameter Specification Comments

OPC DA versions 1.0a, 2.05, and 3.0 -

supported
OPC HDA versions 1.1, and 1.2 -
supported

Number of PHD 1 -
OPC Servers
installed on a
Windows server
Number of PHD 100 -
OPC Servers
connected to a PHD
server
Number of OPC 50 This also
clients connected to depends on if
a single PHD OPC the OPC
server server is
collocated
with PHD
server or on a
standalone
box. RDM is
assumed not
to be installed
for this
number.

Uniformance - PHD Specification Sheet • 19

2 Important Considerations in PHD System Sizing
2.8 PHD OPC Server

Parameter Specification Comments

Maximum OPC 80 Based on
Groups supported 'maximum
tags per
group' (5,000
items per
OPC group)
and maximum
tags
(400,000),
then 400,000 /
5,000 = 80.
Maximum tags per 5,000 -
OPC group
HDA server OPCHDA_INTERPOLATIVE -
aggregates
implemented OPCHDA_TOTAL
OPCHDA_AVERAGE
OPCHDA_TIMEAVERAGE
OPCHDA_COUNT
OPCHDA_STDEV
OPCHDA_MINIMUMACTUALTIME
OPCHDA_MINIMUM
OPCHDA_MAXIMUMACTUALTIM
E
OPCHDA_MAXIMUM
OPCHDA_START
OPCHDA_END
OPCHDA_DELTA

20 • Uniformance - PHD Specification Sheet

 2 Important Considerations in PHD System Sizing
2.8 PHD OPC Server

Parameter Specification Comments

HDA server OPCHDA_REGSLOPE -
aggregates
implemented OPCHDA_REGCONST
OPCHDA_REGDEV
OPCHDA_VARIANCE
OPCHDA_RANGE
OPCHDA_DURATIONGOOD
OPCHDA_DURATIONBAD
OPCHDA_PERCENTGOOD
OPCHDA_PERCENTBAD
OPCHDA_WORSTQUALITY
PHD_INTERPOLATIVE
PHD_AVERAGE
PHD_TIMEAVERAGE
PHD_DELTA
PHD_MINIMUMACTUALTIME
PHD_MINIMUM
PHD_MAXIMUMACTUALTIME
PHD_MAXIMUM
PHD_STDEV
PHD_REGSLOPE
PHD_REGCONST
PHD_REGDEV
PHD_FIRST

Uniformance - PHD Specification Sheet • 21

2 Important Considerations in PHD System Sizing
2.8 PHD OPC Server

Parameter Specification Comments

PHD_MINIMUMACTUALTIME_CO -
NF
PHD_MINIMUM_CONF
PHD_MAXIMUMACTUALTIME_C
ONF
PHD_ MAXIMUM_CONF
PHD_STDEV_CONF
PHD_REGSLOPE_CONF
PHD_REGCONST_CONF
PHD_REGDEV_CONF
PHD_FIRST_CONF
PHD_LAST_CONF
PHD_LAST
PHD_INTERPOLATIVE_CONF
PHD_AVERAGE_CONF
PHD_TIME_AVERAGE_CONF
PHD_DELTA_CONF

22 • Uniformance - PHD Specification Sheet

2.9 PHD Applications
Consolidated Event Journal (CEJ)

Parameter Specification Comments

Maximum data 5 years Data can be retained as many

retention years as required depending on
memory available space on the
hard disk drive.
Maximum records 16 Also refer to LCN for appropriate
inserted per second limitations

EJC RDI for Consolidated Event Journal (CEJ)

Parameter Specification Comments
Number of TPS 25 -
systems connected
to a single database

EPKS RDI for Consolidated Event Journal (CEJ)

Parameter Specification Comments

Number of EPKS 9 -
collectors configured

OPCAE RDI 1.10 for Consolidated Event Journal (CEJ)

Parameter Specification Comments

Number of OPCAE 9 -
collectors configured

Uniformance - PHD Specification Sheet • 23

PHD to Relational

Parameter Specification Comments

Number of tasks 16 -
scheduled

Number of tags per 16 -

task

Peer Tag Sync

Parameter Specification Comments

Number of tags 230,000 -

Experion Tag Sync

Parameter Specification Comments

Number of tags 50,000 -

Number of Experion 36 -
Servers

Honeywell International
Process Solutions
1860 W Rose Garden Ln
Phoenix, AZ 85027-2708