Uniformance®

PHD/Experion Link
Installation and Configuration Guide
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:
[email protected]
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 [email protected].

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. Introducing the PHD-Experion Integration...................................................... 13

1.1 About This Document ............................................................................. 13
1.2 Overview of PHD-Experion Integration Functions .................................. 13
1.3 Overview of PHD Experion Link ............................................................. 16
Tag capacity limitations ........................................................................ 16
Concurrent interface limitations ........................................................... 17
History Recovery .................................................................................. 18
PHD Experion Link data for Shadow system ....................................... 19
PHD Experion Link data for Shadow system using GatewayRDI........ 19
1.4 Overview of Redirection Manager .......................................................... 21
1.5 Overview of Matrikon OPC Redundancy Broker .................................... 21
1.6 Overview of Experion History ................................................................. 22
Categories of Experion tag history ....................................................... 22
Tag history assignments ...................................................................... 23
Maximum parameters assigned to Experion history ............................ 25
Tools for assigning TPS point parameters to Experion history............ 25
Tags not assigned to Experion history ................................................. 25
1.7 Overview of Tag Synchronization ........................................................... 26
Tag Synchronization Rules .................................................................. 27
1.8 Overview of PHD Point Server ............................................................... 28

2. Overview of Requirements for PHD-Experion Integration ............................ 31

2.1 Licensing and Packaging........................................................................ 31
2.2 Prerequisites for PHD-Experion Integration ........................................... 31
2.3 Checklist for PHD-Experion Integration .................................................. 33
2.4 How to Obtain Software Patches and Documentation Updates............. 43
To check HPS Online Support web site ............................................... 43
2.5 Overview of Security Requirements for PHD-Experion Integration........ 44
Domain requirements ........................................................................... 44
Windows account requirements ........................................................... 44
SQLServer user for Tag Synchronization ............................................ 46
 Recommendation if firewall exists between Shadow PHD Server and
Experion Server .................................................................................... 47

3. Prepare Domain Account, Experion Servers, and SQLServer User for PHD-
Experion Integration .......................................................................................... 49
3.1 Create Domain Account for RDI Server and Tag Synchronization ......... 49
On Domain Controller - Create domain account for RDI Server .......... 49
On Domain Controller – Create domain account for Tag
Synchronization (optional) .................................................................... 50
3.2 On Experion Servers - Add RDI Server Domain User to ‘Distributed COM
Users’ Local Group ................................................................................. 51
3.3 On Experion Servers – Modify Default DCOM Settings ......................... 52
3.4 On Experion Servers – Configure WMI Security .................................... 74
3.5 On Experion Servers – Configure Windows Firewall .............................. 75
3.6 Assign Windows User for Tag Synchronization Database Access ......... 76
Configure Tag Synchronization Database Access user ....................... 76

4. Prepare PHD Server for PHD-Experion Integration ........................................ 81

4.1 Add mngr Local Windows Account ......................................................... 81
4.2 On PHD Server – Configure Windows Firewall ...................................... 81
4.3 On PHD Server – Configure Logon Account for RDIServer Service ...... 87
4.4 On PHD Server – Change PHD Security Server .................................... 89
4.5 On PHD Server – Update HOSTS File ................................................... 89
4.6 On PHD Server – Update Services File (Optional) ................................. 92
4.7 On PHD Server – Increase the Maximum PHD Tags (PhdParams.Dat) 93

5. Install Software for PHD-Experion Integration ................................................ 95

5.1 On PHD Server - Install RDM and System Management Display for
Experion 300 (Optional) .......................................................................... 95
Additional RDM settings on non-Experion nodes ................................. 97
Alternative approach for Experion Link to connect to redundant
Experion servers................................................................................... 98
5.2 On PHD Server - Install PHD Point Server (Optional) ............................ 99
5.3 On PHD Server - Install Tag Synchronization (Optional) ...................... 100
Tag Synchronization upgrades/patches ............................................. 103

6. Configure PHD-Experion Integration ............................................................. 105

 6.1 On PHD Server - Configure System Management Display (Optional) . 105
6.2 On PHD Server - Configure RDM (Optional) ........................................ 105
6.3 In PHD Configuration Tool – Configure PHD Experion Link ................ 107
6.4 On PHD Server - Create Registry and File Entries for PHD Experion Link111
Add parameter to registry and change default value ......................... 116
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules .... 117
What Tag Sync rules are needed? .................................................... 117
To view and evaluate the default rule ................................................ 117
To view and evaluate the default parent tag ...................................... 118
To configure a new rule ..................................................................... 119
Honeywell-supplied default rule text for Experion.............................. 120
Honeywell-supplied default Parent Tag for Experion......................... 122
Rule examples for Experion ............................................................... 123
Tag name considerations................................................................... 128
Tips for regular expressions............................................................... 128
Tag Sync variables ............................................................................ 129
To view synchronized tags in staging table before sending tag
definitions to PHD .............................................................................. 131
6.6 Configure PHD Point Server................................................................. 133
On Experion Servers - Configure Experion to communicate with PHD
Point Server ....................................................................................... 133
On PHD Server - Configure registry settings, as needed, for PHD Point
Server................................................................................................. 134

7. Startup PHD-Experion Integration Components .......................................... 137

7.1 On PHD Server - Start and Monitor PHD Experion Link ...................... 137
7.2 Start and Monitor Tag Synchronization ................................................ 137
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag
Synchronization Staging Table (Optional) ............................................ 142
Overview ............................................................................................ 142
Fields.................................................................................................. 145
Statuses and actions .......................................................................... 146
To take action..................................................................................... 148
To view Tag Sync log ......................................................................... 149
7.4 Tasks to Perform After Initial Tag Synchronization .............................. 150
Complete PHD engineering unit configuration................................... 150
Enable/Disable continuous Automatic Tag Synchronization (Optional)153
Set DEBUG registry parameter back to 1 .......................................... 153
Set Tag Synchronization service to Automatic startup ...................... 154
 7.5 On PHD Server – Start PHD Point Server Service ............................... 154
7.6 On Experion Server – View PHD Point Server Status .......................... 154
7.7 On Experion Server – View PHD Point Server Trend Data .................. 156

8. Configure PHD Tags on PHD Experion Link ................................................. 159

8.1 General PHD Tag Configuration Guidelines ......................................... 159
8.2 Manually Configure a New PHD Tag .................................................... 159
Before you begin ................................................................................ 159
To manually configure a new PHD tag ............................................... 159
8.3 Deleting an Experion point or removing it from Experion history .......... 160
8.4 Disable Tag Synchronization for a PHD Tag ........................................ 161
8.5 Update or Migrate Existing PHD Tags .................................................. 162
8.6 Tag Field Usage for PHD Tags on PHD Experion Link ........................ 163
Tag Name ........................................................................................... 163
Active .................................................................................................. 163
Parent Tag Name ............................................................................... 163
Tag Units ............................................................................................ 164
Enable Collection................................................................................ 164
Data Store .......................................................................................... 164
Digital Enumeration ............................................................................ 164
Automatic Tag Synchronization .......................................................... 164
Source Tag Specification Source Tag Index ...................................... 165
Source System Type .......................................................................... 165
Source Tag Type ................................................................................ 165
Source Tag Attribute........................................................................... 166
Source Tag Units ................................................................................ 166
Collector Name ................................................................................... 166
Scan Frequency ................................................................................. 166
Digital Enumeration List Name ........................................................... 168
PHD Link Name .................................................................................. 168
Extended Source Tag Name .............................................................. 168
Scale High Extreme Scale Low Extreme ........................................... 168
Quantum ............................................................................................. 169
Synchronization Rule Name ............................................................... 169
Asset Name ........................................................................................ 169
Item Name .......................................................................................... 169
8.7 Collect and Access Enumeration Data ................................................. 169
Collect enumeration data.................................................................... 169
Enable PHD to return either strings or ordinals to clients .................. 170
Client access of enumeration strings or ordinals ............................... 170
8.8 Configure Manual Input Tags on PHD Experion Link ........................... 171
9. Monitor and Troubleshoot PHD-Experion Integration ................................. 173
9.1 Troubleshoot the PHD Experion Link ................................................... 173
View logs related to data collection.................................................... 173
Procedure to restart PHD Experion Link ............................................ 173
Procedure to view PHD/Link Status ................................................... 173
Interpret status and log messages ..................................................... 174
Common installation problems........................................................... 176
Symptom - Missing history data on PHD Server after history recovery177
Symptom - PHD failed to collect non-historizided point parameters from
Experion ............................................................................................. 177
9.2 Troubleshoot Redirection Manager (RDM) .......................................... 177
View logs related to RDM .................................................................. 177
View RDM auxiliary status display ..................................................... 178
9.3 Troubleshooting Tag Synchronization .................................................. 179
To view logs related to Tag Synchronization ..................................... 179
To view Tag Synchronization Status and Tuning display .................. 179
To locate PHD tags with range errors after executing Tag Sync....... 181
To handle tag configuration errors ..................................................... 183
To handle rule compilation errors ...................................................... 183
To force a resync ............................................................................... 183
View log related to PHD Point Server and Experion trends .............. 184
Interpret PHD Point Server Status display ......................................... 184
Symptom - Connection problems....................................................... 185
Symptom - Data missing from Experion trend ................................... 186
Recommendations - minimize PHD CPU usage and trend data callup
time .................................................................................................... 187
9.4 PHD Confidence and OPC Quality ....................................................... 188

10. Appendix A – PHD Server Registry Settings for PHD-Experion Integration189

10.1 PHD Experion Link Registry Settings ................................................... 189
10.2 Tag Synchronization Registry Settings ................................................ 190
10.3 PHD Point Server Registry Settings ..................................................... 192
Average and Snapshot retrieval settings ........................................... 194

11. Appendix B – Overview of RDISetup ............................................................. 197

11.1 RDISetup Data Flow ............................................................................. 197
 Figures
Figure 1 – PHD-Experion Integration - Function Diagram .............................................15
Figure 2 – PHD-Experion Integration - Example Topology ............................................17
Figure 3 – History Recovery by PHD Experion Link ......................................................19
Figure 4 – Example Shadow System Topology .............................................................20
Figure 5 – Diagram of PHD Experion Link with RDM ....................................................21
Figure 6 – Experion History Assignment ........................................................................24
Figure 7 –Tag Synchronization Process ........................................................................27
Figure 8 – PHD Point Server Components ....................................................................29
Figure 9 – Firewall between Shadow PHD Server and Experion ..................................48
Figure 10 – Configure WMI Security ..............................................................................74
Figure 11 – TCP/IP Name and "Target Host Name"......................................................91
Figure 12 – PHD Point Server Status Display .............................................................155
Figure 13 – Link Status Display – With RDM ...............................................................174
Figure 14 – Link Status Display – Non-Redundant Experion Server ...........................176
Figure 15 – Redirection Manager Auxiliary Status Display ..........................................178
Figure 16 – Tag Synchronization Status Display .........................................................180
Figure 17 – PHDMAN Confidence Report Indicates Problem Tags ............................182
Figure 18 – PHD Point Server Status Display .............................................................185
Figure 19 – Configuration of PHD Experion Links through RDISetup .........................197

Tables
Table 1 – Description of PHD-Experion Integration Functions ......................................14
Table 2 – PHD Links Configuration Form Entries ........................................................108
Table 3 – RDI Setup Indicators and Checkboxes ........................................................114
Table 4 – Fields on Tag Sync Acknowledgment form..................................................145
Table 5 – Statuses on Tag Sync Acknowledgment Form ............................................146
Table 6 – Buttons on Tag Sync Acknowledgment form ...............................................148
This page is intentionally left blank
 1. Introducing the PHD-Experion Integration
1.1 About This Document
This document describes the software installation and configuration procedures to
provide integration between the Honeywell Process History Database (PHD) historian
and the Honeywell Experion Server embedded historian.

1.2 Overview of PHD-Experion Integration Functions

PHD-Experion integration comprises the following key functions.
• PHD Experion Link
• Tag Synchronization
• PHD Point Server
The PHD Experion Link collects history from Experion for long term storage in PHD.
This data link function minimizes the impact of history collection on data providers, such
as controllers – it imposes no additional load when collecting history for PHD that is also
collected by Experion. The history collected by PHD matches the Experion history. The
PHD Experion Link supports history recovery from Experion after a communication
failure, and it has the ability to write values to Experion point parameters.

ATTENTION
The PHD Experion Link is not designed for real time delivery of history data
from Experion to PHD. History data is typically delivered to PHD one history
period after the data is placed in Experion database. If real time delivery of
history data from Experion to PHD is required, then you must use the PHD
OPC RDI.

The Tag Synchronization function eliminates duplicate engineering by automatically

building PHD tags that match the point parameters assigned to Experion history. Tag
Synchronization also reduces the effort required to maintain the synchronized systems,
especially when dealing with large tag databases. When a point parameter assigned to
Experion history is modified (for example, the range or engineering units is changed), the
corresponding PHD tags are updated as well.
If you remove a point parameter from Experion history assignment or delete the point
from the Experion system, PHD history collection is automatically disabled, but the tag
and history data are still available from PHD (for details see section 8.3, "Deleting an
Experion point or removing it from Experion history").

Uniformance - PHD/Experion Link Installation and Configuration Guide • 13

1 Introducing the PHD-Experion Integration
1.2 Overview of PHD-Experion Integration Functions

On a parameter-by-parameter basis, you can stop PHD from synchronizing tag

definitions or from collecting history values.
The PHD Point Server function allows an Experion Server to access PHD tag history
data for non-synchronized tags, so that you can include tags that are not historized in
Experion but are historized in PHD on Experion trend displays.
The following table briefly describes the PHD-Experion integration functions, which are
illustrated in Figure 1.

Table 1 – Description of PHD-Experion Integration Functions

Functions Components Purpose

1 Tag Uniformance Uniformance Tag Synchronization runs as a

Synchronization Tag Sync Windows service on the PHD Server and initiates
Tag Synchronization with the Experion Server.

Experion The Experion Tag Synchronization server running

Tag Sync on the Experion Server sends history tag definitions
to the PHD Server. Any subsequent
updates/modifications to the history tags are sent to
PHD as they occur.

2 Data collection PHD Experion The PHD Experion Link, running on the PHD
Link Server, requests history data from the Experion
OPC HDA Server for all of its assigned PHD tags
(those that have been synchronized and those that
have been manually created).

Experion OPC The Experion OPC HDA Server sends requested

HDA Server history values to the PHD Experion Link. In this role,
the Experion Server acts as the history cache to the
PHD Server.

Uniformance The PHD Experion Link runs under a Windows

RDI Server service named ‘Uniformance RDI Server'.

Redirection The PHD Experion Link uses the Redirection

Manager Manager (RDM) to direct it to the active Experion
(RDM) Server in a redundant pair.

3 PHD data on Experion PHD The Experion Server's 'PHD System Interface'
Experion trends System requests history data from PHD when an operator
Interface displays an Experion trend that references non-
synchronized PHD history tags (that is, tags that are
not assigned to Experion history).

14 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.2 Overview of PHD-Experion Integration Functions

Functions Components Purpose

PHD Point The Experion PKS PHD Point Server, running as a

Server Windows service on the PHD Server, sends the
PHD history data to the Experion Server as
requested.

Figure 1 – PHD-Experion Integration - Function Diagram

Uniformance - PHD/Experion Link Installation and Configuration Guide • 15

1 Introducing the PHD-Experion Integration
1.3 Overview of PHD Experion Link

1.3 Overview of PHD Experion Link

The PHD Experion Link is an OPC HDA client designed to interface and collect data
from the Experion Server history database for storage of the data to a Uniformance PHD
Server. The PHD Experion Link has the following standard functionality:
• Runs in Exception mode for reading single values.
• Optionally writes single values from PHD through the user-enabled Put-Download
mechanism.
• Performs history recovery.
The PHD Experion Link is managed by the RDI (real-time data interface) Server, which
runs on the PHD Server node as a Windows service.
You configure the PHD Experion Link through the PHD Configuration Tool and the
PHD RDI Configuration tool (RDISetup), and use the PHDMAN command line utility to
view the status and start/stop the PHD Experion Link.
The PHD Experion Link can use the Redirection Manager (RDM) to support failover
when connected to redundant Experion Servers.
The Uniformance Tag Sync service can be used to automatically create PHD tags from
Experion tags that have history assignment, and assign those PHD tags to a PHD
Experion Link for data collection. You can also create PHD tags manually.

Data throughput and constraints

PHD Experion Link delivers history data to PHD Server based on the number of point
parameters that can be assigned to Fast and Standard history in Experion Server.

REFERENCE
For details on the history assignment limits, refer to the Experion Server
Specification, which is available on the Honeywell Online Solutions web site.

Tag capacity limitations

The Experion Server's software licensing defines the Experion tag capacity limitations.
On the PHD Server, the user specifies the maximum number of PHD tags. An Experion
tag represents multiple parameters. A PHD tag represents a single parameter, such as
PV, SP, or OP.

16 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.3 Overview of PHD Experion Link

Concurrent interface limitations

You define only a single PHD Experion Link between a PHD Server and an Experion
Server. An Experion Server connects to only one PHD Server. Honeywell does not
support multiple PHD Experion Links to a single Experion Server or redundant pair.
In R320, a 64 bit PHD server supports a maximum of 36 PHD Experion Links. A PHD
Server running on versions R210.1.3 to R310 supports maximum of seven (7) PHD
Experion Links. Prior PHD releases support maximum of three (3) PHD Experion Links.

Figure 2 – PHD-Experion Integration - Example Topology

Uniformance - PHD/Experion Link Installation and Configuration Guide • 17

1 Introducing the PHD-Experion Integration
1.3 Overview of PHD Experion Link

ATTENTION
If there are more than three Experion Servers, contact Honeywell Services for
hardware sizing assistance.

Minimum Experion Server software release: R301.1.002.

PHD R210 releases earlier than R210.1.3 support up to three PHD Experion
Links.

If there is a requirement for more than seven PHD Experion links, Honeywell
recommends that you use multiple PHD Servers and define the PHD Experion Links
across these nodes.

History Recovery
History Recovery is the retrieval of data from the Experion Server by the PHD Experion
Link for the period of time during which the Link was unable to collect data directly
from the Experion Server. The recovered data eliminates the data gaps that result from
non-collection of data. For history recovery, the Experion Server returns data from its
fastest history collection group for each tag. For example, if an Experion tag is assigned
to one-minute and one-hour Experion history collection, then the Experion Server returns
one-minute data to the Link.
The PHD Experion Link parameter MAX_HISTRECMN specifies the oldest time the
Link should use for history recovery.
The Link uses the OPC HDA interface ‘ReadRaw’ for History Recovery. The ReadRaw
call accepts one timestamp for all the items requested. Since the Link can specify only
one timestamp to the ReadRaw call, it uses the oldest time across all the tags.
As illustrated in the following figure, the Link finds the oldest of the most recent value
for each tag, and if that value is earlier than MAX_HISTRECMN minutes ago, then it
starts history recovery from MAX_HISTRECMN minutes ago.

18 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.3 Overview of PHD Experion Link

Figure 3 – History Recovery by PHD Experion Link

PHD Experion Link data for Shadow system

An “upper” PHD Server can obtain data from a “lower” PHD Server. This is called
“shadowing.” The interface to the shadow is done using RDC (Robust Data Collection)
mechanism. To configure a link in RDC mode, refer to the “Robust Data Collection
Users Guide” (pim350).
Alternatively, the previous mechanism was to utilize the Gateway RDI and RemotePeer
server. This option can still be used and is discussed below.

PHD Experion Link data for Shadow system using GatewayRDI

An "upper" PHD Server can obtain data from a "lower" PHD Server. This is called
"shadowing." The interface to the shadow is the Gateway/Remote Peer RDI.
To shadow the PHD Experion Link, you configure a Gateway RDI on the "upper" node
and install the RemotePeer Server as a Windows service on the "lower" node. The
Gateway RDI connects to the RemotePeer Server on a specified port. The Gateway RDI
requests data from the Remote Peer Server, which answers that request by retrieving data
from its PHD Server.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 19

1 Introducing the PHD-Experion Integration
1.4 Overview of Redirection Manager

The Gateway RDI runs in either SHADOW or PEER mode. In SHADOW mode (as
illustrated in the following figure), both PHD Servers share the same database. In PEER
mode, the PHD Servers have separate databases.

REFERENCE
For additional PHD topologies, refer to the Uniformance Network Security
and Planning Guide (am0651).

Figure 4 – Example Shadow System Topology

Tag Synchronization for Shadow system

When implemented in a Shadow system, Tag Synchronization occurs to both the PHD
Shadow Server and the PHD Collector Server. The approach Honeywell recommends is
to send configuration updates to the PHD Shadow Server, which should be configured to
inform all of the PHD Collector Servers of the updates.
After updating the Uniformance database, the Tag Synchronization service informs the
Shadow PHD Server (specified in the Primary PHD Server property of the UDB Server).
Note: This is the same mechanism used by the PHD Configuration Tool for user updates.

20 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.4 Overview of Redirection Manager

The PHD Shadow Server informs all of the PHD Collector Servers listed in its PHD
Server Host List tab of the PHD Server properties page.

1.4 Overview of Redirection Manager

Redirection Manager (RDM) is required on the PHD Server if the PHD Experion Link is
to connect to a redundant pair of Experion Servers.
In such a case, the PHD Experion Link is configured to connect to Redirection Manager
instead of the Experion OPC HDA server.
RDM forwards requests to the active Experion Server of a configured redundant pair.
Redirection occurs whenever a failure is detected in the active Experion Server.
RDM operates in passive redundancy mode when the target OPC servers are Experion
Servers. This means that the redundant server node platform initiates the failover, not the
RDM.
RDM blocks all OPC calls until after the failover completes or after a user-configured
timeout.

Figure 5 – Diagram of PHD Experion Link with RDM

1.5 Overview of Matrikon OPC Redundancy Broker

OPC Redundancy Broker (ORB) is required on the PHD server if PHD Experion Link
must be connected to a redundant pair of Experion Servers. If PHD Experion Link must
be connected, it must be configured to connect to the ORB instead of the Experion OPC

Uniformance - PHD/Experion Link Installation and Configuration Guide • 21

1 Introducing the PHD-Experion Integration
1.6 Overview of Experion History

HDA server. The ORB forwards requests to the active Experion Server of a configured
redundant pair.
For more information on installing and configuring the Matrikon OPC Redundancy
Broker, refer to Matrikon documentation.

1.6 Overview of Experion History

Categories of Experion tag history
The Experion Server collects tag data from controllers and stores different categories of
tag history in its local history database files. Experion Servers (Experion R400 and later
versions) can be configured to store four different categories of tag history in its local
history database, as follows:

Category History Database

Fast history • 1-second to 30-second snapshots (one user-configurable interval

per Experion Server)
• 1-second to 30-second snapshots (one user-configurable interval
per tag in the Experion Server and is supported for Experion R400
and later versions)

Standard 1-minute snapshots

history 6-minute, 1-hour, 8-hour, and 24-hour averages

Extended 1-hour, 8-hour, and 24-hour snapshots

Exception Exception history collects parameter values at a specified rate in the

history Experion Server and is supported only for Experion R400 and later
versions. These values are stored in the Experion Server only if there
is any change in the value or confidence from the previously stored
value.

NOTE: Exception history only supports string values.

For more information on exception history, refer to Experion documentation.

22 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.6 Overview of Experion History

Tag history assignments

The PHD Experion Link and Tag Synchronization depend on Experion Server history
assignments.
Point.parameters assigned to Experion history gets added to PHD through tag
synchronization.
By default, the Experion Server returns tag data to PHD from its fastest history collection
group. For example, if an Experion tag is assigned to Standard and Extended history,
then the Experion Server returns one-minute data from Standard history to PHD.
However, it is possible to configure a different history assignment than the default to
individual parameters. For example, if the default collection is one-minute data from
Standard history to PHD, you can configure the PV of a point to collect 5-second data
from Fast history to PHD.
As shown in the following figure, you can assign an individual Experion tag parameter to
any, all, or none of the Experion history categories. The following figure shows the
Experion history assignment for a control module named CM_AUX.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 23

1 Introducing the PHD-Experion Integration
1.6 Overview of Experion History

Figure 6 – Experion History Assignment

In Experion 430 and later releases, it is possible to configure PHD history collection for
individual point parameters either at a different (slower) rate, or to exclude the point
parameter from PHD collection.

Refer to the section, PHD Collection Rule in Experion PKS Hardware and Point Build
Reference guide for more details.

24 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.7 Overview of Tag Synchronization

Maximum parameters assigned to Experion history

The Experion Server has a default maximum number of parameters for each category of
history.

REFERENCE
For details on the Experion Server history sizing, refer to the Experion Server
Specification, which is available on the Honeywell Online Solutions web site.

Tools for assigning TPS point parameters to Experion history

For LCN-connected Experion systems, you can use the following tools to assign TPS
point parameters to Experion history:
• TPS History Configuration Import tool
• ptbuild command line utility

REFERENCE
For details on how to use the above tools, refer to the following documents:

• Experion R301 book set: Experion Server and Client Configuration

Guide, section “Integrating PHD, Assigning TPS point parameters to
history".
• Experion R400 book set: Integrated Experion TPS Nodes User's Guide,
section "Importing TPS History Configuration".

Tags not assigned to Experion history

If PHD requests a parameter that is not assigned to Experion history and Experion's
"Allow PHD to access non-historized point parameters" server-wide setting is
enabled, then the Experion Server returns current cached data established through
standard Experion data access mechanisms.
PHD Experion Tag Synchronization does not examine PointName.Parameters that you
did not assign to Experion history.
Any numerical data that is to be collected/synchronized in PHD should be assigned to
Experion history.

ATTENTION
Experion 400 allows you to collect string tags through ESVT.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 25

1 Introducing the PHD-Experion Integration
1.7 Overview of Tag Synchronization

1.7 Overview of Tag Synchronization

Uniformance Tag Synchronization runs as a Windows service on the PHD Server to
automatically create and (if needed) continuously synchronize PHD tag definitions to the
Experion history point configuration. Tag Synchronization is made up of components
running on both the primary and backup Experion Servers and the PHD Server. These
components perform as follows:
1. When started, the Uniformance Tag Sync service uses RPC (Remote Procedure
Calls) to ask the Experion Server for the definitions of tags in its history assignment.
The Experion Server sends (using RPC) the full tag definition, server name, point
name, parameter description, and timestamp of when the tag definition was sent to
Tag Sync.
2. From the information received, Tag Sync creates PHD tag definitions (based on
user-configured rules) and writes the definitions to a "staging table" in the PHD
SQLServer database.
3. After the user acknowledges the definitions in the "staging table", Tag Sync updates
the existing tag definitions in the PHD SQLServer database or creates new tags, and
automatically updates the PHD Server with a copy of the tag definitions. The user
can configure Tag Sync to automatically acknowledge the tag definitions in the
staging table. The default configuration requires user acknowledgement.
4. Uniformance Tag Sync requests updated and new definitions from the Experion
Server every 60 seconds.

26 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.8 Overview of PHD Point Server

Figure 7 –Tag Synchronization Process

Tag Synchronization Rules

Tag Sync examines each returned Experion history PointName.Parameter against the
optional regular expression of each Tag Sync Rule (user-configured rules and a default
rule), and tries to find a match. When it finds a match, it creates a PHD tag definition
using that Rule's text.
Note: Tag sync only examines PointName.Parameters that you assign to Experion
history. If a single Experion tag has multiple parameters assigned to history (for example,
PV, SP, and OP), then Tag Sync will correspondingly create multiple PHD tags. Atleast
one out of the three parameters (PV, SP, or OP) must be unique.
The default installation of Tag Sync provides one default rule and a default PHD parent
tag. This may be satisfactory for integration of an Experion system into new PHD
systems that do not have existing PHD tags. The user may create new rules and parent
tags or modify the Honeywell-supplied default.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 27

1 Introducing the PHD-Experion Integration
1.8 Overview of PHD Point Server

1.8 Overview of PHD Point Server

PHD Point Server (running as a Windows service named Experion PKS PHD Point
Server) allows you to view PHD data in Experion Trends. After you add PHD tags to
Experion trends, the history data requests for points that exist only on the PHD system
(for example, lab data tags) are made to the PHD Point Server. By default, the PHD Point
Server returns PHD data for non-synchronized tags; that is, tags that are not historized on
Experion. Return of synchronized tags can be enabled through a registry setting (see
Appendix A – PHD Server Registry Settings for PHD-Experion Integration).
The PHD Point Server responds to PHD history data requests from the Experion trend
subsystem by way of GDA (General Database Access).
• PHD Point Server, running on the PHD Server, can communicate with a single PHD
Server and a single Experion Server (or a redundant pair).
• Only one Experion Server (or a redundant pair) can connect and retrieve data from a
PHD Point Server. Additional Experion Servers may access the same trend data
through configuration of Experion DSA (Distributed System Architecture).

28 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 1 Introducing the PHD-Experion Integration
1.8 Overview of PHD Point Server

Figure 8 – PHD Point Server Components

Uniformance - PHD/Experion Link Installation and Configuration Guide • 29

This page is intentionally left blank

Uniformance - PHD/Experion Link Installation and Configuration Guide • 30

 2. Overview of Requirements for PHD-Experion
Integration
2.1 Licensing and Packaging
No additional licenses or software are required for Experion-PHD integration. Experion-
PHD Integration is enabled in all PHD and Experion systems.
Experion Redirection Manager (RDM) and the Experion PHD Point Server are packaged
on the Experion media, but need to be installed on the PHD Server.
No additional OPC connection license is required on the Experion Server for the
Experion-PHD integration.

2.2 Prerequisites for PHD-Experion Integration

Verify that the following prerequisites have been completed before continuing.

Prerequisite Reference 

Compatible version of Experion Server is installed, Experion Software Installation

(including appropriate operating system service User's Guide
packs), and system is operative.

Any applicable patches have been applied. Patch release lettersSee NOTE

Complete the point history assignments on the Experion Server and Client
Experion Server for points that are to be synchronized Configuration Guide
or collected in PHD.

Note: For LCN-connected Experion Servers, there are

procedures for assigning TPS points to Experion
history (refer to section "Importing HM history
assignment into Experion" or "Creating an LCN-
connected server point build file").

The appropriate release of Uniformance Database Uniformance Security and

and PHD Server is installed, configured, and running. Network Planning Guide
(am0651)
Any applicable patches have been applied.
Uniformance Installation Guide
Attention: RDM is an Experion component and (in6001)
therefore falls under Experion restrictions. The PHD-
See NOTE
compliant server that will run RDM must run a Patch release letters
Windows operating system that is Experion-compliant.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 31

2 Overview of Requirements for PHD-Experion Integration
2.2 Prerequisites for PHD-Experion Integration

Prerequisite Reference 

The PHD Configuration Tool is installed and operable Uniformance Installation Guide
on the computer you plan to use for entering/viewing (in6001)
configuration data.

Any applicable patches have been applied Patch release lettersSee NOTE

A DVD drive is available to install the optional RDM

and PHD Point Server software from the Experion
Applications DVD.

The system-wide impact of the Honeywell system Experion Redirection Manager

management infrastructure required by RDM is known. User's Guide in the Experion book
set.

Experion System Management

Configuration Guide in the
Experion book set.

ATTENTION
Read the latest Uniformance SCN for your release and any associated patch release
letters – look for notifications related to software components that are required for
PHD Experion integration.

See section 2.4 of this guide, "How to Obtain Software Patches and Documentation
Updates".

32 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

PREPARATION

PREPARATION - General

Obtain the software media: The Experion

Applications DVD is
• Uniformance DVD required only if
• Experion PKS Applications DVD installing RDM or PHD
Point Server.

Ensure the prerequisites have been This guide – section

met. 2.2, Prerequisites for
PHD-Experion
Integration

Check the Honeywell online support This guide – section

web site to obtain PHD software 2.4, How to Obtain
patches and the latest version of this Software Patches and
document. Documentation
Updates

Review the security requirements. This guide – section

2.5, Overview of
Security Requirements
for PHD-Experion
Integration.

PREPARATION - On the Domain Controller

Create domain account(s) to be used This guide – section You may use the same
by these services: 3.1, Create Domain account for Tag Sync
Account for RDI Server as RDI Server, or
• Uniformance RDI Server service and Tag Sync create separate
• (Optional) Uniformance Tag Sync accounts.
service

PREPARATION - On the Experion Servers nodes

Uniformance - PHD/Experion Link Installation and Configuration Guide • 33

2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

Add the domain account to be used by This guide – section Perform this task on
the Uniformance RDI Server service to 3.2, On Experion both the Primary and
the Experion Server's local ‘Distributed Servers - Add RDI Secondary nodes.
COM Users’ group. Server Domain User to
‘Distributed COM Users’
Local Group

Complete the DCOM configuration. This guide – section Perform this task on
3.3, On Experion both the Primary and
Servers – Modify Default Secondary Experion
DCOM Settings Server nodes

Configure WMI Security This guide – section 3.4 Perform this task on
On Experion Servers – both the Primary and
Configure WMI Security Secondary Experion
Server nodes

Configure Windows Firewall. This guide – section 3.5 Perform this task on
On Experion Servers – both the Primary and
Configure Windows Secondary Experion
Firewall Server nodes

PREPARATION – Database user for Tag Synchronization (Optional)

(Optional) Using the Uniformance This guide – section Required if the PHD
System Console (USC), configure a 3.6, Assign Windows Server is to have Tag
SQLServer user for the Tag User for Tag Synchronization from
Synchronization service to use to log on Synchronization the Experion Server's
to SQLServer: history point database.

PREPARATION - On the PHD Collector Server

Add mngr as a local user on the PHD This guide – section The user must be
Server node. 4.1, Add mngr Local configured on the PHD
Windows Account Server node exactly as
it is defined on the
Experion PKS OPC
Server node.

Configure Windows Firewall. This guide – section

4.2, On PHD Server –
Configure Windows
Firewall

34 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

Complete the DCOM configuration. This guide – section Use a Honeywell or

0, On PHD Server - third-party OPC client
Verify that the Experion Server is Modify DCOM Settings to test the
reachable by DCOM communication communication.
from the PHD Server.

Configure the existing Uniformance RDI This guide – section

Server to use a domain account. 4.3, On PHD Server –
Configure Logon
Assign the domain account to the Account for RDIServer
required local groups and policies. Service

Update the HOSTS file to include the This guide – section Use "ping".
Experion servers. 4.4, On PHD Server –
Change PHD Security
Ensure the primary and secondary Server
Experion Servers are reachable by
TCP/IP communication from the PHD
Server.

Update the Services file to include the This guide – section

port number used by the Experion Tag 4.6, On PHD Server –
Synchronization component. Update Services File
(Optional)

(Optional) Modify the maximum number This guide – section <install directory>
of PHD tags specified for the PHD 4.7, On PHD Server – PHDServer
Server in its PhdParams.Dat file, if you Increase the Maximum \NtSite\PhdParams.
anticipate the current maximum to be PHD Tags Dat
exceeded by the automatic Tag Sync (PhdParams.Dat)
service or manual tag creation.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 35

2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

INSTALLATION
INSTALLATION – On the PHD Collector Server (Optional)
(Optional) Install Redirection Manager This guide – section The RDM is required if
(RDM) on the PHD Server that is to run 5.1, On PHD Server - the PHD Experion Link
the PHD Experion Link. Install RDM and System is to have failover
Management Display for support for redundant
(Optional) Install System Management Experion 300 (Optional) Experion Servers.
Display on the PHD Server that is to
run the PHD Experion Link. The System
Management Display is
Install applicable patches, if any. optional, but is useful
for troubleshooting the
RDM.

Use Experion
Applications DVD.

For patches, see HPS

online support web site.

36 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

(Optional) Install PHD Point Server on This guide, section 0, Required if the PHD
the PHD Server. Alternative approach Server is to support
for Experion Link to data retrieval of non-
Install applicable patches, if any. connect to redundant synchronized PHD tags
Experion servers by Experion Server
trends.
If you do not
want to install Use Experion
RDM, you can Applications DVD.
use an alternate
approach to
connect the
link to the
redundant
Experion
servers.
1. In
PCT
update
the
Experi
on
Link
definit
ion.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 37

2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

For patches, see HPS

online support web site.

(Optional) Install Tag Synchronization This guide, section Required if the PHD
on the PHD Server that is to run the 5.3, On PHD Server - Server is to have
PHD Experion Link. Install Tag automatic PHD tag
Synchronization creation from the
Install applicable patches, if any. (Optional) Experion Server's
history point database.

Use Uniformance CD.

For patches, see HPS

online support web site.

CONFIGURATION
CONFIGURATION – RDM and System Management Display (Optional)
(Optional) On the PHD Server node, This guide – section Required only if the
configure the System Management 6.1, On PHD Server - System
Display. Configure System Management Display
Management Display was installed on the
(Optional) PHD Server node.

(Optional) On the PHD Server node, This guide – section Required only if the
use the Experion Configuration Utility or 6.2, On PHD Server - RDM was installed
the System Management Display to Configure RDM on the PHD Server
configure the RDM, if it was installed. (Optional) node.

CONFIGURATION – PHD Experion Link

Use the PHD Configuration Tool to This guide – section Start>Programs>
complete the Interfaces 9RDI’s and 6.3, In PHD Uniformance> PHD
Links) Configuration form. Configuration Tool – Configuration
Configure PHD Tool>PHD
Experion Link Configuration
Tool>Interfaces>
Interfaces (RDI’s and
Links) form.

38 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

On the PHD Server node, create the This guide – section Start>Programs>
registry and file entries for the PHD 6.4, On PHD Server - Uniformance>PHD
Experion Link. Create Registry and Server> PHD RDI
File Entries for PHD Configuration
Experion Link
Use Regedit as
needed.

CONFIGURATION – Tag Synchronization (Optional)

Use the PHD Configuration Tool to This guide – section 0, Required if the PHD
evaluate the default Tag Server is to have
Synchronization rule and default parent In PHD Configuration automatic PHD tag
tag for suitability on your site. Configure Tool - Configure Tag creation from the
new rules/parents and/or modify the Synchronization Experion Server's
existing Honeywell-supplied defaults, history point
as needed. database.

Use the arrow key in the Tag This guide – section 0, This step is critical to
Synchronization Rule Configuration ensure that
form to move the Default Rule to the In PHD Configuration applicable rules get
bottom of the list of Configured Rules. Tool - Configure Tag processed before the
Synchronization default rule

CONFIGURATION – PHD Point Server (Optional)

The following tasks are required only if the PHD Point Server was installed on the PHD Server
node.

On the Experion Server, configure the This guide – section

system interface for the PHD Point 6.6, On Experion
Server. Servers - Configure
Experion to
communicate with PHD
Point Server

On PHD Server - Configure registry This guide – section

settings, as needed to enable or disable 6.6,
PHD Point Server functionality.
On PHD Server -
Configure registry
settings, as needed, for
PHD Point Server

Uniformance - PHD/Experion Link Installation and Configuration Guide • 39

2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

CONFIGURATION – Shadow Link using Gateway RDI/RemotePeer (Optional)

The following tasks are required only if a shadow ("upper") PHD Server is to acquire data from
a collector ("lower") PHD Server that is running a PHD Experion Link. The interface to the
shadow is the Gateway/Remote Peer RDI.

Use the PHD Configuration Tool to Remote Peer RDI Start>Programs>

configure the Gateway RDI to run on Installation Guide Uniformance> PHD
the "upper" PHD Server. (rdi1001) Configuration
Tool>PHD
Configuration
Tool>Interfaces>
Interfaces (RDI’s and
Links) form.

Note: The following

parameters are
required as remote
RDI parameters on
the Gateway RDI:
• XHIST (Exception
History Recovery)
• /L (to disable local
interface
checking)

On the "upper" PHD Server, run Remote Peer RDI

RDISetup and Interfaces.Dat to create Installation Guide
the registry and file entries for the (rdi1001)
Gateway RDI.

(Optional) On the "upper" PHD Required if using

Server, enter the hostname of the PHD Tag Synchronization.
Collector Server in the
NtSite\phdserver.hosts file.

On the "lower" PHD Server, install Remote Peer RDI

and configure the Remote Peer service. Installation Guide
(rdi1001)

40 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.3 Checklist for PHD-Experion Integration

Task Go to  Notes

STARTUP

STARTUP – Start PHD-Experion integration components

On the PHD Server that is to run the This guide – section PHDMAN STA INT
PHD Experion Link, use PHDMAN to 7.1, On PHD Server - <linkname>
start the Link and verify its status Start and Monitor PHD
PHDMAN SHO INT
Experion Link
<linkname>
(Optional) On the PHD Server, start This guide – section Required only if
the 'Uniformance Tag Synchronization' 7.2, Start and Monitor using Tag
Windows service. Tag Synchronization Synchronization.

(Optional) Use the PHD Configuration This guide – section Required only if Tag
Tool to view the synchronized PHD tag 7.3, In PHD Synchronization
definitions in the staging table. Configuration Tool – Rules were
Acknowledge Changes configured to require
in Tag Synchronization explicit user
Staging Table acknowledgement.
(Optional)
Start>Programs>
Uniformance> PHD
Configuration
Tool>PHD
Configuration
Tool>Applications >
Tag Synchronization
Acknowledgement
form.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 41

2 Overview of Requirements for PHD-Experion Integration
2.4 How to Obtain Software Patches and Documentation Updates

Task Go to  Notes

(Optional) Perform configuration This guide – section Required only if

required after initial Tag 7.4, Tasks to Perform using Tag
Synchronization: After Initial Tag Synchronization.
Synchronization
• Use the PHD Configuration Tool to
complete engineering unit
configuration, as needed.
• Use the PHD Configuration Tool to
enable or disable Automatic
Synchronization for each
synchronized PHD tag, as needed.
• On the PHD Server, configure
automatic startup of the
'Uniformance Tag Synchronization'
Windows service.

(Optional) On the PHD Server, start This guide – section Required only if PHD
the 'Experion PKS PHD Point Server' 7.5, On PHD Server – Point Server was
Windows service. Start PHD Point Server installed on the PHD
Service Server.

(Optional) On the Experion Server, This guide – section Required only if the
view the PHD Point Server status 7.6, On Experion PHD Point Server
display. Server – View PHD was installed on the
Point Server Status PHD Server.

(Optional) On the Experion Server, This guide – section Required only if the
create a PHD Point Server Experion 7.7, On Experion PHD Point Server
Trend and verify that the PHD Point Server – View PHD was installed on the
Server returns PHD data. Point Server Trend PHD Server.
Data

42 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.4 How to Obtain Software Patches and Documentation Updates

2.4 How to Obtain Software Patches and Documentation

Updates
Updates available on HPS Online Support web site
Before installing Uniformance software for PHD Experion integration, please perform
the following steps to check the Honeywell Process Solutions (HPS) Online Support web
site for patches to the software. At the same location, you should obtain the Uniformance
software change notice (SCN) document.
Uniformance documentation is updated when PARs (Product Anomaly Reports) are
received – the newest documents are posted to the Online Support web site. Honeywell
recommends that you download and review the latest documents.

To check HPS Online Support web site

Step Action
1 Go to www.honeywellprocess.com.
2 If you are a registered user, click Login to My Account.

Type your USER LOGIN and PASSWORD, and then click Login.

Note: If you are a new user, you can click Register Now to register for
access to the site.
3 Select Support > System Products.
4 Select Information Management from the System Products list.
5 Select Uniformance PHD from the Information Management list.
6 From the Uniformance PHD page, you can access any of the following:

Notifications: Priority Notifications and BeAware Advisories

Software Downloads: Software patches and hot fixes

Product documentation: Software Change Notices and other

documentation

TIP: To be notified by email of updates to the web page content, click the
content category of interest (Notifications, Software Downloads, or Product
Documentation), and then click SUBSCRIBE.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 43

2 Overview of Requirements for PHD-Experion Integration
2.5 Overview of Security Requirements for PHD-Experion Integration

2.5 Overview of Security Requirements for PHD-Experion

Integration
Domain requirements
Honeywell strongly recommends that the Experion Server and the PHD Server be
members of the same domain.

ATTENTION
If you plan to use Workgroups instead of Domains, please call Honeywell
TAC for assistance.

Windows account requirements

Uniformance RDI Server and Tag Synchronization run as Windows services but may be
run under the Network Service account to limit access to system resources. When
configured in this manner, the Uniformance System Console (USC) must be used to
configure the Windows user account the Tag Synchronization service should use to
access the SQLServer database and to connect to the PHD server. These entries are
stored encrypted in the registry for use by the service when connecting to the database
and to PHD.
You may use the same Windows accounts for both RDI Server and Tag Synchronization
services, or you may create separate accounts.
Honeywell strongly recommends that domain accounts be used.
If an account local to the PHD server is used, then a corresponding local account (with
matching name and password) must exist on the Experion Servers, so authentication can
take place. You may be able to implement authentication using equivalent local accounts,
but be aware that experience has proven this not to work 100% of the time with Windows
Server 2008 or 2012.

RDI Server account requirements

For data collection by the PHD Experion Link, the Experion Server node must be able to
authenticate the account used by the Uniformance RDI Server service.
The RDI Server is configured to run as the Network Service account by default.
However DCOM communications requires that the server be run as the specific user
account in order for authentication to work properly. You must change the RDI Server's
logon account and grant the account the required privileges.

44 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.5 Overview of Security Requirements for PHD-Experion Integration

REFERENCE - INTERNAL
For information on how to change the RDI server’s logon account, refer to
the section, On PHD Server – Change PHD Security Server.

The account used by RDI Server requires the following local privileges on the PHD
Server node:
• Local Groups – member of local Product Administrators group
• Local Policy – assigned local user right to "log on as a service" and to "act as part of
the operating system."
Asynchronous callbacks are made from the Experion OPC Server to the Uniformance
RDI Server. This requires that the PHD Server node be able to authenticate the user that
the Experion PKS OPC Server runs under. By default, this is the mngr account.
If using Redirection Manager (RDM), callback security in the form of account
authentication will need to be considered as well. (Refer to the patch release letters for
information related to RDM issues.)

Tag Synchronization account requirements

RPC (Remote Procedure Call) connection level authentication is used between the Tag
Sync client running on the PHD Server and the Tag Sync server running on the Experion
Server (only when the Tag Sync client establishes a relationship with the Tag Sync
server).
If run as the Network Service Account, Uniformance Tag Synchronization on the PHD
Server requires the following local privileges on the PHD Server node:
• Local Policy – assigned local user right to "log on as a service"
The service must then have a database and PHD user configured through the
Uniformance System Console (USC). These users must valid window users that can be
authenticated to the system using Windows Authentication. The database user must be
assigned to the “Local Engineers” role.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 45

2 Overview of Requirements for PHD-Experion Integration
2.5 Overview of Security Requirements for PHD-Experion Integration

SQLServer user for Tag Synchronization

Uniformance Tag Synchronization, running as a Windows service, must access
SQLServer to make changes to PHD tag definitions. The following SQLServer
configuration is required for Uniformance Tag Synchronization to be able to access the
SQLServer database:
• The Windows user name that the Uniformance Tag Sync uses to connect to the
database must be recognized by SQLServer as a valid Windows user.
• The SQLServer user used by the Uniformance Tag Sync service to connect to
SQLServer must be assigned to the “Local Engineers” role in order to have
read/write privilege to the SQLServer Tag Synchronization tables.

How Tag Synchronization logs on to SQLServer

When Uniformance Tag Synchronization logs on to SQLServer, it does so by first
creating a local logon token for the specified Windows Database User. This user must be
assigned to the “Local Engineers” role to provide the necessary Read/Write access to the
Tag Synchronization database tables. Once the Windows user has been successfully, that
thread then connects to the SQLServer database and appears to the database as the
specified user with that user’s rights. It is therefore important that the database user
specified for Tag Synchronization to user has the necessary rights in order to read and
write to the SQLServer database.

DCOM configuration and Windows Firewall

PHD Link
DCOM security configuration must be configured to open the communications between
the PHD Server node and the primary and backup Experion Server nodes. Because the
PHD Experion Link runs under a Windows service named ‘Uniformance RDI Server,' the
OPC client (in this case, the account used by the Uniformance RDI Server) must be
granted access in DCOM configuration on the Experion PKS OPC Server machine to
Access and Launch the Experion PKS OPC Server, either explicitly through its Windows
logon user name or through a Windows group containing it.
To re-enable OPC communication, it is necessary to do the following:
• Configure the Windows Firewall appropriately or disable the Windows Firewall (not
recommended unless the machine is already behind a corporate firewall).
• Reconfigure DCOM.

46 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 2 Overview of Requirements for PHD-Experion Integration
2.5 Overview of Security Requirements for PHD-Experion Integration

REFERENCE
For full details on the actions required to re-enable OPC communication on
Windows 2008 and Windows 2012, download the following white paper from
http://opcfoundation.org/.

Tag Synchronization
The Windows Firewall settings on the Experion Servers must be modified to allow the
optional Uniformance Tag Sync service to be able to connect to the Experion Server’s
Tag Synchronization component (htsserver.exe).

Recommendation if firewall exists between Shadow PHD Server and Experion

Server
The PHD Experion Link uses OPC to obtain data from Experion Servers; consequently,
it is not firewall friendly. In situations where a firewall is required between a PHD
Shadow Server and the Experion Servers, Honeywell recommends that a PHD Server be
installed on the Experion-side of the firewall to run the PHD Experion Links.
The following figure shows the recommended approach when a firewall exists between
the PHD Shadow Server and Experion Servers.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 47

2 Overview of Requirements for PHD-Experion Integration
2.5 Overview of Security Requirements for PHD-Experion Integration

Figure 9 – Firewall between Shadow PHD Server and Experion

48 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3. Prepare Domain Account, Experion Servers, and
SQLServer User for PHD-Experion Integration
3.1 Create Domain Account for RDI Server and Tag
Synchronization
Note: Typically the services will be run as the “Network Service” account. In these
cases, the domain account is necessary for the Tag Synchronization service to be able to
successfully connect to the SQLServer database.

On Domain Controller - Create domain account for RDI Server

If the Experion Server is in a domain, but the PHD Server’s RDI Server service is not yet
configured to run under a domain account, then perform the following steps to create a
domain account to be used for that purpose.

Step Action
1 On the Domain Controller, create a user account (for example
CGY\PHDExpLink).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 49

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.2 On Experion Servers - Add RDI Server Domain User to ‘Distributed COM Users’ Local Group

Step Action
2 Select the ‘Password Never Expires’ and the User ‘Cannot Change
Password’ options.

Clear the ‘User Must Change Password At Next Logon’ option.

On Domain Controller – Create domain account for Tag Synchronization (optional)

If you want to use a separate domain account for the Uniformance Tag Sync service,
repeat the previous steps to create a separate domain account – for example,
CGY\RunTS.
Ensure this user is assigned to the “Local Engineers” role in order for it to have the
necessary permissions to read and write to the SQLServer database tables.

50 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.2 On Experion Servers - Add RDI Server Domain User to ‘Distributed COM Users’ Local Group

3.2 On Experion Servers - Add RDI Server Domain User

to ‘Distributed COM Users’ Local Group
On the primary and backup Experion Servers, perform the following steps to add the user
that is used by the Uniformance RDI Server to the local Windows group named
'Distributed COM Users.' The domain user must be the same domain user that the
Uniformance RDI Server will run as on the PHD Server machine.

Step Action
1 On the Experion Server, right-click My Computer and choose Manage.
2 Expand Local Users and Groups, open Groups, and then open Distributed
COM Users.
3 Add the user (for example CGY\PHDExpLink) to the group and click OK.

TIP: The 'Distributed COM Users' local group will not exist on some Windows
operating systems that do not have the required service pack installed.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 51

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

ATTENTION
Perform this configuration on both the Primary and Secondary Experion
Server nodes.

3.3 On Experion Servers – Modify Default DCOM Settings

On the primary and backup Experion Servers, perform the following steps to configure
the default DCOM settings. Note: Do not attempt to modify DCOM configuration
information without a thorough understanding of the impact it may have on your system.

Step Action
1 Click Start, click Run, type DCOMCNFG, and click OK.

The Component Services window appears.

2 Expand Component Services > Computers.
3 Right-click My Computer, and choose Properties.
4 Click the Default Properties tab.

52 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
5 Set the Default Properties as shown in the following screen example.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 53

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
6 Click the Default Protocols tab.
7 Ensure that Connection-oriented TCP I/P is listed as the first protocol.

8 Click OK to close the window.

54 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

Edit the properties of the ‘OpcEnum’ DCOM Object:

9 In the Component Services window, expand My Computer.

Expand DCOM Config, right-click OpcEnum, and choose Properties.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 55

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
10 In the General tab, edit the properties as shown in the following screen
example.

Note: This screen will appear slightly different in cases where

OpcEnum was not installed as a service.

56 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
11 Click the Location tab. Edit the properties as shown in the following screen
example:

Uniformance - PHD/Experion Link Installation and Configuration Guide • 57

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
12 Click the Security tab.

Under ‘Launch and Activation Permissions’, select Customize and click Edit.

58 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘OpcEnum’ Properties, continued

13 Ensure the Everyone group has Remote Launch and Remote Activation
enabled, as shown in the following example.

14 Click OK.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 59

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘OpcEnum’ Properties, continued

15 On the Security tab, under Access Permissions, select Customize and click
Edit.

60 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘OpcEnum’ Properties, continued

16 Ensure the Everyone group has Remote Access enabled, as shown in the
following screen example.

17 Click OK.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 61

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘OpcEnum’ Properties, continued

18 Click the Endpoints tab and set the properties as shown in the following
screen example:

62 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘OpcEnum’ Properties, continued

19 Click the Identify tab and set the properties as shown in the following screen
example.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 63

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

ATTENTION:
The ‘system account’ radio button will be grayed-out if OpcEnum was not
registered as a service. In such a case, run OpcEnum -service from a
command prompt, and then reopen DCOMCNFG, return to this dialog box,
and select ‘The system account’.
20 Click OK.

Edit the properties of the ‘Experion PKS OPC Server’ DCOM Object
21 In Component Services, under DCOM Config, right-click Experion PKS OPC
Server and choose Properties.

64 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
22 In the General tab, edit the properties as shown in the following screen
example:

Uniformance - PHD/Experion Link Installation and Configuration Guide • 65

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘Experion PKS OPC Server' Properties, continued

23 Click the Location tab. Edit the properties as shown in the following screen
example:

66 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘Experion PKS OPC Server' Properties, continued

24 Click the Security tab.

Under Launch and Activation Permissions, select Customize and click

Edit.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 67

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘Experion PKS OPC Server' Properties, continued

68 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
25 Add the Distributed COM Users group to the list if it is not there already.

Ensure the Distributed COM Users local group has Remote Activation
enabled and Remote Launch disabled, as shown in the following screen
example.

Note: If the Remote Launch option is enabled, it may lead to multiple OPC
servers being launched when failover happens on Experion Servers. As
Experion servers automatically launch the OPC servers and there is no need
for the Experion link to launch it manually.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 69

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action
26 Click OK.

‘Experion PKS OPC Server' Properties, continued

27 On the Security tab, under Access Permissions, select Customize and
click Edit.

70 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘Experion PKS OPC Server' Properties, continued

28 Add the Distributed COM Users group to the list if it is not there already.

Ensure the Distributed COM Users group has Remote Access enabled, as
shown in the following screen example.

29 Click OK.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 71

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.3 On Experion Servers – Modify Default DCOM Settings

Step Action

‘Experion PKS OPC Server' Properties, continued

30 Click the Endpoints tab and set the properties as shown in the following
screen example:

72 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.4 On Experion Servers – Configure WMI Security

Step Action

‘Experion PKS OPC Server' Properties, continued

31 Click the Identify tab and set the properties as shown in the following screen
example (<local machine>\<user>), where user is the Experion Server local
mngr account.

32 Click OK.

ATTENTION
Perform this DCOM configuration (described in section 3.3) on both the
Primary and Secondary Experion Server nodes.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 73

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.4 On Experion Servers – Configure WMI Security

3.4 On Experion Servers – Configure WMI Security

On the primary and backup Experion Servers R400.x, perform the following steps to
verify the WMI security settings.

Figure 10 – Configure WMI Security

Step Action
1 Click Start > Run.

The Run dialog box appears.

74 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.5 On Experion Servers – Configure Windows Firewall

Step Action
2 In the Open box, type WMImgmt.msc.
3 On the left pane, right-click WMI Control and click Properties.

The WMI Control Properties dialog box appears.

4 Click the Security tab.
5 Click Root and then click Security.

The Security for Root dialog box appears.

6 Click Advanced.

The Advanced Security for Root dialog box appears.

7 Click Add.

The Select User, Computer, Service, Account or Group dialog box

appears.
8 In the Enter the object name to select box, type the name of the
Administrator and click OK.
9 On the Advanced Security for Root dialog box, select the name of the
Administrator and click Edit.

The Permission Entry for Root dialog box appears.

10 In the Apply to drop-down list, select the This namespace and sub-
namespaces option.
11 Click OK and then click Apply.
12 Click OK.
13 Restart the servers.

3.5 On Experion Servers – Configure Windows Firewall

Turn off the Windows firewall on the Experion Server or, if the Windows Firewall is
configured on the Experion Server, then refer to the white paper Using OPC via DCOM
with XP SP2.pdf, available at http://opcfoundation.org.
Perform this configuration on both the Primary and Secondary Experion Server nodes.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 75

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.6 Assign Windows User for Tag Synchronization Database Access

3.6 Assign Windows User for Tag Synchronization

Database Access
Perform this procedure if you created a new Windows user for use by Tag
Synchronization for connecting to the database.

Configure Tag Synchronization Database Access user

The PHD administrator must perform the following configuration through the
Uniformance System Console.

Step Action
1 Click the Uniformance System Console shortcut to open the Uniformance
System Console window.
2 Connect to the local server and click the Uniformance Tag Synchronization
item and then click Properties.
3 When the dialog opens, click the Tag Synchronization Users tab.

76 • Uniformance - PHD/Experion Link Installation and Configuration Guide

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.6 Assign Windows User for Tag Synchronization Database Access

Step Action

Define Database user

4 Click the Database User Account button.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 77

3 Prepare Domain Account, Experion Servers, and SQLServer User for PHD-Experion
Integration
3.6 Assign Windows User for Tag Synchronization Database Access

Step Action
5 Enter the user details in the dialog box that appears.

78 • Uniformance - PHD/Experion Link Installation and Configuration Guide

This page is intentionally left blank

Uniformance - PHD/Experion Link Installation and Configuration Guide • 80

 4. Prepare PHD Server for PHD-Experion
Integration
4.1 Add mngr Local Windows Account
The PHD Server node must be able to validate the user that the Experion PKS OPC
Server runs under - by default, this is mngr.
Add mngr as a local user on the PHD Server node.
To function properly, the mngr account must be configured on the PHD Server node
exactly as it is defined on the Experion PKS OPC Server node.

4.2 On PHD Server – Configure Windows Firewall

For Windows Server, turn off the Windows firewall on the PHD Server or, if the
Windows Firewall is configured on the PHD Server, then refer to the white paper Using
OPC via DCOM.pdf, available for download at http://opcfoundation.org On PHD Server
- Modify DCOM Settings
This section provides instructions for configuring the DCOM security to open the
communications between the PHD Server node and the primary and backup Experion
Server nodes.

TIP
Wrong settings here are the most common reason why an OPC client will be
able to do one-time reads of the remote OPC server, but will NOT get
exception data when it is subscribed and expecting the OPC server to send
back data only when it changes.

The user that the Experion PKS OPC server runs under must be granted
DCOM access on the machine running the OPC client. Failure to grant
DCOM access to the proper user prevents the OPC client from receiving
callbacks on subscription/exception reads from the OPC server.

On the PHD Server where the PHD Experion Link is to run, perform the following steps
to configure the default DCOM settings.

Step Action

Uniformance - PHD/Experion Link Installation and Configuration Guide • 81

4 Prepare PHD Server for PHD-Experion Integration
4.2 On PHD Server – Configure Windows Firewall

Step Action
1 Click Start, click Run, type DCOMCNFG, and click OK.

The Component Services window appears.

2 Expand Component Services, expand Computers, right-click My Computer,
and choose Properties.
3 Click the Default Properties tab.
4 Set the Default Properties as shown in the following screen example:

5 Click the Default Protocols tab.

6 Ensure that Connection-oriented TCP/IP is the first protocol listed.

82 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 4 Prepare PHD Server for PHD-Experion Integration
4.2 On PHD Server – Configure Windows Firewall

Step Action

7 Click the COM Security tab.

8 Under Access Permissions, click Edit Limits.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 83

4 Prepare PHD Server for PHD-Experion Integration
4.2 On PHD Server – Configure Windows Firewall

Step Action

9 Add NETWORK to the list and make sure Remote Access is selected, as
shown in the following screen example.

84 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 4 Prepare PHD Server for PHD-Experion Integration
4.2 On PHD Server – Configure Windows Firewall

Step Action

10 Click OK.
11 Under Access Permissions click Edit Default.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 85

4 Prepare PHD Server for PHD-Experion Integration
4.2 On PHD Server – Configure Windows Firewall

Step Action

12 Ensure that the Everyone group has permissions as shown in the following
screen example.

86 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 4 Prepare PHD Server for PHD-Experion Integration
4.3 On PHD Server – Configure Logon Account for RDIServer Service

Step Action

13 Click OK.
14 Click OK to close the window.

4.3 On PHD Server – Configure Logon Account for

RDIServer Service
Perform the following steps to configure the Uniformance RDI Server to run as a domain
user account and assign that account the required local security policies and local groups.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 87

4 Prepare PHD Server for PHD-Experion Integration
4.4 On PHD Server – Change PHD Security Server

Step Action
1 Log on to the PHD Server node as a domain administrator.

Note: Depending on the default domain policy, you may need to log on to the
PHD Server machine as a user with domain administration privileges – this
will allow you to specify a domain account as a service's logon account and to
be able to assign local policy rights to a domain account.
2 Configure RDI Server service's logon account:
a) Go to the Microsoft Services window.
b) Go to the Properties of the Uniformance RDI Server service.
c) Configure the service to Log On as the domain account that you created
previously (<domain>\<username>). For example CGY\PHDEXPLINK.
d) Enter the password of the domain account.
3 Configure the local policies for the RDI Server's account:
a) Go to Local Security Policy under Administrative Tools.
b) Under Local Policies>User Rights Assignment, double-click the policy
Act as part of the operating system.
c) Click Add User and add the RDI Server's domain account this local user
right.

Note: The operating system automatically assigns the user the 'Logon as a
service right', so you do not have to configure it.
4 Add the RDI Server's account to local groups:
a) Right-click My Computer and choose Manage.
b) Expand Local Users and Groups and open Groups.
c) Open the Product Administrators group and Add the RDI Server's user
(<domain>\<username>) to the group. For example CGY\PHDEXPLINK.
d) Click OK.
5 The configuration of the logon for the Uniformance RDI Server service will not
take effect until you restart the service or reboot the PHD Server node.

NOTE: If you plan to use a separate Windows account for the Uniformance Tag Sync
Service, then at this time you can assign that domain account to the required local groups
and policies also:

88 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 4 Prepare PHD Server for PHD-Experion Integration
4.4 On PHD Server – Change PHD Security Server

• Local Policy – assign the user the local user right to "log on as a service".
• Local Groups – add the user to the local Product Administrators groups.

4.4 On PHD Server – Change PHD Security Server

When the RDI server is configured to run using a specific user account (either local
account or domain account), attempts to start/stop/list links/RDIs may fail with an "-E-
FAILED to get security information" error. To resolve this issue, the following registry
setting needs to be changed to the username that is configured to run the RDI server:
Step Action
1 Click Start > Run.
The Run dialog box appears.
2 In the Open box, type regedit.
The Registry Editor window appears.
3 On the left pane, navigate to the following location:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RDIServer\
parameters\.
The RDI server parameters are listed on the right pane.
4 Right-click PHDSecurityServer and click Modify.
The Edit String dialog appears.
5 In the Value Data box, enter the user name of the account that is configured
to run the RDI server.
For example, if the RDIServer service is configured to run using a user
account called "domainname\PHDExpLink", the value of the
PHDSecurityServer registry setting needs to be changed to "PHDExpLink".

4.5 On PHD Server – Update HOSTS File

The Hosts file on the PHD Server (Windows\system32\drivers\etc) requires specific
entries for the PHD Experion Link and RDM to collect from a backup Experion Server in
the event of a redundant Experion Server fail-over. The same entries are in the Hosts file
on the Experion Server.
For redundant Experion Servers with FTE, list the Hostname twice after its IP address
with the second listing ending with a zero (0).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 89

4 Prepare PHD Server for PHD-Experion Integration
4.5 On PHD Server – Update HOSTS File

For a server with a dual network - that is, a second NIC (network interface card), add the
second IP address with the Hostname ending with a one (1).

Procedure to update Hosts file

Perform the following steps to add the required references to Experion Servers in the
Hosts file on the PHD Server.

ATTENTION
Do NOT delete "127.0.0.1 localhost" from the Hosts file. This entry (created
during Windows installation) is used by PHD Server functions.

Step Action
1 On the PHD Server computer, open the Hosts file in Notepad:
Windows\system32\drivers\etc

2 Modify the Hosts file. Substitute the IP addresses and Hostnames shown in
the examples with those on your system.
3 Save the modified Hosts file.
4 At a command prompt on the PHD Server, verify that you can ping the
Experion Servers by Hostname: PING <hostname><n>
Where: n is blank, 0, or 1
5 Verify that the ping returns OK and it returns the correct IP address.

Note: Verify that you can ping serverA, serverA0, serverA1 (if present),
serverB, serverB0 and serverB1 (if present), substituting your Hostnames.

Example: For a redundant Experion Server with FTE enabled, these

commands should display the IP address of the primary (Yellow) link:
ping LSTB-EXPA
ping LSTB-EXPA0
ping LSTB-EXPB
ping LSTB-EXPB0

Example HOSTS file entries

Non-redundant Experion Server:
10.1.0.1 lstb-exp

Redundant Experion Server:

90 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 4 Prepare PHD Server for PHD-Experion Integration
4.5 On PHD Server – Update HOSTS File

# TCP/IP address for the primary

10.1.0.1 lstb-expa lstb-expa0
# TCP/IP address for the backup
10.1.0.2 lstb-expb lstb-expb0
Redundant Experion Server with FTE (IP address of FTE yellow link):
# TCP/IP address for the primary
10.1.0.1 lstb-expa lstb-expa0
# TCP/IP address for the backup
10.1.0.3 lstb-expb lstb-expb0

Dual Network, Redundant Experion Server:

# First TCP/IP link of the primary
10.1.0.1 lstb-expa lstb-expa0
# Second TCP/IP link of the primary
10.1.1.1 lstb-expa1
# First TCP/IP link of the backup
10.1.0.2 lstb-expb lstb-expb0
# Second TCP/IP link of the backup
10.1.1.2 lstb-expb1

TCP/IP Hostname and "Target Host Name"

When you configure the PHD Experion Link, you will specify a "Target Host Name" in
the PHD Links Configuration form. The "Target Host Name" is the base hostname of the
Experion Server, without the A/B or the 1/0 characters.
Note: You will be able to ping the TCP/IP names; but if the PHD Experion Link is
configured for a redundant or FTE Experion Server, you will not be able to ping the
"Target Host Name."
The following figure compares IP names in the HOSTS file to the "Target Host Name" of
the PHD Links Configuration form.

Figure 11 – TCP/IP Name and "Target Host Name"

Experion Server IP

Non-redundant Experion Server:

TCP/IP Name: LSTB-EXP 10.1.0.1

Uniformance - PHD/Experion Link Installation and Configuration Guide • 91

4 Prepare PHD Server for PHD-Experion Integration
4.6 On PHD Server – Update Services File (Optional)

Experion Server IP

"Target Host Name" LSTB-EXP

Redundant Experion Server:

1- TCP/IP Name: LSTB-EXPA 10.1.0.1

2- TCP/IP Name: LSTB-EXPB 10.1.0.2

"Target Host Name" LSTB-EXP

Redundant Experion Server with FTE:

1- TCP/IP Name: LSTB-EXPA 10.1.0.1

2- TCP/IP Name: LSTB-EXPB 10.1.0.3

"Target Host Name" LSTB-EXP

Dual Network, Redundant Experion Server:

1- TCP/IP Name: LSTB-EXPA 10.1.0.1

10.1.1.1
2- TCP/IP Name: LSTB-EXPB 10.1.0.2
10.1.1.2
"Target Host Name" LSTB-EXP

4.6 On PHD Server – Update Services File (Optional)

By default, the Experion Tag Synchronization server listens on TCP port 49999. Before
installing Uniformance Tag Synch Server on the PHD Server, update the PHD Server's
\WINDOWS\system32\drivers\etc\ Services file to reserve this port number, which the
Uniformance TagSync Service will use to connect to the Experion Server.
Example lines in the Services file on a PHD Server are as follows – in this example, the
last line applies to Tag Synchronization:
# <service name> <port number>/<protocol> [aliases...] [#<comment>]
Unfphd 2000/tcp phdserver # Uniformance PHD Server
Unfapi 3100/tcp apiserver # Uniformance API Server
Unfapitel 3101/tcp apitelnet # Uniformance API Server Telnet
Unfrapi 3150/tcp rapiserver # Uniformance RAPI Server

92 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 4 Prepare PHD Server for PHD-Experion Integration
4.7 On PHD Server – Increase the Maximum PHD Tags (PhdParams.Dat)

Unfrapi 3151/tcp rapitelnet # Uniformance RAPI Server Telnet

Unfrdi 4100/tcp rdiserver # Uniformance RDI Server
Unfrditel 4101/tcp rditelnet # Uniformance RDI Server Telnet
myrdi1_Active 4200/tcp # Uniformance RDC
myrdi1_Standby 4201/tcp # Uniformance RDC
Unfmon 41000/tcp phdstart # Uniformance PHD Startup Server
Unfts 49999/tcp htsserver # Uniformance Tag Synchronization

ATTENTION
• The ports in the Services file must be in ascending numerical order.
• Reboot the computer after updating the Services file.

4.7 On PHD Server – Increase the Maximum PHD Tags

(PhdParams.Dat)
The number of Experion tags assigned to history + the existing number of PHD tags
should not exceed the PHD system parameter MAX_TAGS.
You should ensure that tags built against the new PHD Experion Link (either manually or
by the Tag Synchronization service) will not exceed the specified maximum for the PHD
Server.
Note: The number of PHD tags that will be built automatically by the Tag
Synchronization service, if installed, depends on the number of point parameters assigned
to Experion history collection and the Tag Synchronization Rules. For example, Tag
Synchronization may build three PHD tags (PV, OP, and SP) for each Experion history
point that matches the expression of a specific rule.
Perform the following steps to view or modify the maximum number of tags configured
for the PHD System, to ensure that tags built against the new PHD Experion Link do not
exceed the specified maximum.

Step Action
1 Open the file <install directory>PHDServer\NtSite\PhdParams.Dat.
2 If necessary, increase the values of the following parameters:
• MAX_TAGS - Maximum number of defined tags.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 93

4 Prepare PHD Server for PHD-Experion Integration
4.7 On PHD Server – Increase the Maximum PHD Tags (PhdParams.Dat)

Step Action
• MAX_TAGNO - Maximum possible tag numbers.
3 Save the file.
4 If you modified the above parameters, then you need to Stop and Cold Start
the PHD Server in order to resize its global memory sections.

To restart the PHD Server, execute the following commands at a command

prompt:

PHDCTL STOP

PHDCTL START COLD

94 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 5. Install Software for PHD-Experion Integration
5.1 On PHD Server - Install RDM and System
Management Display for Experion 300 (Optional)
If the PHD Experion Link is to connect to redundant Experion Servers, install the
Redirection Manager (RDM) software on the PHD Server machine that will run the PHD
Experion Link. The RDM supports failover of the PHD data collection interface with
redundant Experion Servers.
RDM installation includes installation of the Honeywell System Management Runtime
software package, which provides the base infrastructure for Honeywell System
Management. You install System Management Runtime on every node that is to be
integrated into a system of "managed nodes."
The Honeywell System Management Display can be installed optionally on the PHD
Server node to aid in monitoring and troubleshooting the RDM.
The Honeywell System Management Display is a Microsoft Management Console
(MMC) snap-in that exposes the tools necessary to configure and monitor a system of
nodes – it can be installed on one or more nodes in the system. The System Management
Display interacts with each node's System Management Runtime components to
determine the status of each "managed" node.

ATTENTION
This guide provides a basic software installation procedure for RDM and the
System Management Display, but it does not address the larger implications
for configuring the Honeywell system management infrastructure.

Make sure you are aware of your system's configuration requirements for
Honeywell system management.

REFERENCE
For details on Redirection Manager, refer to the Experion Redirection
Manager User's Guide in the Experion book set.

For details on Honeywell System Management, refer to the Experion System

Management Configuration Guide in the Experion book set.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 95

5 Install Software for PHD-Experion Integration
5.1 On PHD Server - Install RDM and System Management Display for Experion 300 (Optional)

Prerequisites
RDM is an Experion component and therefore falls under Experion restrictions. The
PHD-compliant server that will run RDM must run a Windows operating system that is
Experion-compliant.

Procedure to install RDM and System Management Display

Step Action
1 On the PHD Server node that will run the PHD Experion Link, insert the
Experion Installation DVD.
2 Review the information about installing software, license agreements, and
third-party compatibility. On each screen, click Next to continue.
3 On the User Information screen, type your Name and Company details.

For PHD, accept the default for License and Authorization numbers (blank)
and click Next to continue.
4 Select Run Experion Media Browser.
a) Click Install/Migrate Experion PKS.
b) Select Install Clean.
c) Select Optional Features.
d) Select No TPS Licensed Components.
e) Select HCI Runtime and System Management Runtime.
f) Enter Local COM and MNGR passwords.
5 Click Install Package.

The installation begins.

6 After the installation is complete, restart the server.
7 On the Windows services, verify that whether all the sm- services have
started.

96 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 5 Install Software for PHD-Experion Integration
5.1 On PHD Server - Install RDM and System Management Display for Experion 300 (Optional)

Step Action

ATTENTION
If any of the sm- services is not started, try starting the services again.
Reinstall the System Management Runtime again if the sm – services are not
started.

If the sm- services are not started, Redirection Manager cannot be installed.
8 Insert the Experion Installation DVD.
8 Select Browse Contents and browse to the location
Packages/RedirectionManager on the DVD.
9 Double-click the .msi file.

The installation begins.

10 After the installation is complete, restart the server.
11 Verify that all the sm- services are running.

The RDM Configuration can be viewed from the Configuration Utility.

ATTENTION
The PHD Server and Experion Servers must run the same version of the
following components, which are common to RDM and the System
Management Display:
• Honeywell Packaged Redistributable Files

• Honeywell HCI Runtime

• Honeywell System Management Runtime

• Honeywell Admin Support Files

Additional RDM settings on non-Experion nodes

Perform the following to install RDM on non-Experion nodes from the Optional
Features in the Experion PKS Installation DVD:
Step Action
1 Install HCI Runtime and System Management Runtime.
2 Double-click the honeywell_redirection_manager.msi file to install RDM

Uniformance - PHD/Experion Link Installation and Configuration Guide • 97

5 Install Software for PHD-Experion Integration
5.2 On PHD Server - Install PHD Point Server (Optional)

Step Action
from the following location: \Packages\RedirectionManager\ folder.
RDM is installed on the non-Experion nodes.

Alternative approach for Experion Link to connect to redundant Experion servers

If you do not want to install RDM, you can use an alternate approach to connect the link
to the redundant Experion servers.
3. In PCT update the Experion Link definition.

• Turn off the “include” flag on the RDMNUMBER parameter.

• Ensure the HOSTNAME parameter is configured with the Experion

server pair hostname (without the trailing A/B)
4. On each PHD Buffer:

• Create the following DWORD:

HKLM\System\CurrentControlSet\Services\RDIServer\Parameters\Lin
kList\<LinkName>\RedundantPair = 1.

• Run RDISetup to update the configuration in interfaces.dat and in the

registry.

• Restart the Experion Link(s)

With the above configuration in place, the Link will attempt to connect to server A, and
if that fails, it will connect to server B, etc.
When the Experion servers fail, the Link’s interface state will go to INACTIVE, and 30
seconds later, it will attempt to connect to the other Experion server. It will keep toggling
between the servers until it successfully establishes a connection.
Note that when the Link is connecting through RDM, the Link’s interface state
continually stays ACTIVE.

98 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 5 Install Software for PHD-Experion Integration
5.2 On PHD Server - Install PHD Point Server (Optional)

5.2 On PHD Server - Install PHD Point Server (Optional)

Install the Experion PHD Point Server on the PHD Server node to support retrieval of
PHD data by an Experion Server for native Experion trends.

Prerequisites for Experion PHD Point Server installation

For installing the Experion PHD Point Server, you must:
• Have Administrator privileges
• Have the password for the local Windows manager account of the Experion Server
• Install Microsoft .NET Framework version 4
• Install PHD .NET Wrapper
NOTE: Installing the minimum Uniformance Desktop installs the following items:
- Microsoft .NET Framework
- PHD .NET Wrapper
- DAO 3.6
Alternatively, you can download .NET Framework from www.microsoft.com.

Procedure to install Experion PHD Point Server

NOTE: The following instructions allow you to install the Experion R410 PHD Point
Server on a PHD R300 Server. For instructions on installing Experion PHD Point Server
for earlier versions of Experion or PHD, refer to the previous versions of this guide.

Step Action
1 Install the prerequisites on the PHD Server.
2 On the PHD Server, insert the Experion R410 Applications DVD.
3 Browse to the Server-Client\PHDPointServer folder on the DVD and run the
Experion PHD Point Server.msi installation application.
4 When prompted for the mngr password, type the same password as the
Windows local mngr account on the Experion Server.
5 Click Install.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 99

5 Install Software for PHD-Experion Integration
5.3 On PHD Server - Install Tag Synchronization (Optional)

Step Action

Note: The Experion PHD Point Server installation program only checks for the
prerequisite software, but does not install the prerequisites.

Result: The PHD Point Server is installed.

6 Browse to the ServerClient\PHDPointServer folder on the DVD and run the
PHDCentralNameUpdate.vbs application.
7 When prompted to enter the Central Name, type the base name of the
Experion Server that communicates with the PHD Server.

Note: If the Experion Server is non-redundant, type the full name. If the
Experion Server is redundant, type the base name. For example, if the names
of the redundant pair are SERVERA and SERVERB, the base name is
SERVER.

5.3 On PHD Server - Install Tag Synchronization

(Optional)
Tag Sync installation requirements
• The system that will host Uniformance Tag Synchronization requires Microsoft’s
.NET framework. Uniformance R210.1.2 and later Tag Sync requires .NET version
2.0. Installing the minimum Uniformance Desktop from R210.1.3, R215, R300,
R310 or R320 will install .NET version 2.0.
• Install the Uniformance Tag Synchronization software on the PHD Collector Server
that is to run the PHD Experion Link.
• The installation of Uniformance Tag Sync Server requires a Windows account that
the Uniformance Tag Sync Service will use to access the database (see section 2.5,
"RDI Server account requirements"). The Experion Server will need to be able to
authenticate this account. Honeywell recommends that this be a domain account. The
PHD Server and Experion Server must be in the same domain.
• The Uniformance SQLServer Database server will need to be able to recognize the
Tag Synchronization service's Windows username as valid Windows user (see
section 2.5, "SQLServer user for Tag Synchronization").
• The database user must be assigned to the “Local Engineers” Role that has
permission to insert/update to the database.

100 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 5 Install Software for PHD-Experion Integration
5.3 On PHD Server - Install Tag Synchronization (Optional)

Procedure to install Tag Synchronization

ATTENTION
Before you start the installation: To be able to run the setup installation program, you
must be logged on to the local node as a user that has local administration privileges.

Perform the following steps to install Uniformance Tag Synch Server on the PHD Server.

Step Action
1 Insert Uniformance DVD-ROM.
2 If the Uniformance menu launches automatically, go to the Step 3.

If the Uniformance menu does not launch, launch it manually:

a) Open Windows Explorer.
b) Right-click on the CD-drive and then click Auto Play.
Or
Browse the CD-ROM drive and in the Documentation directory double-click
launch.exe.
3 From the Honeywell Uniformance menu, click Software Installations.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 101

5 Install Software for PHD-Experion Integration
5.3 On PHD Server - Install Tag Synchronization (Optional)

Step Action
4 The Uniformance Software Installations menu will be displayed.

Double click Uniformance Tag Synchronisation Server.

5 On the 'Destination Folder' window, click Next, unless you need to change the
Destination Folder.

Honeywell recommends that you keep the default (Program Files \Honeywell
\Uniformance).
6 Click Finish to complete the installation.

Result: The Uniformance TagSync Service is installed, but not started.

102 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 5 Install Software for PHD-Experion Integration
5.3 On PHD Server - Install Tag Synchronization (Optional)

ATTENTION
To prevent premature PHD tag creation, do not start the Uniformance TagSync
Service.

If you have existing PHD tags or you wish to build PHD tags in your Uniformance
system prior to activating the Uniformance TagSync Service (such as parent tags
to be used by Tag Synchronization), then ensure that the Uniformance TagSync
Service is not started.

Do not start the Uniformance TagSync Service until you have evaluated the
Default Tag Synchronization rule and Default parent tags and determined them to
be satisfactory or modified or added rules that are suitable for your site.

Tag Synchronization upgrades/patches

Note: If you reinstall Tag Synchronization, you must also ensure the Experion host name
list in the registry has the correct hostnames of the Experion Servers. This registry key is
located at
HKLM\System\CurrentControlSet\Services\UniformanceTagSync\Parameters\SystemLis
t\Experion\Machines
When the PHD Experion Link is configured with RDM, the server list in the Tag
Synchronization Server is automatically updated when you run the RDI Setup Utility.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 103

 6. Configure PHD-Experion Integration
6.1 On PHD Server - Configure System Management
Display (Optional)
If you installed the optional System Management Display, then perform the required
steps to configure it.

REFERENCE
For details about configuring the System Management Display, refer to the
Experion System Management Configuration Guide in the Experion book set.

6.2 On PHD Server - Configure RDM (Optional)

If you installed the optional Redirection Manager (RDM) software, perform the
following steps to configure the RDM as an HCI (Honeywell Communications Interface)
component.

REFERENCE
For details about RDM configuration, see the Experion Redirection Manager
User Guide in the Experion book set.

Step Action
1 Go to the HCI Component Configuration Page using one of these methods:
• Method 1: Open the Honeywell Configuration Utility and select HCI
Component from the Configure menu.
• Method 2: In a Honeywell Experion PKS>System Management> System
Management Display, right-click the PHD node and select
Configure>HCI Component.
2 From the HCI Component Page, click the Base PROGID drop-down list and
select an available component ID (for example, Honeywell.Redirect1).
3 Enter a Component Name for your Redirection Manager and then click
Check Name to ensure the name is not already in use.

Uniformance - PHD Experion Link Configuration Guide • 105

6 Configure PHD-Experion Integration
6.2 On PHD Server - Configure RDM (Optional)

Step Action

4 Click the Enter/Edit Server Specific Configuration button.

5 Respond to the message dialogs by clicking Yes.
6 From the Redirection Manager Device Specific Configuration page, select the
primary and secondary Experion Server nodes using the drop down lists, or
click Browse and navigate to the nodes.

7 For both the PRIMARY and SECONDARY Experion nodes, double-click

HWHsc.OPCServer from the OPC HDA Server 1.2 list of class IDs.

Ensure you have assigned both the primary and secondary Experion Servers
to the Redirection Manager.
8 Optionally, you may click Supplemental Configuration and choose the
RDM's node status detection mechanism to be "WMI Provider for Remote
Node Status" or "ICMP Echo."

106 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.3 In PHD Configuration Tool – Configure PHD Experion Link

Step Action
9 Click OK.
10 The Experion Servers are validated and any errors or warnings are displayed
in message boxes.

6.3 In PHD Configuration Tool – Configure PHD Experion

Link
You must complete the PHD Links Configuration form to define the information about
the servers to which the PHD Experion Link will communicate and the name of the
optional Redirection Manager (RDM).
Perform the following steps to complete the PHD Links Configuration form.

Step Action
1 Launch the PHD Configuration Tool: Start > Programs > Uniformance >
PHD Configuration Tool > PHD Configuration Tool
2 Under Interfaces, open the form Interfaces (RDI’s and Links).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 107

6 Configure PHD-Experion Integration
6.3 In PHD Configuration Tool – Configure PHD Experion Link

Step Action
3 Enter data in the fields as required for the new Link.
For descriptions of the fields, refer to Table 2.

4 After entering the required data, close the form.

Table 2 – PHD Links Configuration Form Entries

Field in form Description

* RDI/Link Name Enter a name for this link. Limited to 10 characters.

The Link Name and Target Host Name combination must

be a unique identifier that will be used to identify data
parameters to be collected by the Link.

* Host Name Select or type the host name of the PHD Server that is to
run this link. Must be uppercase.

Primary TDA Host Check if this PHD Server is the main server holding
these tags.

108 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.3 In PHD Configuration Tool – Configure PHD Experion Link

Field in form Description

* Description Enter a description for this Link.

Enabled Check this option to enable the Link.

* RDI Type Name EXPERION – Select ‘Experion’ if the link is to

communicate to an Experion Server.

PHDLINK – Not implemented.

Remote RDI Type Name Not Used

Source System Select OPC

Parameter HOSTNAME Enter Experion server name for standalone Experion

Server or Experion redundant server base name for
redundant pair Experion while using Tag
Synchronization.

Enter Experion server name for Experion Link to collect

data from standalone Experion Server. Experion Link
ignores this parameter when RDM/ORB is configured.
However, the server list in the Tag Synchronization
Server is automatically updated when you run the RDI
Setup Utility.

Parameter Select the Base PROGID number of the Redirection

RDMNUMBER Manager that was specified through the HCI Component
dialog box (shown below) when the RDM was configured
on the PHD Server. E.G. 1 in the below example.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 109

6 Configure PHD-Experion Integration
6.3 In PHD Configuration Tool – Configure PHD Experion Link

Field in form Description

Parameter Enter the OPC PROGID name of the ORB that was
ORBPROGID specified through the MatrikonOPC Redundancy Broker
Configuration Tool.

The PROGID format is ORB.<custom name> .1.

Note: Do not configure RDMNUMBER parameter while

configuring the ORBPROGID parameter.

Maximum History Enter the maximum number of minutes of history to

Recovery Interval recover. Default is 10080 minutes, which is 7 days (7 *
1440 minutes/day). This field should be set to a value
less than or equal to the maximum history stored on the
Experion Server.

Practically speaking, the MAX_HISTRECMN should be

set to a number that will capture the maximum time that
the interfaces between the PHD Server and the Experion
Server may be down. Normally, one week (10080) is a
good number to use.

Note: You may choose to use a larger number for initial

history recovery (for example, to recover 6 months of
history from an existing Experion Server's history
database), and then (after the initial history recovery has
completed), change the value to the actual number
wanted for ongoing operations.

0 = No History Recovery
For details on how History Recovery works, see section
1.3, "History Recovery".
Check For Download Set the frequency in seconds that RDI Server should
check for new values to be written to the Experion
Server. Default is every 2 seconds.

110 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.4 On PHD Server - Create Registry and File Entries for PHD Experion Link

Field in form Description

Maximum Queue Default to 0.

Overwrite Log

Statistics ON – PHD will collect scan rate statistics for the Link.

OFF – PHD will not collect statistics. Default is OFF.

Tag Update on Range Indicates whether the Link should trigger a PHD tag
Change update when a change occurs to the low or high range
value on Experion Server points.

ON – PHD will perform a tag update based on a tag

high/low range change event from the Experion Server.

OFF – PHD will not perform a tag update based on a tag

high/low range change event from the Experion Server.
Synchronized tag definitions will be changed in the
database, but this Link on the PHD Server will not be
updated.

Default is OFF.

This should be left OFF in most cases.

* The asterisks (*) in the table indicate mandatory fields.

6.4 On PHD Server - Create Registry and File Entries for

PHD Experion Link
Before you begin
Consider performing the following steps on the PHD Server that is to run the PHD
Experion Link.

Step Action

1 Make a backup copy of the following files located at <install directory>

\PHDServer\NtSite\:

Interfaces.Dat

Start_Interfaces.Dat.
2 If the Link was previously created in error, execute the PHDMAN command to

Uniformance - PHD/Experion Link Installation and Configuration Guide • 111

6 Configure PHD-Experion Integration
6.4 On PHD Server - Create Registry and File Entries for PHD Experion Link

Step Action
shutdown the Link:

PHDMAN SHUT INT <linkname>

Procedure to run RDISetup

The RDISetup utility reads the database configuration of the PHD Experion Link and,
upon user selection of the Save RDI/Link Configuration command, creates entries for the
new Link in the registry, the Interfaces.Dat file, and the Start_Interfaces.Dat file.
Perform the following steps to run RDISetup.

ATTENTION
• Perform the following procedure on the PHD Server machine on which
the Link is to run.
• Log on to the operating system as a user that is a member of the Product
Administrators group.
• If you change a local right (for example, if you add the logon user to the
local Product Administrators group), you must log off and log back on to
the machine to establish the change.

Step Action
1 On the PHD Server where the Link is to execute, select
Start>Programs>Uniformance>PHD Server>PHD RDI Configuration

TIP: Alternatively, you can Run rdisetup (Start>Run) or double-click on

RDISetup.exe.

RESULT: The RDISetup user interface is displayed.

2 In the left pane, select the Link of interest.

RESULT: The link parameters appear in the right pane, as shown in the
following screen example for link EXPTEST1.

For definitions of the fields, refer to Table 3 – RDI Setup Indicators and
Checkboxes.

112 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.4 On PHD Server - Create Registry and File Entries for PHD Experion Link

Step Action

3 Ensure the following checkbox is checked if it is not checked, RDISetup will

not save the configuration for this Link to the local registry and files):

4 Select File and choose Save RDI/Link Configuration.

RESULT:
• The Interfaces.Dat and the Start_Interfaces.Dat files now contain SET
commands to define the Link parameters to PHD (see following screens).
• The PHD Experion Link is registered under the specified RDI Server:

HKLM\ SYSTEM\ CurrentControlSet\ Services\ <RDI

Server>\ Parameters\ LinkList\ <linkname>

Uniformance - PHD/Experion Link Installation and Configuration Guide • 113

6 Configure PHD-Experion Integration
6.4 On PHD Server - Create Registry and File Entries for PHD Experion Link

Step Action
• If Tag Synchronization is present on this machine, then the value of the
following registry key is populated with the Experion "Target Hostname":
HKLM\ SYSTEM\ CurrentControlSet\ Services\
UniformanceTagSync\ Parameters\ SystemList\ Experion\
Machines

TIP: If you install Tag Synchronization at a later time, then you must ensure
'Machines' registry key has the names of the Experion hosts to be Tag
Synch’d.

Table 3 – RDI Setup Indicators and Checkboxes

Indicator/Field Description

Folders The left pane shows the names of RDIs and Links read from the database
and local data.
Bold letters: Indicates that differences exist between the local and the
database data.

114 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.4 On PHD Server - Create Registry and File Entries for PHD Experion Link

Indicator/Field Description

Parameter After you select a PHD Experion Link in the left pane, the right pane shows its
Name/ Value configuration data. The parameter list can show either the database or local
data, depending on your selected state of the "Use Local Parameter Values"
checkbox.
If you need to change a value, double-click the parameter and enter the new
value.
Red color: Indicates that the local value and the database value are different.

Checkbox The following checkbox determines whether or not RDISetup will save
configuration for this Link when you execute the 'Save RDI/Link
Configuration' command:

If checked, then RDISetup will save the Link

configuration to the files and registry.

If unchecked, then RDISetup will not save the

configuration, and will discard any changes.

The following checkbox determines what values are displayed in the right
pane parameter list and what data (local or database) will be saved to the
files and registry when you select the File>Save RDI/Link Configuration
command:

If checked, the parameter list in the right pane

shows local data, and RDISetup will use the
local data when it saves the configuration of this
Link to the files and registry.

If unchecked, the parameter list in the right

pane shows the database data, and RDISetup
will use the database data when it saves the
configuration of this Link to the files and
registry.

If you used RDISetup to make changes to values for this PHD Experion Link
and you want RDISetup to save those previous locally-resident changes,
make sure the checkbox contains a checkmark before you select the 'Save'
command.

Note: RDISetup does not write to the database. For details on the data flow
of the RDISetup utility, refer to Appendix B.

RDI Server Specifies the RDI Server service that runs this Link. Note: Most PHD
Instance systems require only one instance of RDI Server. All PHD Experion Links
running on a PHD Server can use the same RDI Server instance and port
number.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 115

6 Configure PHD-Experion Integration
6.4 On PHD Server - Create Registry and File Entries for PHD Experion Link

Indicator/Field Description

RDI Server Specifies the RDI Server port used by this Link.
Port

Procedure to run Interfaces.Dat

After you run RDISetup, you need to execute the Interfaces.Dat file to define the new
Link to the PHD Server.
In a running PHD system, perform the following steps to manually execute the
Interfaces.Dat file through the PHDMAN utility, which completes the definition of PHD
Experion Link.
Note: If the PHD system is not running, a startup of the PHD system (PHDCTL Start
or PHDCTL Start Cold) causes the Interfaces.Dat file to be executed automatically.

Step Action
1 On the PHD Server where the PHD Experion Link is to run, open a command
prompt and enter the following command:

PHDMAN EXECUTE %PHD_ROOT%\NTSITE\INTERFACES.DAT

Note: Alternatively, you can use the PHDMAN shortcut on the desktop,
which defaults to the path of the NtSite directory.

RESULT: The configuration is written to the PHD Server's SCON memory

section.
2 Verify that the new PHD Experion Link is now available:

PHDMAN SHO INT <linkname>

Add parameter to registry and change default value

ATTENTION
Because the default behavior of the PHD Experion Link will negatively impact
history recovery performance, Honeywell recommends that you add the
parameter IgnoreNegativeConfidence to the registry and set it to a
value of 1.

This disables the insertion of a 0 (zero) tag value with a -1 confidence

whenever the Link is started, shutdown, or every 24 hours when the Link

116 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

resynchronizes its time.

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\

<RDI Server>\ Parameters\ LinkList\ <linkname>\
IgnoreNegativeConfidence

REFERENCE: For other registry settings, refer to Appendix A –PHD Experion Link
Registry Settings, in this guide.

6.5 In PHD Configuration Tool - Configure Tag

Synchronization Rules
What Tag Sync rules are needed?
To determine what Tag Sync rules are needed, you must understand the fields coming
from the Experion Server to determine if the values that will come in can be used "as is".
For example, each point.parameter will have a high and low range. These may be valid
to use with PHD or they may need to be modified. If the range values can be used "as
is", then the rule is simple, because incoming fields are moved directly into the
corresponding PHD tag field.
The second factor to consider is whether or not the PHD tags already exist. This can
affect what PHD tag fields you should allow Tag Sync to change.
• You may not want to allow Tag Sync to change the current PHD high and low range.
• If the existing PHD tag names are considerably different from the Experion
point.parameter names, then the Tag Sync rule needs to take this into account, so that
it does not change the PHD tag name.
Before performing Tag Sync, create any required parent tags in the Tag Configuration
form, and the required rules in the Tag Synchronization Rule Configuration form
For any given tag, only one rule will execute. The staging table indicates which rule was
applied. The staging table is viewed through the PHD Tag Synchronization
Acknowledgement form.

To view and evaluate the default rule

The default rule is the rule that executes if no other rules match or if no other rules are
present. Perform the following steps to view the Honeywell-supplied default rule.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 117

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Step Action
1 Open the PHD Configuration Tool.
2 Under Interfaces > select RDI Types.
3 In the Current list of RDI Types, select EXPERION.
4 On the Tag Synchronization Rules tab, click DEFAULT_RULE.

Result: The default rule displays.

5 Configure the default rule to suit your needs.

REFERENCE
For a description of the default rule, refer to the subsection "Honeywell-
supplied default rule text for Experion" in this guide.

To view and evaluate the default parent tag

The default rule assigns the Parent Tag to be EXP_PARENT
Perform the following steps to view the Honeywell-supplied default Parent Tag.
Step Action
1 Open the PHD Configuration Tool.
2 Select the Tags form.
3 Enter EXP_PARENT in the search box and click Go.

Result: The Honeywell-supplied default Parent Tag displays.

Determine whether the default Parent Tag is suitable for your site. You may need to
modify it and/or configure additional Parent Tags.
REFERENCE
For a description of the default Parent Tag, refer to the subsection
"Honeywell-supplied default Parent Tag for Experion" in this guide.

For guidelines on Parent Tags, refer to the section "Rule examples for
Experion", subsection "General considerations."

118 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

To configure a new rule

Perform the following steps to configure a new rule. The examples shown in the steps
will create a rule for configuring MODE tags.

Step Action
1 Open the RDI Types configuration form.
2 In the Current list of RDI Type records, select EXPERION.
3 Click New RDI Type > New Tag Synchronization Rule.
4 Enter the name for the new rule.

For example, enter MODE_RULE.

5 In the Variable Name box, select the incoming Experion tag variable that you
want Tag Sync to examine:

ASSET
DISPLAYTYPE (ESVT Only)
ENTITYTYPE
EXTENDEDHIGHRANGE
EXTENDEDLOWRANGE
HISTORYINTERVAL
ITEM
MACHINENAME
PARAMETER
POINTNAME
SOURCETAGATTRIB
SOURCETAGTYPE
RANGE_HI
RANGE_LO
EXPDESCRIPTION

For example, select PARAMETER

6 In the Regular Expression box, enter the expression on which the rule
can match.
For example, enter MODE.

ATTENTION: By default, Regular Expressions are case sensitive.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 119

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Step Action
7 In the Rule Text box, enter the logic that you want.

For example, copy/paste the Rule Text from the DEFAULT_RULE to the
MODE_RULE, and then modify it as follows: TagUnits = ""

8 (Optional) To check rule syntax, you may choose to select Export Rule to
export the rule text to a file.

Then you can insert the rule text into a Visual Studio 2005 project and
compile it there.

After syntax checking is completed (solution builds), copy/paste the rule text
back into the Tag Synchronization Rule Configuration form.
9 Move the DEFAULT_RULE to the bottom of the list, as follows:
a) Click DEFAULT_RULE.

Click the down arrow until DEFAULT_RULE displays at the bottom of

Configured Rules, as shown below:

10 Add more rules, as needed.

ATTENTION
Ensure that the DEFAULT_RULE is always at the bottom of the list.

REFERENCE: For more rule examples, refer to the subsection "Rule examples for
Experion" in this guide.

Honeywell-supplied default rule text for Experion

Tag Sync executes the default rule if no other match is found or if no other rules are
present. The default rule should be the last rule in the list.

120 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

PHD software release updates do not overwrite the default rule text, so any customer
changes to the default rule will not be discarded during an upgrade - consequently,
Honeywell improvements to the default rule are not supplied in the database.
Please manually enter the improved default rule text, if you want to use it.

Default rule text provided in the database

// Set the Parent to the standard EXP_PARENT
ParentTagName = "EXP_PARENT"
Active = "X"
Quantum = -1
TagName = PointName + "." + Parameter
If Length( TagName ) > 32 Then
TagName = "" See Note 1
Endif
ScanFrequency = HistoryInterval / 1000 See Note 2

Improved default rule text

'Set the Parent Tagname to the default Experion Parent tag. Also
‘set the tagname to the point.parameter UNLESS the combination
‘of these two is greater than 32 characters. In this case, let TagSync
‘define the tagname which can be updated later.

ParentTagName = "EXP_PARENT"

TagName = PointName + "." + Parameter

If (Tagname.Length > 32) Then
Tagname = Nothing See Note 1
End If

'If this is an enumeration, set the attribute to a string.

If (SourceTagType = "EN") Then
SourceTagAttrib = "STRING" See Note 3

Uniformance - PHD/Experion Link Installation and Configuration Guide • 121

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

End If

'By default the rules are implicitly acknowledged. Delete

'the following line if this is not desired.
Acknowledge() See Note 4

Notes
Note 1: This statement sets the tagname to the point.parameter UNLESS the combination
of these two is greater than 32 characters. In this case, Tag Sync defines the tagname as
EXPERION_xxxx, where xxxx is a sequentially increasing number – you can update this
tagname later. 'Length' is a method that can be referenced in a rule.
Note 2: This statement sets the Scan Frequency (seconds) to the Experion History
Interval (milliseconds). This scan frequency step is not required in PHD 215 or PHD
210.1.2 and greater.
Note 3: This statement configures PHD to historize the enumeration string instead of the
ordinal value. See section 8.7, "Collect and Access Enumeration Data".
Note 4: This statement automatically acknowledges any tag definition changes. See
section 0, "To view synchronized tags in staging table before sending tag definitions to
PHD".

Honeywell-supplied default Parent Tag for Experion

The default rule for EXPERION assigns the Parent Tag to be EXP_PARENT. The
Honeywell-supplied Tag Configuration of EXP_PARENT is as follows:
Description: Experion parent tag
Collection X
Demand Calculation
Manual Input
Put Download
Data Store X
Data Edit
Archive Resample
Digital Enumeration
Automatic Synchronization X
Data Collection
Source Tag Specification
Source Tag Index
Source System Type EXPERION
Source Tag Type AS

122 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Source Tag Attribute VALUE

Source Tag Units
Collector Name
Scan Frequency 60
Scan Timestamp Unit s
Tolerance, Type
Digital Enumeration List Name
PHD Link Name
PHD Link Point Name
PHD Link Parameter Name
Data Processing
Gross Error Sigma Limit
Gross Error Samples
Smoothing Constant
Noise Gate Level
Compression Tolerance Factor -1
Min Compression Tolerance
Scale High Extreme
Scale Low Extreme
Quantum
General
Data Type C
Data Length 80
Spec Queue Size
Resample Method
Extrapolation Damping
Interpolation Method
Percent Record Fill
User Defined 1
User Defined 2
Synchronization Rule Name
Asset Name
Item Name
Rule examples for Experion

General considerations
PHD tag attributes are either
• Set by Tag Sync (default value or explicit rule value), or
• Inherited from the parent tag.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 123

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Attributes that can be set by a PHD parent tag include the following:
• Enable flags
• Tolerance related attributes
• Interpolation Method
You will be able to manually change the tag configuration of these inherited attributes
after the tag has been created.
To aid in ongoing PHD tag maintenance, you may choose to assign each class of tags to a
different parent tag.
ParentTagname = "EXP_FLOAT_OP"
ParentTagname = "EXP_FLOAT_LIN"
ParentTagname = "EXP_FLOAT_STEP"
ParentTagname = "EXP_FLOAT_PUT"
ParentTagname = "EXP_ENUM_MODE"
ParentTagname = "EXP_INT"
The Active flag cannot be inherited from a parent tag, so it should be placed in each rule.
Active = "X"
You may choose to specify Quantum in each rule; otherwise PHD sometimes calculates
its own values, which you may not want.
Quantum = n

MODE
The default Tag Sync rule sets the engineering units of MODE to the same units as PV. If
needed, create a rule to set the units of MODE to "nothing":
TagUnits = ""
Note: The TagUnits rule text is not required for synchronization of Experion systems
running software release R310 and greater, because for those versions the Experion
Server sends TagSync the appropriate units value for .OP and .MODE tags.
In the following example, the user created the rule MODE_RULE. The Variable Name is
PARAMETER and the Regular Expression is MODE.

124 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

ATTENTION
After you add rules, use the Arrow button to move DEFAULT_RULE to the
bottom of the Configured Rules list.

OP
• The default Tag Sync rule sets the engineering units of OP to the same units as PV.
If needed, create a rule to set the units of OP to "%":
TagUnits = %

Note: The TagUnits rule text is not required for synchronization of Experion
systems running software release R310 and greater, because the Experion Server
sends TagSync the appropriate units value for .OP and .MODE tags.
• You may choose to put information about parameter type in the tag description.
Description = Description + "Output"
• You may choose to adjust the ranges on OP tags to always be -10 to 110.
HighExtreme = 110

Uniformance - PHD/Experion Link Installation and Configuration Guide • 125

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

LowExtreme = -10

ATTENTION
After you add rules, use the Arrow button to move DEFAULT_RULE to the
bottom of the Configured Rules list.

PV
PHD uses the standard high and low range of the Experion point during Tag
Synchronization. The Experion extended range is not returned by the Experion server to
the PHD Tag Synchronization. If the value for an Experion point is above/below the
standard range in Experion, but within the extended range in Experion, then the value is
good in Experion but clamped in PHD (because it is out of range). Values sent to PHD
that are outside the range are not stored.
You can create/adjust a Tag Sync rule to increase the range of the PHD tags. The
following example increases the PHD tag range by 10%.

126 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Dim Adjustment As Decimal

Adjustment = (HighExtreme.Value - LowExtreme.Value) * 0.1
HighExtreme = HighExtreme.Value + Adjustment
LowExtreme = LowExtreme.Value - Adjustment
Note: The Dim operator (Dim VariableName As DataType) creates a variable named
Adjustment. In this example, it can be either Decimal or Double.
Following is an example for comparing the limits:
If HighExtreme.Value > 32767 Then
HighExtreme = 32767
End If
If LowExtreme.Value < -32767 Then
LowExtreme = -32767
End If

Uniformance - PHD/Experion Link Installation and Configuration Guide • 127

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Ordinals (EN)
By default, TagSync sets the PHD tag definition of ordinals to EN/VALUE, as follows,
so PHD historizes the ordinal values:
SourceTagType = EN
SourceTagAttribute = VALUE

If you want PHD to historize the enumeration strings instead of the ordinal values, create
a rule to set the tag definitions to EN/STRING.
If (SourceTagType = "EN") Then
SourceTagAttrib = "STRING"
End If
REFERENCE: For additional information on enumerations, refer to section 8.7 "Collect
and Access Enumeration Data".
Tag name considerations
The default TagSync rule assigns the PHD tagname to be the following:
• For a controller point – Tagname.FunctionBlock.Parameter (for example
TIC100.PIDA.SP)
• For a SCADA point – Tagname.Parameter (for example TIC100.PV)
If the length of the Experion source "tagname.parameter" is greater than 32 characters,
then Tag Sync will set the tagname of the PHD tag to EXPERION_xxxx, where xxxx is a
sequentially increasing number.
Tips for regular expressions
• Regular expressions are case sensitive. Tag Sync does not convert regular
expressions to uppercase - this can cause issues with the syntax for POINT and
PARAMETER variables. To address this, you may choose to modify regular
expressions as follows:
(?i) - Ignore Case

To ignore case, prefix the string with (?i)

Examples:

(?i)OP Will match any string that contains OP in any case

(OP,op,Op,oP,xop,ops)
(?i)SP Will match any string that contains SP in any case

128 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

• By default, regular expressions look for a match anywhere in the string. For
example, MODE will match MODE and MODESTR. To address this, you may find
the following options useful:
^ - Match from the start of the string
To force the match to the start of the string, place ^ at the start of the expression.
Examples:

^OP Will match any string that starts with OP in uppercase (OP,
OPS).
(?i)^OP Will match any string that starts with OP in any case.

$ - Match to the end of the string

To force the match to the end of the string, place $ at the end of the expression.
Examples:

OP$ Will match any string that that ends with OP in uppercase (OP,
XOP).
(?i)OP$ Will match any string that ends with OP in any case.
(?i)^OP$ Will match any string that starts or ends with OP in any case (OP,
op, Op, oP, XOP, xop, xoP).

Tag Sync variables

Each Tag Sync rule executes as a method of a tag definition. Within this tag definition,
there are a set of member variables (properties) and methods that are common to all
source system types. There is also a set of member variables that are specific to
Experion. You can use rules to configure common and Experion-specific variables.
You can base rule execution on any of the variables shown in bold.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 129

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Pre-initialized common member variables

Tag Sync ALWAYS sets these variables to match the incoming configuration. This helps
minimize the configuration that you need to place in the rules.

Member Variable Name Description of incoming Comment

configuration from Experion system
SourceSystem “EXPERION”
MachineName <Experion Server Name>
PointName <Experion Point>
Parameter <Experion Parameter>
TimeStamp <Time of definition change on Experion>
Description <Experion point description>
Asset <Experion Asset>
Item <Experion Item>
TagUnits <Units for Experion Point.Parameter>
LowExteme <Experion Minimum Range>
HighExtreme <Experion Maximum Range>
ScanFrequency <Experion History Interval> In seconds if possible
ScanTimeStampUnit “ms” If ScanFrequency is in ms
SourceTagType “I4” Integer datatype
“L8” Long Integer datatype
“US” String datatype
“F4” Floating Point datatype
“EN” Enumeration datatype

SourceTagAttrib “STRING” String datatype

"VALUE” All other datatypes

ATTENTION
You should never manually overwrite the tag configuration of these attributes
through the PHD Tag Configuration form, unless you configured them to be
inherited from a Parent Tag, because the next Tag Sync will overwrite the
value again. Inheritance takes precedence over tag sync, so you can
manually overwrite inherited values through the Tag Configuration form.

130 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Experion-specific member variables

All of the incoming data from the Experion server can be used in a rule – this includes
common member variables and the following Experion-specific member variables that
provide additional information for an Experion tag.
All of the Experion-specific member variables are strings, but can be used as double-
precision numbers or integers in a rule if needed (with the exception of ExpDescription,
EntityType, and DisplayType). See the PV example in the "Rule examples for Experion"
in this section.

Member Variable Name Description of incoming Comment

configuration from Experion system
ExpDescription <Experion point description>
Range_Lo <Experion low range for This is parameter
point.parameter> specific.
Range_Hi <Experion high range for the This is parameter
point.parameter. specific.
HistoryInterval <Experion history interval of the This is parameter
point.parameter specified in specific.
milliseconds>
ExtendedHighRange <Experion extended low range for the This is parameter
point.parameter> specific. ESVT Only
ExtendedLowRange <Experion extended high range for the This is parameter
point.parameter> specific. ESVT Only
EntityType <Experion entity type for the point> ESVT Only
DisplayType <Experion display type for the point> ESVT Only

To view synchronized tags in staging table before sending tag definitions to PHD
By default, Tag Sync does not automatically acknowledge the synchronized tag
definitions in its staging table. This allows the user to view the tags in the staging table
before sending them to PHD.
The staging table is viewed through the PHD Tag Synchronization Acknowledgement
form.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 131

6 Configure PHD-Experion Integration
6.5 In PHD Configuration Tool - Configure Tag Synchronization Rules

Initially, you may want to leave automatic acknowledgement off, so you can view tag
configuration in the staging table. Later, you may choose to turn on automatic
acknowledgement, if it is wanted.
When you start the Tag Sync service, the automatic acknowledgement immediately
applies Tag Sync tag definitions to the PHD tag table.
Possible reasons to leave automatic acknowledgement off are as follows:
• To ensure that Tag Sync does not automatically overwrite existing PHD tag
configuration until you are comfortable that the rules execute as expected.
• To allow you to validate that the Tag Sync tag definitions will not overwrite
important data in the existing tag definitions.
• To allow you to be aware of all changes that Tag Sync will make to existing tags.
After initial tag synchronization, you may add the following line to your rules to turn on
automatic acknowledgement, if it is wanted:
Acknowledge()

REFERENCE
For details on Tag Synchronization rules, refer to the section, Configuring PHD Tag
Synchronization Rules in the PHD User Guide (pim0201).

For details on PHD tag configuration fields, refer to the section 8.6, Tag Field Usage
for PHD Tags on PHD Experion Link.

132 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 6 Configure PHD-Experion Integration
6.6 Configure PHD Point Server

6.6 Configure PHD Point Server

On Experion Servers - Configure Experion to communicate with PHD Point Server
If the optional PHD Point Server has been installed on the PHD Server to support
Experion trends, perform the following steps to configure the Experion Server to
communicate to the PHD Point Server.

Step Action
1 Start the Station application on an Experion client PC or on the Experion
Server. Log on to Station as a user with administrator (MNGR) access.
2 In the Station application, choose Configure > System Hardware > PHD
Server.

RESULT: The Configuration tab of the PHD Server Configuration display

appears.
3 (Optional) In the Alias box, enter an alias for the PHD system interface.
The default is PHD.

TIP: When you build an Experion trend, you will select this Alias as the Point
Name and then enter the PHD tagname as the Parameter. The result is
shown below:

4 Click the checkbox This server connects to the PHD Point Server.
5 In the Network Name box, type the hostname of the PHD Server node where
the PHD Point Server will run.

You cannot use an IP address.

Press Enter before leaving the port.

6 (Optional) In the Assignable Asset box, if an Asset has been configured to
represent the PHD Server, select it from the drop down list.

Press Enter before leaving the port.

TIP: To configure assets in Experion, from the Experion Configuration

Studio, select the System name, then select Configure Assets for this

Uniformance - PHD/Experion Link Installation and Configuration Guide • 133

6 Configure PHD-Experion Integration
6.6 Configure PHD Point Server

Step Action
system.

On PHD Server - Configure registry settings, as needed, for PHD Point Server
When started, the PHD Point Server reads a set of configurable registry settings on the
PHD Server node.
Certain registry settings disable/enable specific PHD Point Server functionality. Other
registry settings may be used to tune the PHD Point Server for the purpose of reducing
CPU usage and improving trend callup times.
You may change the registry settings as needed for your site.
The registry settings include the following:
• AllowTagSyncTags - determines whether to allow synchronized PHD tags
(tags that are in both PHD and Experion history) to be retrieved on Experion trends,
or only allow non-synchronized PHD tags to be retrieved (tags that are only in PHD
history). This bypasses data security and provides read access to all PHD data.
• HistoryTimeout - sets the timeout for PHD history requests from PHD Point
Server.
• MinConfidence - defines the minimum confidence value required for data to
be plotted on Experion trends.
• AverageRetrievalSettings and SnapshotRetrievalSettings -
defines the PHD retrieval attributes – maps the Experion history data requests to
PHD data requests.
For detailed descriptions of the registry settings, refer to Appendix A, PHD Point Server
Registry Settings.

134 • Uniformance - PHD/Experion Link Installation and Configuration Guide

This page is intentionally left blank

Uniformance - PHD Experion Link Configuration Guide • 136

 7. Startup PHD-Experion Integration Components
7.1 On PHD Server - Start and Monitor PHD Experion Link
In a running PHD system, perform the following steps to start the PHD Experion Link.
Note: If the PHD system is not running, a startup of the PHD system (PHDCTL Start
or PHDCTL Start Cold) causes the Start_Interfaces.Dat file to be executed
automatically, which starts all non-running interfaces.

Step Action
1 Enter the following command to start the PHD Experion Link:

PHDMAN START INT <linkname>

2 Enter the following command to view the PHD Experion Link status display
with continuous updating:

PHDMAN MON INT <linkname>

3 The status should be ACTIVE ACTIVE.

If there are startup problems, view the output file generated by the Link:

C:\ProgramData\Honeywell\Uniformance\Log Files \LINK<linkname>.OUT.

The Program Data folder must be made visible.

For additional information, see section 9.1, Troubleshoot the PHD Experion
Link.

Next Step
To implement PHD data collection, the next step is to add PHD tags to the PHD
Experion Link, either manually or through the automated Tag Synchronization service.
Before starting Tag Synchronization, you may choose to manually configure a test tag to
confirm successful data collection for that one tag. See section 8.2, Manually Configure
a New PHD Tag.

7.2 Start and Monitor Tag Synchronization

Before you start Tag Synchronization

Check Machines registry parameter

Uniformance - PHD/Experion Link Installation and Configuration Guide • 137

7 Startup PHD-Experion Integration Components
7.2 Start and Monitor Tag Synchronization

Ensure that the Experion\ Machines registry parameter has been populated with the
Experion Server name(s) from the PHD Links Configuration form(s).
If the key has not been created or populated, run RDISetup and execute its Save
RDI/Link Configuration command. See Appendix A for registry information.

Change DEBUG registry parameter (optional)

For the initial Tag Synchronization, it may be useful to change the value of the DEBUG
registry parameter of the Tag Synchronization service to 2, to increase the amount of
detail it outputs to its log.
See Appendix A for registry information.

Change deleted tags collector name (optional)

If a synchronized tag has its point.parameter removed from history on Experion, either
explicitly or through the deletion of the Experion point, Tag Synchronization places the
tag on the NONE collector. This can be overridden if you specify a different Collector
Name for the “DELETED TAG COLLECTOR” attribute.
To specify a different Collector Name, open the PHD Configuration Tool, select the
Plant Reference Model application, open the Application Attribute Configuration form,
go to the “TAGSYNC APPLICATION” attribute type, add the "DELETED TAG
COLLECTOR” attribute (it is not present, by default), and then change the attribute.

REFERENCE
For details to configure the Tag Synchronization attribute, refer to the
following section in the Process History Database User Guide (pim0201):
• “Application Attributes”

138 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.2 Start and Monitor Tag Synchronization

Disable "Check for publisher's certificate revocation" (optional)

With Uniformance R210 and greater, all Uniformance PHD executables and DLLs are
signed with a digital certificate. An integrity check is executed each time any of the
applications are started. Part of the integrity check is the verification of the digital
certificate, which may involve an attempt to connect to the internet.
If no connection to the internet exists, or if the connection to the internet is extremely
slow, the verification of the digital certificate may not complete in the time frame
required by the service control manager. In such a case, the Uniformance Tag Sync
service fails to start and the message notification indicates that the service failed to
respond in a timely fashion.
To prevent/resolve this problem do the following:

Step Action
1 Using the account that the service is going to be running as, launch the
Internet Options application in Control Panel.
2 Within the application, navigate to the Advanced tab.

Under Security, disable the "Check for publisher's certificate revocation"

(remove checkmark from checkbox).

By default, the Uniformance Tag Synchronization Service runs under the Network
Service. Follow the steps to disable the certificates for Network Service.
Step Action
1 Double-click Uniformance System Console.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 139

7 Startup PHD-Experion Integration Components
7.2 Start and Monitor Tag Synchronization

Step Action

2 Right-click localhost and then choose All Tasks > Disable Certificate
Checking.
The Select User Accounts dialog box appears.

140 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.2 Start and Monitor Tag Synchronization

Step Action

3 In the User Account list, select the Network Service check box.

4 Click Disable.
This disables the certificates for Network Service. In the Current State list,
the Network Service state changes to disabled.

Procedure to start Tag Synchronization and monitor its progress

Step Action
1 From the Microsoft Services window on the PHD Server, start the
Uniformance Tag Sync service.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 141

7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

Step Action
2 To verify that the Tag Synchronization service successfully connected to the
Experion Server, go to the Experion Server's Station application and view the
PHD Server status display :
In Station, choose View>System Status>PHD Server.

The Tag Synchronization Status should become SYNCHRONIZING and the

LED should be green.
3 Every 60 seconds, Uniformance Tag Synchronization requests definitions
from the Experion Server. The statistics indicate the progress.

When the synchronization completes, the Status will be SYCHRONIZED.

For definitions of the statistics, see section 9.3, To view Tag Synchronization
Status and Tuning display.

For guidelines on troubleshooting Tag Synchronization, see section 9.3,

Troubleshooting Tag Synchronization.

7.3 In PHD Configuration Tool – Acknowledge Changes

in Tag Synchronization Staging Table (Optional)
Overview
If there are configuration errors, or if a Tag Sync Rule has been configured to require
explicit user acknowledge, then you must use the Tag Synchronization Acknowledgment
form to take action on tag definitions that Tag Sync created in the staging table. The
form displays tags that are either unacknowledged or incorrectly configured.

To view/take action on tags in the staging table

Step Action
1 On the Home tab of the ribbon bar, choose Applications > Tag
Synchronization Acknowledgement from the PHD Configuration Menu.
2 Either enter a partial/complete tag name or click Advanced Search link to
filter the list of displayed tags.

142 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

Step Action

Tip: • To view tags with a specific Tag Sync status, or all but a specific status,
use the Tag Synchronization Status field.
• To retrieve all tags in the staging table, leave all the fields blank.

• To view a single tag, enter its Tag Name.

Tips for entering a Query:

• Use an asterisk (*) to indicate a wildcard search.

• To search on the underscore (_) character, enclose it in square brackets

([ ]). For example, searching for EXPERION[_]* (with square brackets around the
underscore) will return results for EXPERION_. An underscore is interpreted in the
database as a single-wildcard character, so querying on EXPERION* and
EXPERION_* will return the same results. This also applies to the percent (%)
character, which is a multi-character wildcard in the database.
• To retrieve records that are NULL or not NULL, select the operator 'Value is NULL'
or 'Value is not NULL'.
3 Click OK. The query returns the tags that match the specified criteria.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 143

7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

Step Action

4 Refer to Table 4 for descriptions of the fields on the Tag Synchronization

Acknowledgement form.

Depending on the message in the Status field, take the appropriate action, as
described in Table 5.

144 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

Fields
The following fields either exist only in the Tag Synchronization Acknowledge form or
have a different meaning than in the Tag Configuration form.
All fields on the form are read only.

Table 4 – Fields on Tag Sync Acknowledgment form

Field Description

Tag Name The PHD tagname. It is valid for the Tag Name field to be
empty. If it is empty, the Tag Sync process assigns a unique
tagname.

The default is <source system>_xxxx.

Where: xxxx is a sequentially increasing number.

Example: EXPERION_1111

Status The status of the operation. This indicates if the definition is

valid or if there was a problem with the definition of the PHD
tag.

In general, the user can use Discard or Reprocess for any

status.

For a status of Tag Valid, the user can also Acknowledge

the tag to have it created/updated in PHD.

Existing Tag Name Displays the name of the existing PHD tag in the database
that this definition will overwrite.

Click View Tag to display the definition of the existing tag.

Action The action that Tag Sync undertook for this tag. Displayed
values are UPDATE, CREATE, DELETE and RENAME.

Note: For descriptions of the fields that are the same as those in the Tag Configuration
form, refer to section 8.6, Tag Field Usage for PHD Tags on PHD Experion Link in this
guide.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 145

7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

Statuses and actions

Depending on the message in the Status field, take the appropriate action, as described in
the following table.

Table 5 – Statuses on Tag Sync Acknowledgment Form

Status Description/ACTION
An exception An unhandled exception occurred in the execution of the rule.
has occurred
during the ACTION: Review log file to determine problem with rule.
processing of
the rule for
the tag

Database There is a problem with the configuration data in SQLServer.

failure
ACTION: Review log file and contact Honeywell TAC.
Datatype does The datatype of the existing tag does not match the datatype
not match for the Tag Synchronization definition.
existing tag
ACTION: The user should do either of the following:
• Modify rule so that datatype matches existing tag, or

• Manually change Source Tag Type and/or Source Tag

Attribute of existing tag to match datatype in Tag
Synchronization. Doing this will result in existing data for the
tag being lost (unreadable).
Invalid Tag This error should not appear on the acknowledgement form. It
implies that an unknown error occurred in the processing of
the tag.

ACTION: Review log file and contact Honeywell TAC.

146 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

Status Description/ACTION
Multiple There are multiple tags in PHD that match the tag definition
synchronizati and have Tag Synchronization enabled.
on tag exist
ACTION: You need to modify the tag database. This may
mean that you need to delete one of the tags or change one of
the tags to be non-sync enabled (only if they are different tag
types, such as a Collection tag and a Manual Input tag for Put
Download).
Non- A tag that is not synchronized already exists for PHD.
synchronized
tag exists ACTION: Modify the existing tag so that it is synchronized.

Tag This is a temporary condition that should not remain for a long
acknowledged period of time. This occurs after a tag has been acknowledged
through the form or implicitly through the execution of a rule.
Tag discarded The tag has been discarded either through the
acknowledgement form or implicitly through a rule.
Tag The tag is scheduled to be reprocessed. This is a temporary
reprocessing condition.
Tag source The tag source information specified is not valid for the source
information system. For Experion, this means that either the Point or
invalid Parameter is unspecified.

ACTION: Modify the Point or Parameter in the rule.

Tag Valid The tag is confirmed to be valid.

ACTION: Click Acknowledge Selected to create/update the

tag.

Note: Additional statuses may display that are not listed here – those statuses
correspond to the same errors that are seen on the Tag Configuration form (for
example, Invalid Parent Tag Name specified).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 147

7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

To take action
You must use the Acknowledge Selected, Acknowledge All, Discard Selected, or
Reprocess Selected buttons to take an action. The following table describes these
buttons.

Table 6 – Buttons on Tag Sync Acknowledgment form

Button Description

Acknowledge Selected Select one or more staging Tags from the Current list of
Staging Tag records.

If the displayed tag has a valid definition, the Acknowledge

button will be enabled.

Click Acknowledge to cause Tag Sync to either update the

existing tag definition in the database or create the new tag.

After acknowledgement, the form shows the next tag in the

staging table.

Acknowledge Select one or more staging Tags from the Current list of
All Staging Tag records.

If any of the queried tags have a valid definition, the

Acknowledge All button will be enabled.

Click this button to acknowledge all of the queried tag records

that have Acknowledge enabled.

Discard Selected Select one or more staging Tags from the Current list of
Staging Tag records.

Click Discard if the tag is not to be saved to the database.

The tag will remain in the staging table.

Generally, this action is used if the tag is available in Experion

history, but is of no interest to PHD. After you click Discard,
Tag Sync will still be aware of the definition, so it will not
continually identify the tag as a missing definition from the
source system.

148 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.3 In PHD Configuration Tool – Acknowledge Changes in Tag Synchronization Staging Table
(Optional)

Button Description

Reprocess Selected Select one or more staging Tags from the Current list of
Staging Tag records.

Click Reprocess if you want Tag Sync to reprocess the tag.

Generally, this action is used if there was an error in the tag

definition and you have modified either the rule or the parent
tag definition to resolve the problem.

To view Tag Sync log

The Tag Sync log shows the tags being received by PHD.
To view the log go to:
C:\ProgramData\Honeywell\Uniformance\Log Files\UniformanceTagSync.log.
The Program Data folder must be made visible.
Use the InformationLevel registry parameter to increase the level of detail in the log, if
needed to troubleshoot Tag Sync issues (see Appendix A).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 149

7 Startup PHD-Experion Integration Components
7.4 Tasks to Perform After Initial Tag Synchronization

7.4 Tasks to Perform After Initial Tag Synchronization

Complete PHD engineering unit configuration
If the source unit of an Experion tag is not defined in the PHD Engineering Unit
configuration form, then Tag Synchronization creates a record for the source unit in the
PHD Engineering Unit configuration form under the TAGSYNC Unit Type.
For each Source Unit in the TAGSYNC Unit Type, you should either move the unit to an
existing Unit Type and configure its’ conversion factors or create a new Tag Synch Unit
Mapping.
Perform the following steps to complete the unit configuration.

Step Action
1 From the Main Menu of the PHD Configuration Tool, select System Data >
Engineering Units.

NOTE: Tag Synchronization populates units in the TAGSYNC Unit Type,

based on values received from Experion that do not match existing PHD
Units.

150 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.4 Tasks to Perform After Initial Tag Synchronization

Step Action

To map the Source Unit to existing PHD Unit

2 First select the TAGSYNC Unit Type from the Current list of Engineering Unit
Type records and then choose an individual Engineering Unit. Next, choose
Tag Sync Unit Mapping from the menu. The Source Unit should be
populated based on the unit you selected. Choose a corresponding PHD Unit
from the drop down list of existing Engineering units. Click Save and then
click Close.
For example:

Source Unit PHD Unit

Deg C DEGC

Deg F DEGF

Barrels BBL

Cubic Meters M3

When finished, skip to step 4.

If the PHD unit you need does not exist in the drop down list, and then create
a new PHD Unit as described in the following steps.

To move the Source Unit to an Existing Unit Type

3 First select the TAGSYNC unit type from the Current list of Engineering Unit
Type records and then choose an individual Engineering Unit. Next, choose
Move Unit from the menu.
Select the Source Unit. Select the Unit Type you wish to move the Source
Unit to. Click Move and then click Close.

Note: Close the form and reopen it to refresh the underlying data cache.
4 Select the appropriate Unit Type master record.

Select the Experion source unit. Enter the Pre-Add factor, the Multiplication
factor and the Post-Add factor to define how this unit relates to the base unit
of the Unit Type.

REFERENCE: For details on how to create new PHD engineering units, refer
to the Process History Database User Guide (pim0201).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 151

7 Startup PHD-Experion Integration Components
7.4 Tasks to Perform After Initial Tag Synchronization

Step Action
5 When complete, select Update PHD.

152 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.4 Tasks to Perform After Initial Tag Synchronization

Enable/Disable continuous Automatic Tag Synchronization (Optional)

It may be undesirable to have Tag Synchronization continuously overwrite PHD tag
definitions. If you want continuous automatic Tag Synchronization, then enable the
Automatic Synchronization flag. Disable the flag on those tags for which you do not
want continuous synchronization.

Set DEBUG registry parameter back to 1

If you modified the InformationLevel parameter, then after successful Tag
Synchronization, return the parameter value to 1, which outputs the least amount of
information to the log.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 153

7 Startup PHD-Experion Integration Components
7.5 On PHD Server – Start PHD Point Server Service

Set Tag Synchronization service to Automatic startup

Finally, at some time, you may want to set the Uniformance Tag Sync service to startup
automatically upon reboot of the PHD Server.

Step Action
1 On the PHD Server, go to the Microsoft Services window:
Control Panel> Administrative Tools> Services,
2 Right-click Uniformance Tag Sync service and choose Properties.
3 Change the Startup type to Automatic and click OK.

7.5 On PHD Server – Start PHD Point Server Service

Start and stop the PHD Point Server through the Microsoft Services window.

Step Action
1 On the PHD Server, go to the Services window:
Control Panel> Administrative Tools> Services,
2 Right-click and Start the Experion PKS PHD Point Server service.
3 (Optional) If you want the PHD Point Server to start automatically upon
reboot, right click Experion PKS PHD Point Server and choose Properties.

Change the Startup type to Automatic and click OK.

4 To verify the connection to the Experion Server, go to the Experion Server's
Station application and view the PHD Point Server Status (see section 7.6,
On Experion Server – View PHD Point Server Status).

7.6 On Experion Server – View PHD Point Server Status

Step Action
1 Logon to Station as a user with mngr security level. In Station, choose
Configure>System Hardware>PHD Server.
2 Click the Status tab to check if the PHD Point Server is communicating with
the Experion Server.

154 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 7 Startup PHD-Experion Integration Components
7.6 On Experion Server – View PHD Point Server Status

Step Action
3 Both LEDs for the PHD Point Server Network Link should be green (see
Figure 12):
• Check that the Link Status LED is OK and green.

• Check that the Data Status LED is OK and green.

Figure 12 – PHD Point Server Status Display

Uniformance - PHD/Experion Link Installation and Configuration Guide • 155

7 Startup PHD-Experion Integration Components
7.7 On Experion Server – View PHD Point Server Trend Data

7.7 On Experion Server – View PHD Point Server Trend

Data
To check the operation of the PHD Point Server, create an Experion Trend that contains a
non-synchronized PHD tag. Note: The PHD tag must exist on the PHD Server.
Perform the following steps to configure an Experion Trend.

Step Action
1 On an Experion node, go to the Experion Configuration Explorer of
Configuration Studio, click Trends and Groups, and then click the
Configure Trends task.
2 For the Point ID, enter the PHD Point Server's Alias and press Enter.
3 Change the Display parameter to display as an Alphanumeric.
4 For the Parameter, enter the tag name of a PHD tag.

Note: The PHD tag may need to be a non-synchronized PHD tag (not in
Experion history), depending on how the PHD Point Server is configured.
(For details, see section 10.3, PHD Point Server Registry Settings,
AllowTagSyncTags.)

REFERENCE
For details on configuring Experion trends, refer to the Experion Server and
Client Configuration Guide in the Experion book set.

156 • Uniformance - PHD/Experion Link Installation and Configuration Guide

This page is intentionally left blank

Uniformance - PHD/Experion Link Installation and Configuration Guide • 158

 8. Configure PHD Tags on PHD Experion Link
8.1 General PHD Tag Configuration Guidelines
ATTENTION
It is possible to manually build tags in PHD on the PHD Experion Link and/or
use automatic Tag Synchronization.

You must manually build tags to historize in PHD any point parameters that
are not assigned to Experion history. Honeywell supports this functionality for
character (string) parameters only.

All numeric and enumerated (ordinal) data to be collected by the PHD

Experion Link should be assigned to Experion history and automatically Tag
Synchronized.

ATTENTION
Tag Synchronization only examines points with Experion history assignment.

8.2 Manually Configure a New PHD Tag

Before you begin
Read section 8.1, General PHD Tag Configuration Guidelines. Note: Instead of
manually creating PHD tags for numeric or enumerated parameters, you should assign
the parameters to Experion history and Tag Synchronize them to PHD.

To manually configure a new PHD tag

Perform the following steps to manually configure a PHD tag to collect Experion strings.

Step Action
1 In the PHD Configuration Tool, open the Tag Configuration form.
2 Configure a collected tag. For minimum required fields to collect a string, see
below. For descriptions of the tag fields, see section 8.6, Tag Field Usage for
PHD Tags on PHD Experion Link.
3 After entering the required fields, click Send Changes to PHD.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 159

8 Configure PHD Tags on PHD Experion Link
8.3 Deleting an Experion point or removing it from Experion history

Step Action
4 From a command prompt on the PHD Server where the PHD Experion Link is
running, enter the following command.

PHDMAN MON QUE <phdtagname>

5 Verify that values are coming into the tag's data queue.

Example PHD tag configuration

Minimum PHD tag fields to collect a string parameter from Experion are as follows:
Tag Name MYPHDTAG
Active X
Collection X
Source System Type EXPERION
Source Tag Type AS
Source Tag Attribute VALUE40
Scan Frequency 60
PHD Link Name LSTB-EXP
PHD Link Point Name 11_AC12
PHD Link Parameter Name DESC

8.3 Deleting an Experion point or removing it from

Experion history
At some time after initial Tag Synchronization and recovery of the Experion history into
PHD, you may want to remove an Experion point from Experion history or delete the
point from the Experion system.
Deleted Experion points are implicitly acknowledged by Tag Sync.
Before deleting an Experion point or removing it from Experion history, consider
whether you should disable Automatic Tag Synchronization on the PHD tag first:
• If Automatic Tag Synchronization is Enabled on the PHD tag at the time you disable
history collection on the Experion point:
− PHD stops collecting data for the tag, but still returns requested data for the tag.
− Data Store is disabled on the PHD tag,
− Collector Name is set to NONE, and
− Link Name is set to NONE.
160 • Uniformance - PHD/Experion Link Installation and Configuration Guide
 8 Configure PHD Tags on PHD Experion Link
8.4 Disable Tag Synchronization for a PHD Tag

− If the Experion point is re-added to Experion history, Data Store is enabled, the
Collector Name is set by the Rule, and the Link Name is set to the correct link.
• If Automatic Tag Synchronization is Disabled on the PHD tag at the time history
collection is disabled on the Experion point:
− PHD continues to collect data for the tag. Additional load is placed on the
Experion Server, because the data for the tag is not cached in Experion history.
− No tag configuration changes are made to the PHD tag.
− If the Experion point is re-added to Experion history, Tag Sync reports an error
that a non-synchronized PHD tag was detected during the PHD matching of the
Experion point.parameter. Tag Sync does not change the configuration of the
existing PHD tag. At this time, the user could re-enable Automatic Tag
Synchronization on the PHD tag, and Tag Sync would start maintaining the
PHD tag configuration.

ATTENTION
If you want to remove a point.parameter from Experion history, Honeywell
recommends that you disable Automatic Tag Synchronization on the PHD tag
before removing the Experion point’s history assignment from Experion.

8.4 Disable Tag Synchronization for a PHD Tag

The default Tag Synchronization rule/parent tag enables the “Automatic Tag
Synchronization” flag - however, it may be undesirable for Tag Synchronization to
continuously overwrite the PHD tag definitions.
This flag can be disabled to stop continuous Tag Synchronization on a per tag basis, if
wanted; and then any changes to the point definition on the Experion system will not be
reflected in PHD.
Perform the following steps to disable continuous Tag Synchronization of a PHD tag.

Step Action
1 In the PHD Configuration Tool, open the Tag Configuration form.
2 Enter the tag name of interest in the Search entry box. Click Go.
3 On the Tag Configuration form for the tag of interest, disable (remove
checkmark from) the Auto Synchronization flag.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 161

8 Configure PHD Tags on PHD Experion Link
8.5 Update or Migrate Existing PHD Tags

Step Action
4 Save the record.
5 Click Send Changes to PHD.

8.5 Update or Migrate Existing PHD Tags

If PHD tags are already built, but are not yet assigned to a PHD Experion Link,
configure the following fields in the Tag Configuration form and then click Send
Changes to PHD:
- PHD Link Name - PHD Link Point Name - PHD Link Parameter Name
For example, if you performed Tag Synchronization before configuring the PHD
Experion Link and running RDISetup, Tag Synchronization will not have assigned the
synchronized tags to a PHD Experion Link. You can manually assign them through the
above fields.
If existing PHD tags are currently assigned to an LxS RDI, Experion/PlantScape
RDI, or OPC RDI, and you want to reassign them to a PHD Experion Link, the
following steps must be undertaken:
• Configure PHD Experion Link(s)
• Validate/modify Tag Source Configuration
• Modify Tag Configuration
• Configure Shadow Server Peer RDI, if applicable

REFERENCE
Contact Honeywell for more information on how to migrate PHD tags from
existing RDIs to the PHD Experion Link, including enabling Tag
Synchronization.

162 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 8 Configure PHD Tags on PHD Experion Link
8.6 Tag Field Usage for PHD Tags on PHD Experion Link

8.6 Tag Field Usage for PHD Tags on PHD Experion Link
ATTENTION
This section does not repeat the complete definition of every PHD tag field –
it only describes how Tag Synchronization affects each field and how the field
should be handled to support Experion tags that are collected by a PHD
Experion Link.

For additional data entry guidelines, for example, if you want to create tags
manually, also refer to the PHD User Guide (pim020s), section "Tag
Configuration Form."

Tag Name
If using Tag Synchronization, the default Tag Synchronization rule assigns the tagname
to be the Experion “point.parameter”. If the Experion point.parameter length is greater
than 32 characters, and you have not created a rule to compensate for it, then the PHD
tagname will be EXPERION_xxxx, where xxxx is a sequentially increasing number.

Active
This flag must be enabled to make the tag usable. The default Tag Synchronization rule
enables this flag. An inactive tag does not collect or store data; and references to the tag
prompt a message indicating the tagname is unknown. When you need to take a PHD tag
out of service, disable the Active flag.

Parent Tag Name

The default Tag Synchronization rule assigns the parent tag to be EXP_PARENT.
If Tag Synchronization is to be used to maintain the tags for the PHD Experion Link,
then use of the EXP_PARENT parent tag should be sufficient.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 163

8 Configure PHD Tags on PHD Experion Link
8.6 Tag Field Usage for PHD Tags on PHD Experion Link

Tag Units
Tag Synchronization checks to see if the “Source Unit” from the Experion Server is
defined in PHD (Engineering Unit Configuration form in the Plant Reference Model). If
the unit is defined, Tag Synchronization uses this unit for the newly created tag. If the
unit is not defined, it checks the Tag Synchronization Unit Cross Reference form. Tag
Synchronization populates the form based on “Source Units” it receives from the
Experion Server that do not match existing “PHD Units.” These auto-populated records
will have a null (blank) PHD Unit. For records that have a null PHD Unit, you should
take action to complete the configuration (see 7.4, Tasks to Perform After Initial Tag
Synchronization).

Enable Collection
This flag enables continuous data collection by the PHD Experion Link defined in the
PHD Link Name field.
The default Tag Synchronization Rule/Parent Tag enables the Collection flag.

Data Store
This flag enables continuous storage of incoming data by the PHD Server to the PHD
archive files. If this field is blank, any tag data collected is retained only in PHD's
memory queues and will not be stored in archive files on disk. As a result, if unexpected
system outages occur, this data is lost. In most circumstances, setting the Data Store flag
is recommended.
The default Tag Synchronization Rule/Parent Tag enables the Data Store flag.
If the Experion Server notifies Tag Synchronization of an Experion history point
deletion, then PHD disables the Data Store enable flag for any PHD tag(s) associated
with that Experion point.

Digital Enumeration
This flag enables additional handling of this tag's digital value by the PHD Server - the
tag will be able to return either Ordinal integer values or Enumeration String values upon
client request. The mapping of ordinals to strings is specified through the Digital
Enumeration List Name field.

Automatic Tag Synchronization

The default Tag Synchronization rule/parent tag enables the “Automatic Tag
Synchronization” flag; however, it may not be desirable for Tag Synchronization to
continuously overwrite the PHD tag definitions.

164 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 8 Configure PHD Tags on PHD Experion Link
8.6 Tag Field Usage for PHD Tags on PHD Experion Link

If needed, this flag can be disabled to stop continuous Tag Synchronization for the tag;
and then any changes to the history point definition on the Experion system will not be
reflected in PHD.
A PHD tag must be Active and have Automatic Synchronization enabled before Tag
Synchronization can take place.
If you enable Automatic Tag Synchronization, Honeywell recommends that before
removing an Experion point’s history assignment from Experion, you disable Automatic
Tag Synchronization on the associated PHD tag(s).

Source Tag Specification

Source Tag Index
Not Used.

Source System Type

OPC

Source Tag Type

This field defines the data type requested from or downloaded to the source system. The
following table shows the PHD Source Tag Type that is required to collect or download
data types supported by the Experion Server, and how PHD tags store the value in PHD.

Source Tag Source Tag PHD Description

Type Attribute Data Type

F4 VALUE F Four byte float

D8 VALUE D Eight byte float (double-precision)

I4 VALUE I Four byte integer

L8 VALUE L Eight byte integer (long)

EN VALUE I Four byte integer

(Enumeration Ordinal)
(see NOTE2)
EN STRING U 80 character string
(Enumeration String)

AS VALUE## C ## is a number from 10 to 80 that

represents maximum number of

Uniformance - PHD/Experion Link Installation and Configuration Guide • 165

8 Configure PHD Tags on PHD Experion Link
8.6 Tag Field Usage for PHD Tags on PHD Experion Link

Source Tag Source Tag PHD Description

Type Attribute Data Type
characters that can be held. (see NOTE 1)

US VALUE## U ## is a number from 10 to 80 that

represents maximum number of bytes
that can be held. (number of characters
would be half as 2 bytes are required per
(see NOTE 1)
character for Unicode)

In general, users can refer to the list in PHD Configuration Tool.

NOTE 1: Tag Synchronization does not use this tag type, but you may use them to
manually configure PHD tags to historize strings, such as point descriptions.

NOTE 2: If you specify EN/STRING, the Experion OPC Server will convert its
historized Ordinal value to a String and return the String to the PHD Experion Link.
For more information on enumerations, refer to the section 8.7, Collect and Access
Enumeration Data.

Source Tag Attribute

VALUE or STRING

Source Tag Units

For data entry details, refer to the PHD User Guide.

Collector Name
The Link name is not defined here, it is defined in the Interfaces form.
Note: If Tag Synchronization detects the removal of the Experion Point Parameter from
Experion history, it sets the Collector Name to the default "NONE".
Note: If tags defined on the PHD Experion Link are to be collected on the PHD Collector
Server node and then shadowed to a remote PHD Server shadow node, the Collector
Name must be set to the same value as the PHD Link Name. If tags are not to be
shadowed, then the Collector Name should be cleared (set to NULL).

Scan Frequency
For tags that are collecting point-dot-parameters that are defined in Experion History, the
Scan Frequency must match the fastest Experion history file that the point-dot-parameter
is configured in. The default Tag Synchronization Rule will set the Scan Frequency
appropriately.

166 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 8 Configure PHD Tags on PHD Experion Link
8.6 Tag Field Usage for PHD Tags on PHD Experion Link

ATTENTION
Honeywell advises that you should not change the Scan Frequency after Tag
Sync has set it to the appropriate interval.

When a point-dot-parameter is defined in Experion History, PHD has no control over

how often the tag is scanned. Changes to Scan Frequency on the PHD tag will not result
in a change to the Experion history collection rate or the actual data collection rate from
the source by Experion.
As with all types of PHD tags, the Scan Frequency affects the size of the tag’s Data
Queue on the PHD Server. Configuring the Scan Frequency slower than the fastest
history file can result in a degradation of performance in the PHD Server due to the data
queue for the tag being created too small. Conversely, configuring the Scan Frequency
faster than the fastest history file can result in increased memory usage in the PHD
Server due to a larger than required data queue size for the tag.
For PHD tags that are not historized on Experion, (such as strings), the Experion OPC
HDA Server will report the tags by exception, but no faster than the PHD tag’s Scan
Frequency.

Scan Frequency in terms of OPC HDA

The PHD Experion Link sets the UpdateInterval property of the AdviseRaw method on
the Experion OPC HDA server to the value of the PHD tag's Scan Frequency.
The PHD Experion Link uses the AdviseRaw method for continuous collection (updates
from Experion to PHD). The AdviseRaw method causes Experion to send blocks
(batches) of values as they are about to be written to the Experion history files. The
UpdateInterval property defines how often callbacks are made to the PHD Experion
Link.
The PHD Experion Link uses the ReadRaw method on the Experion OPC HDA server
for initial History Recovery. ReadRaw causes a read of the Experion history files.

How Scan Frequency affects compression

Whether or not PHD performs post processing (data compression) depends on whether
PHD receives the data in a block or as a single value. When PHD gets data in a block, it
treats it like a History Recovery request and does NOT perform post processing. When
PHD receives a single value, it treats it as a collected value and post-processes the data.
For example:

Uniformance - PHD/Experion Link Installation and Configuration Guide • 167

8 Configure PHD Tags on PHD Experion Link
8.6 Tag Field Usage for PHD Tags on PHD Experion Link

• If the Scan Frequency of the PHD tag is 60 seconds, but the Experion Server sends
the data every 5 seconds, then PHD gets the data in blocks of 12 values. Post-
processing, such as data compression, is not performed.
• If the Scan Frequency of the PHD tag is 5 seconds, and the Experion Server sends
the data at 5 second intervals, then PHD gets the data as single values. Post-
processing, such as data compression, is performed.

Digital Enumeration List Name

This field specifies the list that maps this tag's Ordinal integer values to Enumeration
Strings. This field, together with the Digital Enumeration enable flag, enables PHD to
return either ordinals or enumerations to clients accessing this tag's value.
If you historize the enumeration string (Source Tag Type = EN and Source Tag Attribute
= STRING), a client will still be able to obtain the ordinal value from PHD if needed.
The same is true if you historize the ordinal (Source Tag Type = EN and Source Tag
Attribute = VALUE) - a client will be able to obtain the enumeration string if needed.

REFERENCE
For information on the Digital Enumeration Configuration Form that you use
to create lists of enumerations, refer to the PHD User's Guide (pim0201)

PHD Link Name

This field specifies the Experion Server name (Target Host entries in the PHD Links
Configuration forms populate the dropdown list).

Extended Source Tag Name

This field specifies the Experion point.parameter that a PHD Experion Link will request
data from the Experion Server. 300 characters max. Case sensitive - may be upper and
lower case. The function block(s) are included in the information that Tag
Synchronization sees as the Experion PARAMETER variable. Controller point:
FunctionBlock.Parameter (Ex: PIDA.SP). SCADA point: Parameter.

Scale High Extreme

Scale Low Extreme
These fields specifies the lowest and highest values for F, D, L and I data type tags. If the
tag value is outside of the range, then PHD clamps the data to the limit and sets the
confidence of the value to 0. For details, refer to the PHD User Guide.

168 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 8 Configure PHD Tags on PHD Experion Link
8.7 Collect and Access Enumeration Data

The default Tag Synchronization rule sets these values to the Experion high range and
low range values.

Quantum
If a quantum is specified, incoming values are rounded to the nearest quantum (step). A
larger quantum yields greater PHD data storage compression, but reduces the precision of
the stored value. Compression is disabled if the Quantum is set to -1. For details, refer to
the PHD User Guide.

Synchronization Rule Name

This read-only field indicates the Tag Sync Rule that created the PHD tag definition.

Asset Name
Tagname of an asset defined through the Experion Enterprise Model Builder. For
example, if Enterprise Model Builder>Assets shows the following configuration:
Tag Name – E110_H11
Item Name – Condenser_H11
Full Item Name – Assets\D_H11\Condenser_H11
Then the Asset Name synchronized to PHD is E100_H11.

Item Name
Item Name defined through Experion Control Builder or Quick Builder. For example, if
Control Builder>Control Module shows the following configuration:
Tag Name – 11_AC12
Item Name – 11_AC12_item
Then the Item Name synchronized to PHD is 11_AC12_item.

8.7 Collect and Access Enumeration Data

Collect enumeration data
The PHD Experion Link can be configured to collect either the ordinal or the string
representation of enumerations from the Experion Server and return it to the PHD Server
for archiving. The Source Tag Type and Source Tag Attribute fields, as follows,
determine whether the PHD Experion Link collects the Ordinal or the String:

If the Source Tag And the Source Tag Then the Link collects this…
Type is this… Attribute is this…

EN VALUE Enumeration Ordinal

Uniformance - PHD/Experion Link Installation and Configuration Guide • 169

8 Configure PHD Tags on PHD Experion Link
8.7 Collect and Access Enumeration Data

EN STRING Enumeration String

Note: The Experion Server always places enumeration data types (such as MODE) into
Experion history by the ordinal value. If you specify EN and STRING, then the PHD
Experion Link automatically appends /ENUM to the item name. The Experion OPC
Server interprets /ENUM to mean that the client wants the enumeration string instead of
the ordinal value. The Experion OPC Server converts the historized Ordinal value to a
String and returns the String to the PHD Experion Link.
Note: When using Tag Synchronization, you may choose to add text to the default rule
to set the PHD tag definition of Ordinals to EN/VALUE. If needed, you can define a Tag
Synchronization rule to set tag definitions to EN/STRING.

Enable PHD to return either strings or ordinals to clients

If Ordinals are archived in PHD, you can enable PHD to return either Ordinal or String
data to clients by configuring the “digital enumeration handling”. This involves
configuring tables that allow PHD to map Ordinals to Strings, and then enabling the
Digital Enumeration flag on a per tag basis:
1. Complete the Digital Enumeration String Configuration Form (creates a list of all
the strings that are to be used by PHD to convert ordinals to strings).
2. Complete the Digital Enumeration Configuration form (creates a named list that
maps ordinals to corresponding enumeration strings).
3. Enable the Digital Enumeration flag in the Tag Configuration form.
4. Assign a Digital Enumeration List Name in the Tag Configuration form.

Client access of enumeration strings or ordinals

Uniformance Desktop clients (including Visual PHD OLE Server, Visual PHD controls,
Excel Companion, PowerPoint Companion, and ModTag) can access enumeration string
data by specifying a suffix on the tagname:
tagname/enum or tagname(enum).
Example:
If Ordinals are being archived, but Digital Enumeration handling has been enabled for a
tag, then specifying the tagname without the suffix returns Ordinal data, and specifying
the suffix returns Enumeration String data.
A100.MODE returns <ordinal>

170 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 8 Configure PHD Tags on PHD Experion Link
8.8 Configure Manual Input Tags on PHD Experion Link

A100.MODE(enum) returns <string>

Note: Clients of the PHD OPC Server can specify tagname(enum)

Note: With ModTag and Excel Companion, uses may select their default preference to
be Ordinals or Enumerations.

8.8 Configure Manual Input Tags on PHD Experion Link

To Put Download (write) a manually entered PHD value to an Experion tag, enter the
following PHD tag configuration:
1. Choose new Manual Input tag instead of the new Collected tag.
2. Enable the Put Download flag.
3. Choose the Experion Link in the RDI/Link Collector field.
4. Fill in the mandatory fields.
5. Specify the destination Experion point.parameter in the Extended Source Tag field.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 171

This page is intentionally left blank

Uniformance - PHD/Experion Link Installation and Configuration Guide • 172

 9. Monitor and Troubleshoot PHD-Experion
Integration
9.1 Troubleshoot the PHD Experion Link
Note: The Uniformance System Monitor (USM), a separately purchased application, can
be used to monitor PHD performance, including Uniformance Tag Synchronization.

View logs related to data collection

Function Log

PHD Experion Link C:\ProgramData\Honeywell\Uniformance\Log

– on PHD Server Files\LINK<linkname>.OUT. The Program Data folder
must be made visible.
Gives information about the Initialization of PHD tags,
poll groups, and errors during these actions, and
outgoing and incoming data packages.

Uniformance RDI Server \Program Files \Honeywell \Uniformance \Logfiles

service – on PHD Server: \RDIServer.LOG

PHD integrity monitor \Program Files \Honeywell \Uniformance \Logfiles

– on PHD Server \PHD_EVENT.LOG

Experion OPC HDA Server Program Files \Honeywell \Experion PKS \server \data
– on Experion Server \log.txt
Paranoid OPCHDA for hscopcserv.exe (HDA-specific
paranoid group for Experion OPC Server)
Note: A paranoid is a debug group whose debug level
can be modified.

Procedure to restart PHD Experion Link

From a command prompt or through the PHDMAN shortcut:
PHDMAN SHUT INT <linkname>
PHDMAN START INT <linkname>

Procedure to view PHD/Link Status

Use PHDMAN to view status of a Link: PHDMAN SHO INT <linkname>
To view the status with continuous updating: PHDMAN MON INT <linkname>

Uniformance - PHD/Experion Link Installation and Configuration Guide • 173

9 Monitor and Troubleshoot PHD-Experion Integration
9.1 Troubleshoot the PHD Experion Link

Interpret status and log messages

The normal Link status indications are:
State: ACTIVE
Interface: ACTIVE

Figure 13 – Link Status Display – With RDM

How to recognize normal history recovery messages (LINK<linkname>.OUT)

When the PHD Experion Link starts, it looks for the oldest of the most recent values in
the PHD data queues of all tags configured on the Link, and uses this timestamp to
determine how far back it is going to do history recovery.
When it performs history recovery, the Link outputs messages to the
LINK<linkname>.OUT file.
The Link submits the initial call for data (ReadRaw) and waits for data to be returned by
the Experion Serve – these messages are normal and indicate the Link works as intended:
[date/time] ID: 0: Info: ReadRaw() Start Time: [date/time]
[date/time] ID: 0: Info: ReadRaw() End Time : [date/time]
[date/time] ID: 0: Info: ReadRaw() Transaction ID: 0x00000001 (0
of 7 Failed)

174 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 9 Monitor and Troubleshoot PHD-Experion Integration
9.1 Troubleshoot the PHD Experion Link

After history recovery completes, the following normal messages indicate that the Link
switched to OnAdvise and is in "normal collection mode" (still asynchronous HDA
reads, but different from the initial call for data):
[date/time] ID: 0: Info: OnReadComplete() Received For: 7 Items
...
[date/time] ID: 0: Info: OnReadComplete() Switching To AdviseRaw
For: 7 Items
Note: When the Link performs history recovery, its status shows ACTIVE ACTIVE,
but the history data may not come in until several minutes later.

System state
The top portion of the Link status display indicates the current system state, the current
local system time, and the current time of the real-time system, as given by current local
time plus the Link's Delta clock seconds.

REAL TIME DATA INTERFACE

The REAL-TIME DATA INTERFACE portion of the Link status display shows Link
states and Link statistics. Note: PHD collects average rate statistics for the Link only
when the STATISTICS parameter is 1 (ON). The <No stats> indicator appears when the
STATISTICS parameter is 0 (OFF). There is overhead associated with the statistics
collection, and as a result, you must explicitly enable statistics collection, when needed,
using PHDMAN or RDISetup.

RDI PARAMETERS
The RDI PARAMETERS portion of the Link status display shows the current parameter
values. If the Link has been configured to support redundant Experion Servers,
HOSTNAME indicates "RDM: n" (see Figure 13). For non-redundant Experion Servers,
HOSTNAME indicates the Target Host Name (see Figure 14).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 175

9 Monitor and Troubleshoot PHD-Experion Integration
9.1 Troubleshoot the PHD Experion Link

Figure 14 – Link Status Display – Non-Redundant Experion Server

RDI FLAGS
The RDI FLAGS portion of the display contains the NEWTAGS or SHUTDOWN flag
parameters, indicating the presence of a new tag update or a shutdown request.

REFERENCE
For definitions of states, statistics, and parameters, refer to the PHD System
Manual (pim0301), section "Monitoring the RDIs and Links".

Common installation problems

In most cases, installation problems are due to the following:
• The interface startup parameters from PHD are incorrectly defined (PHD Links
Configuration form).
• The interface has not been defined to PHD (RDISetup and Interfaces.Dat have not
been run).
• Hosts file on PHD Server is not correct:
- Hostnames of redundant system are not correct.
- IP addresses are not correct.

176 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 9 Monitor and Troubleshoot PHD-Experion Integration
9.2 Troubleshoot Redirection Manager (RDM)

Symptom - Missing history data on PHD Server after history recovery

After the PHD Experion Link performs history recovery, if there are missing samples or
if a PHD tag recovered no history samples, but other PHD tags are fine, perform the
following steps to troubleshoot the problem.

Step Action
1 On the Experion Server, check to see if the samples exist.
2 On the PHD Server, check RDIServer.LOG to see if any errors are reported
for any of the samples.
3 If necessary, Honeywell TAC can instruct you on how to turn up the Experion
OPCHDA paranoid for hscopcserv.exe and then ask you to reproduce the
problem.

Symptom - PHD failed to collect non-historizided point parameters from Experion

Experion (R400 and later versions) has a new configuration available to prevent the
access of non-historized point parameters from PHD Experion Link. The Allow PHD to
access non-historized point parameters check box is available in the Server Wide
Settings of Experion station. The non-historized point parameters tags assigned in PHD
Experion Link collects the data only if the check box is enabled. If the check box is not
selected, PHD displays the value of ‘0’ and the confidence of ‘-1’.

9.2 Troubleshoot Redirection Manager (RDM)

View logs related to RDM

Location Log

PHD Server The Redirection Manager logs its events and errors
into the Windows Event Log. The log includes the
same status changes seen in a Honeywell System
Management Display or an Experion System Status
Display. Typical log entries include the following:
• Switchovers to the secondary Experion Server.

• Errors returned during OPC calls made to the

alternate server.
• “Out of sync” error messages on the alternate
server. If you see this message, check the event log
for more information.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 177

9 Monitor and Troubleshoot PHD-Experion Integration
9.2 Troubleshoot Redirection Manager (RDM)

View RDM auxiliary status display

When the PHD Experion Link successfully connects to RDM, the connection status
automatically appears in the Honeywell System Management display and the Experion
System Status display. At that time, you can callup the Redirection Manager Auxiliary
Status Display to view details of the connection.
The System Management Display example in the following figure shows the status for
RDM_10 in the left pane. The right pane shows the Redirection Manager Auxiliary
Status Display.
A disconnect causes the connection to disappear from the system displays.

REFERENCE
For details on Redirection Manager status, refer to the Experion Redirection
Manager User's Guide in the Experion book set.

Figure 15 – Redirection Manager Auxiliary Status Display

178 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

9.3 Troubleshooting Tag Synchronization

To view logs related to Tag Synchronization

Function – Location Log

Uniformance Tag Sync C:\ProgramData\Honeywell\Uniformance\Log

service Files\UniformaceTagSync.log. The Program Data folder
– on PHD Server must be made visible.

Shows the tags being received by PHD. You can increase

the level of detail that is output by using the registry
parameter (see Appendix A).

Experion History Tag Program Files \Honeywell \Experion PKS \server \data
Synchronization Server \log.txt
– on Experion Server
Paranoid HTS for htsserver.exe (general paranoid group
for Tag Synchronization server)
Paranoid HTSTAG for htsserver.exe (displays tag
information sent to PHD)

To view Tag Synchronization Status and Tuning display

Step Action
1 On Experion Server, logon to Station as a user with administrator access.
2 In Station, choose Configure>System Hardware>PHD Server.

The possible Tag Synchronization statuses are:

Not Synchronized, Synchronizing, Synchronized, Failed.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 179

9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

Figure 16 – Tag Synchronization Status Display

Tag Synchronization Description

Statistics

History Parameters Number of unique point.parameters currently assigned to

Count Experion history. PHD should have this many tags built
(synchronized) from this server.

Total tags output Number of tag updates that PHD retrieved.

Transaction Count Count of network calls. Note: An increasing number

confirms connectivity.

Queue Size Count of changes currently queued and waiting for PHD to
retrieve.

Average Rate Rolling average throughput calculated over last 30 minutes.

Maximum Rate Peak throughput

180 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

The Tuning tab shows the following Tag Synchronization settings.

Tag Sync Tuning Description

List Fragment Size The number of history point.parameter definitions that the
Experion server will process per subscription period.
Default is 100. Note: Do not increase this value without
consultation with Honeywell TAC, to ensure the load on the
Experion Server and PHD Server is not excessive.

Subscription Period Defines the period for how often the PHD Server should poll
the Experion Server for history tag definition changes.
Default is 60 seconds.

Timeout Interval Specifies the amount of time before the Experion tag sync
server causes the connection to timeout, after no
transactions are received from PHD Server.
Default is 180 seconds. Note: The value must be at least
three times the Subscription Period.

History Rate Update Defines the maximum amount of time for the Experion
Period Server to identify a change to Experion history configuration
for tag synchronization. Default is 60 seconds.

The History Rate Update Period + the history rate configured

on the parameter is the maximum amount of time for the
Experion Server to report a point.parameter history
assignment change to the PHD Server.

This setting applies only to Experion R400 and greater.

ATTENTION
Only experienced personnel should change the Tag Synchronization tuning.
If the entered settings are not suitable, they automatically adjust to be
compatible with this Experion Server's global cache settings.

To locate PHD tags with range errors after executing Tag Sync
If Tag Sync is already done, and PHD clamped a value due to a range error, it assigns
zero (0) confidence to the value. Tags with a confidence greater than zero may have a
different problem.
You can view tags with bad confidence through the following command:
PHDManager> report conf nnn

Uniformance - PHD/Experion Link Installation and Configuration Guide • 181

9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

Where nnn is the number of tags to include in the report (default is 10). Figure 17 shows
example results.

Figure 17 – PHDMAN Confidence Report Indicates Problem Tags

182 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

To handle tag configuration errors

If incorrect data is being set in the PHD tag configuration, then it is up to you to identify
the problem.

To fix PHD tags with range errors, build a rule for range, and then force a resync.
You may want to restrict the resync to the tags with zero (0) confidence.
If you have problems in your PHD tag configuration, then after you fix the rules,
it may be better to rerun all tags through Tag Sync; that is, force a resync.
To handle rule compilation errors
If a Tag Sync rule has a syntax error, the rule will not compile in Tag Sync.
You can increase the Debug level of Tag Sync to 10 or above to output the rule text to
the file and show the compilation error. Use the registry parameter to increase the Debug
level (see Appendix A).
Alternatively, you can use Visual Studio to check rule syntax. In the PHD Configuration
Tool, select Export Rule on the Tag Synchronization Rule Configuration form to export
the rule text to a file. Insert the rule text into a Visual Studio 2005 project and compile it
there. After syntax checking is completed (solution builds), insert the rule text back into
the PHD Configuration Tool form for use by Tag Sync.

To force a resync
The easiest way to force a resync is through an update of the
LAST_UPDT_FILETM column in the database, as described below:

Uniformance - PHD/Experion Link Installation and Configuration Guide • 183

9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

• To force a resync of tags with zero (0) confidence, execute either of the following
statements at a SQL prompt:
UPDATE PHDCFG.PHDCFG.UF_TAG SET LAST_UPDT_FILETM=1000
WHERE TAGNO IN (List of Tagnos with bad confidence)
• To force a resync of all tags, execute the following statement at a SQL prompt:
UPDATE PHDCFG.PHDCFG.UF_TAG SET LAST_UPDT_FILETM = 1000
WHERE LAST_UPDT_FILETM is Not Null

View log related to PHD Point Server and Experion trends

Function – Location Log

Experion PKS PHD Point \Program Files \Honeywell \LogFiles \logps.txt

Server service
– on PHD Server

Interpret PHD Point Server Status display

On the Experion Server, check the LEDs on the PHD Server Status display - the Network
Status LED and the Data Status LED should be OK and green.

Step Action
1 On the Experion Server, logon to Station as a user with administrator
access.
2 In Station, choose Configure>System Hardware>PHD Server.

Result: The PHD Server display appears.

184 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

Figure 18 – PHD Point Server Status Display

As shown in the previous figure, the right-hand section of the display is associated with
the PHD Point Server.
If the PHD Point Server is not configured on the Experion Server, then the entire “right-
hand” section of the screen is blank.

Symptom - Connection problems

If the Network Link Status LED is not OK, then check the network connectivity between
the Experion and PHD Servers. Try to ping the PHD Server from the Experion Server(s)
and ping the Experion Server(s) from the PHD Server.
On the PHD Server, in the Services window, check that the "Experion PKS PHD Point
Server" service is running.
On the PHD Server, check the log file (logps.txt) for errors.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 185

9 Monitor and Troubleshoot PHD-Experion Integration
9.3 Troubleshooting Tag Synchronization

Symptom - Data missing from Experion trend

If PHD data is missing from an Experion trend, perform the following actions to
troubleshoot the problem.

Diagnostic check On the Experion Server, call up the PHD Point Server Status display and
check the status.

Cause If both of the PHD Point Server LEDs are not green, then the trend data is not
available because the PHD Point Server has failed.

Solution On the PHD Server, restart the Experion PKS PHD Point Server service.

Diagnostic check On your Experion trend, does the PHD data appear if you reduce the number
of PHD tags in the trend?

Cause The PHD Point Server measures the time it takes to read a single PHD tag
and then estimates the time required to read all of the PHD tags on the trend.
If this time exceeds the HistoryTimeout value (see 10.3, PHD Point Server
Registry Settings, HistoryTimeout), then the request is canceled and no data
is returned.

Solution On your Experion trend, reduce the number of PHD tags in the trend until the
PHD Point Server does not exceed its HistoryTimeout value.

Diagnostic check On your Experion trend, does the PHD data appear if you change the interval
from an average to a snapshot?

Cause The PHD Point Server checks all data returned from PHD and determines if
the values are below the minimum confidence value (see 10.3, PHD Point
Server Registry Settings, MinConfidence). If the values are below the
confidence value, then the data is not plotted on the trend. Missing data due to
this situation is more likely to occur when you use average intervals in your
trend.

Solution On your Experion trend, change the interval from an average to a snapshot.

186 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 9 Monitor and Troubleshoot PHD-Experion Integration
9.4 PHD Confidence and OPC Quality

Recommendations - minimize PHD CPU usage and trend data callup time

Consider Recommendation Comment

This…

Trend Avoid trends of

Interval PHD tags at the
Experion Fast
history interval.

Trends with Avoid calling up Trends with average interval types (such as 1 hr avg
Average trends of PHD and 8 hr avg) request average reductions from the PHD
interval type tags with averages Point Server, which can cause:
of PHD tags at fast
Scan Frequencies. Increased CPU usage – due to PHD having to average
its raw data before returning it to the PHD Point Server.
Larger intervals relative to the PHD tag’s Scan
Frequency will cause more CPU usage. For example,
calling up a 24 hour average trend on PHD tags that
have a 5 second Scan Frequency will cause increased
CPU usage by the PHD software.

Increased call up time – due to the calculations that

PHD has to perform to average the data.

Number of Avoid configuring Requests for more tags from PHD can cause:
traces too many traces of
PHD tags on a Increased CPU usage – due to more data and values
single Experion having to be retrieved from PHD
trend.
Increased call up time – due to the amount of values
that PHD has to process and the number of values that
have to be passed back from PHD to the PHD Point
Server to Experion. There is a fairly linear relationship
between the number of traces and the call up time.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 187

9 Monitor and Troubleshoot PHD-Experion Integration
9.4 PHD Confidence and OPC Quality

Consider Recommendation Comment

This…

Call up time After the initial Initial trend call up causes a data request for all traces
versus Live callup of a trend, for the entire Time Period of the trend, leading to
Update click Play to put significant CPU usage and call up time. For example,
mode the trend into Live calling up a 1 min interval trend for 1 day of 10 PHD
Update mode. tags causes retrieval of 14400 values (60 minutes X 24
hours X 10 tags) immediately on call up.

If you put a trend into Live Update mode, it updates at

the Interval rate, and only retrieves the last (newest)
values, minimizing the amount of CPU usage. For
example, viewing a 1 min interval trend of 10 PHD tags
causes retrieval of only 10 values (1 value X 10 tags)
every minute.

9.4 PHD Confidence and OPC Quality

If OPC Quality is… Then PHD Confidence is…

BAD –1

UNCERTAIN 0

GOOD 100

188 • Uniformance - PHD/Experion Link Installation and Configuration Guide

10. Appendix A – PHD Server Registry Settings for
PHD-Experion Integration
10.1 PHD Experion Link Registry Settings
The location of the registry key for the PHD Experion Link is as follows:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services
\ <RDI Server> \ Parameters \ LinkList \ <linkname>\
<parameter>
If needed, you can use regedit to add the following parameters:

Parameter Description

IgnoreMaxClockDelta DWORD. Enter 1 to specify that the Link should

ignore the clock delta difference in time stamps
received from the Experion Server. Default is 0.

IgnoreNegativeConfidence DWORD. Enter 1 to disable the insertion of a 0

(zero) tag value with a -1 confidence when the
Link is started, shutdown, or every 24 hours
when the Link resynchronizes its time.

During startup, the default behavior will insert a 0

tag value with a -1 confidence – this negatively
impacts data recovery performance.

Attention: Honeywell recommends that you add

this parameter to the registry and set it to a value
of 1.

InformationLevel DWORD. Sets the debug level for information

messages from the Link. Leave at default - other
values are for troubleshooting purposes only.

OutputFile STRING. Specifies name of .OUT file where Link

outputs information (in 'Log Files' directory).
Default is LINK<linkname>.OUT.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 189

10 Appendix A – PHD Server Registry Settings for PHD-Experion Integration
10.2 Tag Synchronization Registry Settings

Parameter Description
TagUpRange DWORD. Specifies whether the Link should
trigger a PHD tag update when a change occurs
to the low or high range value on Experion
Server points.

1 – Trigger PHD tag update.

0 – Do not trigger PHD tag update. Tag Sync will

still change the tag definitions in the database,
but this Link on the PHD Server will not be
updated.

Default is 0. In most cases, you should leave the

value at default of 0.

Note: If you change the parameters for a running PHD Experion Link, you may have to
restart the Link for the changes to be implemented.

10.2 Tag Synchronization Registry Settings

The location of the registry key for Tag Synchronization is as follows:
HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\
UniformanceTagSync\ Parameters
Note: You can access all the registry settings for Tag Synchronization through the
Uniformance PHD Tag Synchronization Server Properties dialog box of
Uniformance PHD Tag Synchronization Server.
The following table describes the Tag Synchronization registry parameters.

Parameter Type Description

InformationLevel DWORD The debug level. Controls the amount of

information logged to the log file
(UniformanceTagSync.log). The value can be from
1 to 10. One (1) creates the least amount of logged
information. Use 2 for the initial Tag Sync. Use 6
for troubleshooting problems. Use 10 or above to
output the rule text to the file and show any
compilation errors. Default : 1.

190 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 10 Appendix A – PHD Server Registry Settings for PHD-Experion Integration
10.2 Tag Synchronization Registry Settings

Parameter Type Description

SystemList\ Multi-String List of "Target Hostnames" of Experion Servers to

Experion\ Value be used for PHD Tag Synchronization by Tag
Machines Synchronization.

Attention: After configuring the PHD Experion

Link, you must execute the Save RDI/Link
Configuration command through the RDISetup
utility to cause 'Machines' to be created in the
registry and populated with the names of the
Experion Servers (Target Hostnames) specified in
the Interfaces (RDI’s and Links) form(s). You can
view the Experion Servers listed in the
Uniformance PHD TAG Synchronization Server
Properties under the Tag Synchronization
Configuration tab of Uniformance System
Console.

If the parameter is not present and populated, rerun

RDISetup and execute the Save Configuration
command.
MaximumLogFiles DWORD Maximum number of log files to keep
MaximumLogSize
Maximum log file size in KBytes

Uniformance - PHD/Experion Link Installation and Configuration Guide • 191

10 Appendix A – PHD Server Registry Settings for PHD-Experion Integration
10.3 PHD Point Server Registry Settings

10.3 PHD Point Server Registry Settings

The PHD Point Server reads a set of configuration settings stored in the registry as
follows:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Honeywell \ PHDPointServer\
The following table describes some of the configurable settings. These are read only
when the PHD Point Server service is first started. Note: The service will need to be
restarted to allow any changed settings to take effect

Key Type Description

AllowTagSyncTags By default, this setting is not created.

This key contains a flag to allow the PHD Point Server to
read PHD tags that have been set up through Tag
Synchronization with Experion.

0 - Do not allow Tag Sync tags to be accessed. (Default)

1 - Allow Tag Sync tags to be accessed.

Attention: If you wish to allow Experion operators to view

the history of PHD tags that are Tag Synchronized to
Experion point parameters, then create this registry string
value and set the value to “1”.

Attention: Be aware that setting the value to "1" bypasses

any PHD tag READ security or Experion operator security
that has been associated with the PHD tag or the
originating Experion point parameter.

Operators who are restricted from viewing history data

from assets in the Experion security system will have read
access to all the data in PHD.

No tag values on PHD or values of the source Experion

point parameter can be changed through the PHD Point
Server.

192 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 10 Appendix A – PHD Server Registry Settings for PHD-Experion Integration
10.3 PHD Point Server Registry Settings

Key Type Description

AverageRetriev This key contains the PHD data access retrieval attributes
al Settings that are used when you view an Experion Average trend.
Default value: ResampleType=InterpolatedRaw;
ResampleFrequency=60;
UseResampleFrequency=0;
ReductionType=Average;
ReductionOffset=Before

For details, see the section Average and Snapshot

retrieval settings.
CentralName This key contains the base name of the Experion Central
server. This is set to the Central Name value entered by
the user during installation.
DataPort This key contains the RPC port number that the PHD
Point Server will use to communicate with the Experion
Server.
ATTENTION: Do not change this setting without
consultation with Honeywell.
HistoryTimeout This key contains the timeout in milliseconds to use for
requests to PHD. The PHD Point Server measures the
time it takes to read a single PHD tag and then estimates
the time required to read the total number of PHD tags
included in the Experion trend. If the estimated time
exceeds this HistoryTimeout value, then the request is
canceled and no data is plotted on the trend for the
requested time range. Default is 10000.
InstanceName This key contains a unique name that identifies the point
server. This should match the Alias field on the point
server configuration page. Default is PHD.
LinkdPort This key contains the RPC port number that the PHD
Point Server will use to communicate with the Experion
Server.
ATTENTION: Do not change this setting without
consultation with Honeywell.
MinConfidence This key contains the minimum confidence value for good
data to be plotted on an Experion trend. If the confidence
of a value read from PHD is below this number, then the
value will not be plotted on an Experion trend – it will
appear as a gap on the trend. Default is 100.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 193

10 Appendix A – PHD Server Registry Settings for PHD-Experion Integration
10.3 PHD Point Server Registry Settings

Key Type Description

NotifPort This key contains the RPC port number that the PHD
Point Server will use to communicate with the Experion
Server.
ATTENTION: Do not change this setting without
consultation with Honeywell.
PHDServerName By default, this key is not created.
The default value that is used for the name of the PHD
Server with which the PHD Point Server will communicate
is “localhost”.
To change the value, create this registry string value and
set the value to the PHD Server name.
SnapshotRetrie This key contains the PHD data access retrieval attributes
valSettings that are used on an Experion Snapshot trend. Default
value:
ResampleType=Resampled;
UseResampleFrequency=1;
ReductionType=None;
ReductionFrequency=60;
ReductionOffset=Before

For details, see the section Average and Snapshot

retrieval settings.

Average and Snapshot retrieval settings

The Experion Trend currently supports two types of data aggregation – Snapshot and
Average. For example, Fast history, 1 minute, 1 hour, 8 hour and 24 hour intervals use
Snapshots. The 6 minute average, 1 hour average, 8 hour average and 24 hour average
intervals use Average.
The PHD Point Server maps these types of requests to PHD data request properties. You
can configure this mapping through the following registry keys:
• AverageRetrievalSettings
• SnapshotRetrievalSettings
You can modify the mapping through the string value of each key. The string value takes
the following form:
ResampleType=#;ResampleFrequency=#;UseResampleFrequency=#;
ReductionType=#;ReductionOffset=#;ReductionFrequency=#

194 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 10 Appendix A – PHD Server Registry Settings for PHD-Experion Integration
10.3 PHD Point Server Registry Settings

The following table describes the PHD data request properties contained in each string
value.

Property Description
Resample The type of resampling. Valid values are: AVERAGE,
Type INTERPOLATEDRAW, RAW, RESAMPLED, SNAPSHOT.
Resample The value stored here is currently ignored. If
Frequency UseResampleFrequency is 1 (TRUE), then the
ResampleFrequency will be set to the interval period of the trend.
For example, a 1 minute trend will use a 1 minute (60 second)
resample frequency for the PHD data request.
UseResample This value specifies whether to set the PHD Resample frequency
Frequency or Reduction frequency to the interval period of the trend:

1 (TRUE) – Sets the PHD resample frequency to the interval

period of the trend.

0 (FALSE) – Sets the PHD reduction frequency to the interval

period of the trend.

Example - 1 hour interval trend:

UseResampleFrequency = 1 (TRUE)
The PHD data request will use a resample frequency of 1 hour
(3600 seconds) and a reduction frequency of 0.

UseResampleFrequency = 0 (FALSE).
The PHD data request will use a resample frequency of 0 and a
reduction frequency of 1 hour (3600 seconds).

Uniformance - PHD/Experion Link Installation and Configuration Guide • 195

10 Appendix A – PHD Server Registry Settings for PHD-Experion Integration
10.3 PHD Point Server Registry Settings

Property Description
Reduction The type of reduction. Valid values are:
Type AVERAGE, DELTA, FIRST, LAST, MAXIMUM, MINIMUM, NONE,
REGRESSIONCONSTANT, REGRESSIONDEVIATION,
REGRESSIONSLOPE, STANDARDDEVIATION.

Reduction The Reduction Offset defines how the reduction value timestamp
Offset relates to the data in the interval over which the reduction is
performed. Valid values are: AFTER, BEFORE, AROUND.
Reduction The value stored here is currently ignored.
Frequency If UseResampleFrequency is 0 (FALSE), then
ReductionFrequency will be set to the interval period of the trend.
For example, a 1 minute trend will use a 1 minute (60 second)
reduction frequency for the PHD data request.

196 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 11. Appendix B – Overview of RDISetup
11.1 RDISetup Data Flow
The PHD RDI Configuration utility (RDISetup.exe) is used to create/update the
configuration of PHD Experion Links and RDIs on the PHD Server node. The following
figure illustrates the RDISetup functionality.

Figure 19 – Configuration of PHD Experion Links through RDISetup

Uniformance - PHD/Experion Link Installation and Configuration Guide • 197

This page is intentionally left blank

Uniformance - PHD/Experion Link Installation and Configuration Guide • 198

 Glossary

Collector Node
A collector node is a PHD Server that performs data collection from a source system
such as a DCS. The PHD Server that runs the PHD Experion Link interface is a collector
node. Also known as "PHD Collector Server node".

History Recovery
The retrieval of data from a source system by an interface (such as the PHD Experion
Link) for the period of time during which the interface was unable to collect data directly
from the source system. The recovered data will eliminate the data gaps that result from
non-collection of data.

Link
PHD interface to a Honeywell Experion Server. One Link is used to collect data from
one redundant or non-redundant Experion Server.

RDC
Robust Data Collection. Provides a method to transfer data from a PHD Collector Server
node to a PHD Shadow Server node. It also provides a method to transfer the data
collection duties from an Active RDI to a Standby RDI if the Active RDI fails or is taken
out of service - this is typically used for an interface that does not have source system
history recovery capability.
RDC uses a SHADOW type of interface to transfer data from a Collector node to a
Shadow node.
Note: PHD Experion Link supports only simple RDC. On selecting PHD Experion Link
in RDC, the Standby node gets disabled.

Uniformance - PHD/Experion Link Installation and Configuration Guide • 199

Glossary

RDI
Real-time Data Interface. An interface used to collect data from a source system for
storage in the PHD database. PHD includes several types of RDIs and others are
available from Honeywell for many types of DCS, PLC, SCADA, and other real-time
sources of data.

Shadow
A remote PHD Server node used to gather and store process information from one or
more PHD Collector Server nodes.

Source System
The system that provides the real-time data to the PHD system. This can be another PHD
system or a DCS system.

Tag
A distinct value residing in the source system and collected by a PHD interface (RDI or
PHD Experion Link).

200 • Uniformance - PHD/Experion Link Installation and Configuration Guide

 Index

F4.. See four byte float.

Index four byte float data type, 165

four byte integer data type, 165
attribute mapping
History
understanding, 165
Experion History Assignment, 22
case, 119
History Recovery
Configuration
Log Messages, 175
Interfaces.Dat, 116
HistoryTimeout, 186
PHD Links Configuration Form, 107
Hosts file
PHD Server Hosts File, 90
PHD Server, 90
Registry, 189, 192
I4.. See four byte integer.
D8.. See eight byte float.
Local Groups, 45
Data Status LED, 184
Local Policy, 45
data types
Log
D8 or eight byte float, 165
History Recovery Messages, 175
F4 or four byte float, 165
Network Status LED, 184
I4 or four byte integer, 165
OUT
requesting specific types, 165
Link Output File messages, 175
DCOM
PHD Point Server, 194
running DCOMCNFG, 52
PHD reduction frequency, 195
DCOMCNFG, running, 52
PHD resample frequency, 195
default rule, 118, 120
PHD tag definitions
Default Rule, 120
tag source type/attribute mapping, 165
eight byte float data type, 165
RDISetup Data Flow, 197
Experion Links, 197
Reduction Offset, 196
Experion point parameter, 192
Registry
Export, 120, 183

Uniformance - PHD/Experion Link Installation and Configuration Guide • 201

 Link, 189, 192
Restart
link, 173
Scan Frequency, 187
Status
link, 173
syntax, 120, 183
System Management Display, 178
tag source type/attribute mapping:, 165
troubleshooting
link, 176
Visual Studio 2005, 183

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