Introduction-Overview

PHD Introduction
Honeywell Confidential
Introduction/Overview Copyright © 2013 Honeywell International Inc. PHD Introduction
1 9/2/2014
Lesson Objective Honeywell
• Objective
– Identify the PHD system hardware and software components and their
interrelationships
• Topics
– Role of PHD
– Basic PHD Components
– Uniformance Desktop Components
– Menus
– System Topology
2 9/2/2014
Role of PHD Honeywell
• The role of PHD is to:
– Integrate all the real time processes and process-related data
– Provide the process-related information to applications like PHD
Configuration Tool and Uniformance Process Studio
– Manage the archiving of process data so that it is available for future
reference
– Provide a single controlled interface to DCS and SCADA systems
– Provide a facility for doing process calculations and trending capabilities
3 9/2/2014
Basic PHD Components Honeywell
• PHD collects, integrates and maintains a history of real-time continuous
and discrete production data, process performance data, and process-
related data
PHD Configuration and PHD Real Time and
Application Database History Database
Application
Database
MS SQL Server PHD Server
APP
CFG Archive
Configuration
Database
Experion Link RDI
Experion DataSource
PHD – Process History Database
R300+ System
RDI – Real Time Data Interface
4 9/2/2014
Basic PHD Components, continued Honeywell
• PHD Server (32 bit and 64 bit versions)
– History Engine
– Real-time and History Database (Archive)
• OPC Server
– DA 3.0 compliant
– HDA 1.2 compliant
• Microsoft SQL Server
– CFG - Database containing PHD configuration information
– APP - Database containing application information
– Also known as the Uniformance SQL Databases
• RDI
– Vendor-specific hardware and/or software that collects data from a source system
– Also known as a collector
• Experion Link
– Software that collects data from an Experion 300+ system
– Also known as a collector
• PHD Configuration Tool
5 9/2/2014
Configuration-
(CFG) Database Real Time Database
Hard Disk
MS SQL Server
PHD Server Memory
Memory
CFG Copy of
PHDCFG.UF_TAG table Tag Definitions
PHD Tag Names FIC100.PV Current Archive
Ranges 0-60 BPD
Scan Frequencies 60 Sec. Scan
Queues Files
Collector assignments RDI “A” 14:00 30.0 BPD
…other tag definitions 14:01 30.0 BPD
• Based on the tag configuration, tag values are

collected and time-stamped by the RDI, held in RDI “A”
60 Sec Scan
the PHD Server’s memory queues, and then
Tag IDs
periodically moved to an archive file on hard disk
• ARCHIVE - The current queues and the archive
files together are often referred to as the archive Source System
6 9/2/2014
• A minimum of one ________ is used to collect data from each
source system
• The __________ gathers samples of data at a user-defined frequency
per tag in the Current Queue
• The ________ are memory within the PHD Server where the most recent
tag data is cached (Ex. Last 30 minutes)
• Data processing options, such as compression, may be performed in the
__________ before data is sent to the ____________
• The ______________containing several years of data is saved on hard
disk of PHD Server
7 9/2/2014
End Users and Application Programs
APP- Application Database

CFG - Configuration Database
Real Time Database
Hard Disk
MS SQL Server PHD Server
Memory Memory
Copy of
APP
Tag Definitions
FIC100.PV Current
0-60 BPD Archive
CFG Queues
PHDCFG.UF_Tag.table 60 Sec. Scan
14:00 30.0 BPD Files
… and other tables RDI “A”
14:01 30.0 BPD
RDI “A”
60 Sec Scan
Tag IDs
Source System
8 9/2/2014
• The __________ Server using the ________ database takes care of end
user requests for PHD configuration information, such as tag
configuration of FIC100.PV
• The ________ Server takes care of end user requests for real-time and
history data
• The most recent data is retrieved from the ________ , which are in the
memory of the PHD Server
• Older data is retrieved from the ___________ , which are stored on the
PHD Server’s hard disk
9 9/2/2014
APP- Application Database

CFG - Configuration Database
Real Time Database
MS SQL Server Hard Disk

Memory
PHD Server Memory
Copy of
APP
Tag Definitions
FIC100.PV Current
0-60 BPD Archive
CFG Queues
PHDCFG.UF_Tag.table 60 Sec. Scan
14:00 30.0 BPD Files
… and other tables RDI “A”
14:01 30.0 BPD
RDI “A”
60 Sec Scan
Tag IDs
Source System
10 9/2/2014
• End users and application programs may do the following (choose the
correct answer):
– Manually insert a new data value into the queue or archive file
– Edit an existing data value located in the queue or archive file
– Download a data value from the queue to the PHD Server
– All of the above
11 9/2/2014
PHD System Topology Example – Single Node Honeywell

For complete information on the
PHD and Uniformance Desktop
platforms,
refer to these sections of the
PHD R310 SCN:
• Uniformance PHD Release 310 Users
and Supported Platforms
PHD Server
MS SQL
RDI
Source
System
12 9/2/2014
PHD System Topology Example – Shadow System Honeywell
• A Shadow PHD server receives

data from one or more “process-
connected” PHD servers (collectors)
• The configuration data for the PHD

servers can be contained in the
same MS SQL server database, and
it resides on any of the PHD servers
or on a separate database server
• The PHD servers from which the

shadow receives data are
sometimes referred to as “buffers”
Best Practice: House the PHD
Shadow server(s) in a De-Militarized
Zone (DMZ)
13 9/2/2014
PHD System Topology Example – Shadow System Honeywell
•Typically, a Shadow system is

used for online interaction with the
majority of end users.
• A Shadow PHD server supports
the collection of data from any
number of PHD collector nodes, or
Experion servers.
• Except Uniformance Process
Studio (UPS)300, following PHD
desktop tools is supplied on the
PHD R310 media
•USM – Uniformance System
Monitor
•PCT – PHD Configuration Tool
14 9/2/2014
Architecture
Introduction/Overview Copyright © 2013 Honeywell International Inc. Architecture
15 9/2/2014
• Objectives:
– Understand the basics of PHD R310 Architecture
• Topics
– Supported OS
– Architectural Views
– Default Ports Used
– Servers and Services
16 9/2/2014
Lesson Topic: PHD System Computers Honeywell
• Supported Operating Systems:
– Server (SQL Server 2008 & PHD Server)
• Windows 2003 (x86) Windows 2003 (x64)
• Windows 2003 R2 (x86) Windows 2003 R2 (x64) Service Pack 2
• Including both Standard and Enterprise versions
– Client (PHD Configuration Tool, Uniformance System Console and the R310
.NET API)

• Windows 2008 R2 (x86) Windows 2008 R2 (x64)
Service Pack 1
• Windows 7 Professional (x86 & x64)
• Including both Standard and Enterprise versions
17 9/2/2014
PHD Server Components Honeywell
System Console Visual PHD

OPC Server
Port 41000 RemoteAPI Port 3150
Server .Net Wrapper
PHDStart *
Port 2000 Port 2000
Port 2000
Port 4100
RDI Server PHD Server
Port 2000
Port 3100 Port 3100 PHD Manager

Port 3001 Port 53100
RDI/ Link Uniformance

DBSecurity API Server
Database
Server
Services Port 3100
Experion, OPC, LxS OLE DB

PHD OLE DB
or other system
SQL Server 2008 PCT
Configuration DB
PHDCFG
PHDAPP
*- PHDStart Service connects to all other services

18 9/2/2014

OPC Server
Server .Net Wrapper
PHDStart *
Port 2000 Port 2000
Port 2000
Port 4100
Port 2000


Database
Server
Services Port 3100
Remote Computer

PHD OLE DB
or Other System
SQL Server 2008 PCT
Configuration DB
PHDCFG
PHDAPP

19 9/2/2014
Remote Computer
OPC Server
Server .Net Wrapper
PHDStart *
Port 2000 Port 2000
Port 2000
Port 4100
Port 2000


Database
Server
Services Port 3100

PHD OLE DB
or Other System
SQL Server 2008 PCT
Configuration DB
PHDCFG
PHDAPP

20 9/2/2014
Lesson Topic – PHD System Computers Honeywell
• Uniformance Process Studio (R300) along with Uniformance Process
Studio R220 can be used to request data from PHD R310
• PHD R310 does not automatically support named pipe connections from
these releases, requiring that they be changed over to SSPI (Security
Service Provider Interface) authentication or that named pipes be
enabled upon the PHD R310 server
• Altering the desktops to utilize SSPI would have registry entries added
to the client computer
– Under HKLM\Software\Honeywell\Uniformance create entries:
• Type Name Setting
• String Value UseFirewallPackage NTLM
• DWord UseFirewallSecurity 1
21 9/2/2014
Lesson Topic – SQL Server 2008 Honeywell
• Since PHD R300, the configuration database is hosted under SQL
Server 2008
• Both x86 and x64 operating system versions are supported for Windows
2003 and Windows 2008
• SQL Server 2008 licensing can be acquired from Honeywell and
installed using PHD R310 media
• SQL Server software is installed only upon the computer hosting the
configuration database
– No other computer requires any SQL Server 2008 components
• Configuration Database has been altered to be retained in two
instances: PHDCFG and PHDAPP
• A utility called the “Uniformance Database Server” is installed upon the
same computer - to run as a service - and all communication from any
R310 PHD software connects to this service so as to access the
22 9/2/2014
Lesson Topic – R310 Database Honeywell
• PHDCFG contains the configuration of the associated PHD Server
systems for the data collection side of the product
– PHDCFG instance is to be protected from any site customization
• PHDAPP contains the data collected using Event Journal Collection,
configuration and entries for PHD to Relational, Relational to PHD, Tag
Explorer custom directory groupings, Event Analyst tables, Advanced
Formula Manager tables and any site customization tables
• Tables inside PHDCFG have changed dramatically from the Oracle
structure – however, views have been created so that user queries that
currently call for data from Oracle can be converted over to using the
data views
• Current planning has only the PHDCFG instance experiencing internal
migration scripting for future releases with no scripted changes for
PHDAPP being expected
23 9/2/2014
Lesson Topic – PHD Server Honeywell
• Default component directories for installing PHD R310 software are
similar to those experienced with previous releases
• When starting PHD, the order of services has been altered to:
– RDI Server
– PHD Server
– API Server
– RAPI Server
• Note: If the SQL Server Configuration Database is installed upon the

same computer as the PHD Server, then UDBServer Service will be
started first
24 9/2/2014
Lesson Topic – Update for Base PHD Components Honeywell
• Uniformance Database Service (UDB)
• Uniformance System Console (USC)
• Uniformance System Monitor (USM)
• Integrated NT Security (INTS)
• PHD Configuration Tool (PCT)
– Using Honeywell’s Common Desktop Framework
• Registry entries replace command files
– PHD R300 onwards, NTSite folder no longer contains any command files
– PHD Server reads the .dat files and registry setting during system startup and
operation
• Computer Clustering supported
– Starting from PHD R300, failover clustering feature is introduced
• In event of failure on a computer in the cluster, automated failover to next
standby computer in the cluster occurs, so as to achieve maximum
availability of services and applications
25 9/2/2014
Lesson Topic – Uniformance Database Server Honeywell
• Uniformance Database Server component provides access to the
Uniformance PHD Server so that it can communicate with the
– Starting from PHD R300, it is no longer necessary to install any database
components upon any computer other than the computer hosting the PHD
• Uniformance Database Server is installed on the SQL Server 2008 host
computer and all calls for configuration database are directed through
this application
– Listens on default port setting of 53100
• Uniformance Database Server accepts connections from PHD Server
Services to access the configuration database
• All communications from the PHD configuration tool utilize this
connection to access the configuration database
• Runs under the local network services account – do not change this
setting
26 9/2/2014
Lesson Topic: Uniformance System Console Honeywell
• Starting from PHD R300, Uniformance System Console is a graphic
replacement for PHDMAN
– USC has a far greater functionality than was available through PHDMAN
• USC provides access to all PHD server services, their settings and ability to
control the system remotely from the physical computer
• Appropriate access privileges are required to control system and alter
configuration settings
• Built as a Microsoft Management Console add-in
• Makes connection to the PHDStart service which then transfers the
communication over to the other PHD services in review
• The functionality provides access to any PHD component system in the
environment using either trusted or non-trusted access connections
– When a trusted account is used for logging in to the computer, the credentials are
automatically passed over to the PHD service for connection authentication
– When an untrusted account is used for logging in to the computer, the user must enter
logon credentials so as to be validated by the remote PHD system
27 9/2/2014
Lesson Topic: Uniformance System Monitor Honeywell
• A basic version of Uniformance System Monitor (USM) is distributed as
part of PHD R310
– Configuration occurs on each computer where PHDStart is installed
• Each computer configuration is independent – communication between
computers utilizing USM is not supported with this basic version
• Configuration of the settings for USM is performed using the
Uniformance System Console
– Under System Monitoring option
• As per the USM presentation, templates, plugins, system summary
display and some monitor items (condition state, file size, monitor item
value, network ping, SNMP, WMI) are not available in embedded USM
28 9/2/2014
Lesson Topic: Integrated NT Security Honeywell
• Starting from PHD R300, the environment that PHD runs under is
essentially the INTS option from previous releases
• There are three groups created upon every computer where PHD
services are installed and users will need to be added to these for each
computer:
– Product administrators – full administrative capability
– Local engineers – authority to perform configuration in the database and run
updates to the PHD systems, permission to stop & start interfaces
– Local operators – ability to read configuration and view the PHD system
operation
• Tag Security roles are now related to local groups upon the computer
where SQL server is installed
– Domain users would be assigned to these groups for access to tags
29 9/2/2014
Lesson Topic: PHD Configuration Tool Honeywell
• PHD Configuration Tool is based on Honeywell’s Common Desktop
Framework
• PHD Configuration Tool accesses the SQL server database instances,
PHDCFG and PHDAPP for storage of any configuration performed
• When installed, the default expectation is the person utilizing the tool will
be logged on to the local computer with an account that can be
authenticated as a member of the product administrators or local
engineers upon the computer where the SQL server databases are
hosted
30 9/2/2014
Lesson Topic: PHD Application Server services Honeywell
• Following are some PHD Application Server services
– Consolidated Event Journal service – CEJServer
– NameSpace Server – NSServer
– PHD to Relational – PHDtoRel
– Uniformance Tag Synchronization – UnfTagSync
– Relational to PHD – Rel2PHD
• Note: Each of these services will be explained in detail, later in the

course
31 9/2/2014
Lesson Topic: Consolidated Event Journal Honeywell
• Starting from PHD R300, the Event Journal Collection application was
completely rebuilt
– Functionality remains essentially the same, in that data is collected from the
LCN History Module for the defined events that occur upon the LCN;
however the methodology is now functionally more similar to a realtime
interface than the unique service that existed for the previous releases
• An RDIServer application is installed as part of CEJ and runs
independently from the PHD installed service
• Data collected is now populated into the PHDAPP database – all that is
recorded in the PHDCFG database is the collection configuration and
information on the last time data was collected using CEJ
32 9/2/2014
Lesson Topic: Service Applications Honeywell
• NameSpace Server
– Holds the same functionality as existed in PHD R210,PHD R215 & PHD
R300 performing essentially the same mode of operation
• PHDtoRel
– Holds the same functionality as existed in PHD R210,PHD R215 & PHD
• TagSynch
– Holds the same functionality as existed in PHD R210, PHD R215 & PHD
• TagSynch also supports synchronizing from CSV files
• Rel2PHD
– Configuration requirement to identify the database to be connected to, the
account with database access, the tables and fields that will hold the data to
be collected
– More detailed information is in the RDI user guide
33 9/2/2014
Honeywell
This page intentionally left blank
34 9/2/2014
PHD Data Processing Overview
Introduction/Overview Copyright © 2013 Honeywell International Inc. PHD Data Processing Overview
35 9/2/2014
• Objective
– Recognize the purpose of the various PHD data processing options
• Topics
– System Components and Data Flow
– Gross Error Elimination
– Data Smoothing and Noise Gating
– Data Elimination Compression
– Data Quantizing and Scaling (Storage Format Compression)
– Confidence Factor
– Intelligent Data Retrieval:
• Time Weighted Data Reductions
• Interpolation and Extrapolation
• Engineering Unit Conversion
36 9/2/2014
System Components and Data Flow Honeywell
4 To service data requests,
PHD accesses the
End Users and Application Programs memory resident data
before going to the disk
Configured PHD Server Copy of

scan Real Time Database Config Data
MS SQL Server
frequency
per variable
4 Reference Database
RDBMS
Real Time Raw Data
SOURCE 1 Data Queue Queue Tag definitions and
SYSTEM Interface (RDI
Memory Resident Archive
other configuration data
or Link)
2 configured size
1 The RDI or Link places collected data

3 The PHD Continuous Store
for a tag in raw queue. The history
engine applies any user specified data
3 (CONSTORE) process
processing automatically extracts tag
PHD Disk Archives data from the data queue and
Flat Database writes it to disk at a
configured interval (typically
2 The data queue for each tag 10-30 minutes), applying any
user specified quantizing or
holds the processed data for Configured size and
n minutes. Generally the scaling
period is 3 times the Store number of files
Typically, PHD sites keep around five years of high
Interval resolution (scan rate) data online
37 9/2/2014
Front End Processing – Statistical Gross Error Elimination Honeywell
• Configuration Option – PHD evaluates values to eliminate random
instrumentation errors
– Performs linear regression on values before and after the value being
analyzed
– Determines standard deviation of surrounding values
– If the difference between value and regression line estimate is greater than
the threshold, the value is considered a gross error
– The system keeps an online log of gross errors
38 9/2/2014
Front End Processing – Statistical Gross Error Elimination Honeywell
• Tag Definitions:
– Gr Err Sigma Limit
• Number of standard deviations that the
tag can vary from the regression
estimate
– Typical Limit=3 to 5 and Default=0
• disables gross error detection for tag
– Gr Err Samples
• Total number of samples used for
regression estimate and standard
deviation
– Typical Samples = 6 or 8
– Example: Samples = 6
• 3 values prior and 3 values
after the value being evaluated
are used for the
regression/deviation estimate
39 9/2/2014
Front End Processing – Data Smoothing Honeywell
• Configuration option is used to minimize the
effect of random noise on measured values
– Smoothing Constant
• Exponential decay filter + feed forward
digital filter
• Value of 0.99 indicates maximum smoothing
Typical factor = 0.3 - 0.5
• Default = 0, no smoothing
• The smoothed value retains the confidence
of the original value
40 9/2/2014
Front End Processing – Noise Gating Honeywell
• Noise Gate Level
– Low noise threshold value (in EUs) below which values will be clamped to
zero
– 12% deadband built in to minimize chatter around threshold
– Be careful while using Noise Gate level setting
• If set to 0 this setting will affect calculations because it clamps every
value below 0 to 0
– For example -5 will be recorded as 0
41 9/2/2014
Data Elimination Compression Honeywell
• PHD data elimination compression reduces the volume of stored data by
eliminating redundant values and values that can be interpolated within
a specified tolerance
– The integrity and accuracy of the data are maintained
• PHD performs double and floating data type compression using
Honeywell’s constrained slope data compression methods
– If a data value can be successfully interpolated from surrounding data to
within a specific error tolerance, the data value is eliminated
• This error tolerance value is called the compression tolerance
– Non floating data type data is retained only on exception
• This is automatic and not configurable
• Note: In cases where you must preserve the shape of your data curve,
such as modeling for advanced process control, it may be necessary for
your PHD Manager to adjust the tag parameters that control this
processing option or disable it
42 9/2/2014
Data Elimination Compression, continued Honeywell
• PHD calculates the compression tolerance using the equation:
– Compression Tolerance = Tolerance x Compression Tolerance Factor
• Where Tolerance and Compression Tolerance Factor are values
specified in the tag configuration
43 9/2/2014
• Constrained Slope Data Compression Process
– PHD draws a line from the first stored value to each new value that is
received
44 9/2/2014
• Next, PHD checks each new value that is received to determine whether
it falls outside the + compression tolerance band
• PHD stores the first value found that falls outside the band
45 9/2/2014
• Then PHD draws a line from the newly stored value to each new value
that is received
– Values within the + compression tolerance band can be successfully
interpolated from the stored values and are eliminated
Values within the +

compression
tolerance band
46 9/2/2014
• Finally, PHD draws a new line from the newly stored value back to the
last stored value and checks all values between to ensure they are
within the compression tolerance band
• Values within the band can be successfully interpolated from the stored
values and are eliminated
• The process then begins again from the newly stored value
47 9/2/2014
• The constrained slope data compression process reduces the volume of
stored data while it maintains data integrity and accuracy
• One effect of the process is the storage sample rate is no longer
constant
– The sample rate varies with the dynamic range of the data
48 9/2/2014
• Because the storage sample rate varies with the dynamic range of the
data, the number of raw values you retrieve in a specified time interval
may be different for each tag
• If the number of values are different, the time stamps will not have a
one-to-one correspondence
49 9/2/2014
Data Quantization (Rounding) and Scaling Honeywell
• Specifies the precision with which to store a number (to
make more effective use of disk space for archive files)
– PHD can store floating point numbers as scaled 16-bit integer
values
• Low Extreme/Scale High Extreme = Lowest/Highest
possible value for tag
• Quantum = Scaling step size (steps from 0 to100)
– If a quantum is specified, incoming values are rounded to the
nearest quantum (step)
• A larger quantum yields greater compression, but
reduces the precision of the stored value
• (High Extreme-Low Extreme) / 65535 = minimum
quantum
• Quantum = -1 forces PHD to store a full 32 bit floating
representation of the number, rather than scaling it
50 9/2/2014
Future Reference – Tag Configuration Data Processing Parameters Honeywell
51 9/2/2014
52 9/2/2014
53 9/2/2014
Confidence Factor Honeywell
• All data within the PHD system have the following three attributes
– Time stamp: Timestamps in PHD R310 are internally stored as a 64-bit
number representing the number of seconds since midnight, 1st January,
1970
• Value – The value at the time indicated by the time stamp
• Confidence Factor – Indicates the “goodness” of the value
– Confidence factors range from -1 to 100
– For manual input tags and virtual calculations, the confidence factor can be
input with the value
54 9/2/2014
Confidence Factor Honeywell
55 9/2/2014
Confidence Factor -1 Honeywell
• Data unavailable from source system: point execution state inactive
ModTag
ModTag
replacement IE
Plug-in
56 9/2/2014
Confidence Factor 0 Honeywell
• Data clamped at low extreme value of 55
ModTag
ModTag
replacement IE
Plug-in
57 9/2/2014
Intelligent Data Retrieval Honeywell
• PHD provides application programs with built-in data manipulations and
calculations, thus simplifying application development and maintenance
– Data Reduction Calculations
– When requesting data from PHD, the application may request PHD
to perform data reduction calculations
• Data reductions reduce the amount of data to a subset of the
total raw samples
– Automatic Missing Data Interpolation and Extrapolation
– Automatic Engineering Unit Conversions
58 9/2/2014
Data Reduction Calculations Honeywell
• PHD supports data reductions for F (floating point), I (integer), D
(double), and L (long) data, including the following:
– Average: The average data over the reduction frequency (time range)
– Delta: The difference between the values at the end and start of the
reduction frequency (time range)
– First: The first actual (raw) value within the reduction frequency,
timestamped with the actual time
– Last: The last actual (raw) value within the reduction frequency,
timestamped with the actual time
– Maximum: The maximum value over the reduction frequency, timestamped
with the actual time of the maximum value
– Minimum: The minimum value over the reduction frequency, timestamped
with the actual time of the minimum value
59 9/2/2014
Data Reduction Calculations, continued Honeywell
• PHD supports the following data reductions for F (float) and D (double)
datatype tags only:
– Regression
• The regression slope (engineering units/sec) and intercept (estimated
value at the base time of midnight, 01-JAN-70) for the data within the
specified time range
– StDev
• The standard deviation of the data within the specified range
60 9/2/2014
Time Weighted Data Reductions Honeywell
• PHD calculates a time weighted value from the raw values in the time
interval for these reduction types:
– average, delta, delta at interval, maximum, maximum at interval, minimum,
minimum at interval, regression, and standard deviation
• The reductions return both a reduction value and a composite
confidence factor based on the reliability of the source data
61 9/2/2014
Time Weighted Average Confidence Factor Honeywell
• PHD calculates a time weighted average confidence factor for each
reduced value calculated using a time weighted average
62 9/2/2014
Data Retrieval Types Honeywell
• Raw
– Retrieves the actual sample stored with its timestamp, does not include
interpolation
• If the actual sample is not there during the time frame, it returns the
nearest actual samples
• Interpolated Raw
– If RDI returns NaN ( Not a Number), confidence -1, then PHD interpolates
the data value giving it a confidence of 0
• Snapshot
– Interpolates raw data at the sample frequency you request
– Raw data that exist at specific timestamps are retrieved
• Other values are interpolated according to the tag configuration
63 9/2/2014
Data Retrieval Types Honeywell
• Reductions (for floating point and integer data)
– Average, Delta, and Delta at interval
– Maximum, Maximum at interval
– Minimum, Minimum at interval
– Regression and Standard Deviation
– First, First At Interval, Last, and Last At Interval
• Note:
– Tag configuration of interpolation method (linear, which is the default, or
step) affects all reduction results and resample method (Sample at Interval
or Average Around Interval) affects the results when resampled data are
reduced
– Interpolation method also affects data elimination compression
• If the interpolation method for a tag is changed from step to linear, data
may be misrepresented upon retrieval
64 9/2/2014
Data Retrieval Types, continued Honeywell
• Uniformance Process
Studio(UPS) data retrieval
types for Trends:
• Note:
– UPS is a separate
application suite and is not
supplied with as part of any
PHD release
– It is a thick client solution
that allows visualization of
PHD data
65 9/2/2014
Interpolation and Extrapolation Honeywell
• PHD automatically performs interpolation
estimates for missing data segments between
known (stored) values
• PHD R310 onwards, the behavior of PHD has
been modified to perform a linear interpolation
for float and double tags that have no
interpolation method defined
• PHD performs an automatic extrapolation for
data requests that are beyond the limits of
data available for a tag
• Extrapolation for times prior to or after known
data use exponential
damping between the last known slope of the
data and the overall trend of the data
• These extrapolation characteristics are
configurable on a per-tag (or class-tag) basis:
– Last known value extrapolation
– Last known slope extrapolation
– Damped extrapolation
• Damped extrapolation is a combination of
value and slope extrapolations or the mean
of both at a point in time
66 9/2/2014
PHD Data Representation Honeywell
• Confidence factor for data between stored values
– Either the confidence of the previous value or the minimum confidence of
stored values are used in a linear interpolation
67 9/2/2014
Effect of Interpolation Method on Compression Honeywell
• Interpolation Method also affects data elimination compression
– If the Interpolation Method for a tag is changed from Step to Linear, data
may be misrepresented upon retrieval
68 9/2/2014
Reference - Reduction Types Honeywell
69 9/2/2014
Reference - Reduction Types, continued Honeywell
70 9/2/2014
Data Retrieval - Date and Time Examples Honeywell
71 9/2/2014
Data Retrieval - Date and Time Examples, continued Honeywell
• Examples:
– NOW – 1W:One week ago from the current date/time
– TODAY – 1W4H:One week and 4 hours prior to today at midnight
– NOW – 1D+1M:Current date/time less one day plus 1 minute (R202+)
– TODAY – 1D+1S:Yesterday at 12:00:01 AM (R202+ )
• Note:
– Mo in PHD = 30 day month
72 9/2/2014
Automatic Engineering Unit Conversions Honeywell
• When an application program requests
data from PHD, it is possible to specify the
units it requires
– PHD converts the units from those stored
with the tag into the requested units,
eliminating having to build conversion
functions into the various user tools and
applications
• A tag can be defined with any unit
code, but is convertible by PHD only if
it makes use of PHD base units
(standard or user-configured)
• A valid convertible unit contains one or
two base units combined in one of the
following ways:
– baseunit
– baseunit/constant
– baseunit1/baseunit2
– baseunit/timeunit
– See PHD User Guide, “PHD Engineering
Units” and PHD System Manual,
“Automatic Unit Conversion”
73 9/2/2014
Honeywell
This page intentionally left blank
74 9/2/2014

Introduction-Overview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction-Overview

Uploaded by

Copyright:

Available Formats

PHD Introduction

Experion Link RDI

• Based on the tag configuration, tag values are

End Users and Application Programs

APP- Application Database

End Users and Application Programs

APP- Application Database

MS SQL Server Hard Disk

– Edit an existing data value located in the queue or archive file

– Download a data value from the queue to the PHD Server

– All of the above

End Users and Application Programs

• A Shadow PHD server receives

• The configuration data for the PHD

• The PHD servers from which the

•Typically, a Shadow system is

• Windows 2008 (x86) Windows 2008 (x64)

System Console Visual PHD

Port 3100 Port 3100 PHD Manager

RDI/ Link Uniformance

Experion, OPC, LxS OLE DB

*- PHDStart Service connects to all other services

System Console Visual PHD

Port 3100 Port 3100 PHD Manager

RDI/ Link Uniformance

Experion, OPC, LxS OLE DB

*- PHDStart Service connects to all other services

Port 3100 Port 3100 PHD Manager

RDI/ Link Uniformance

Experion, OPC, LxS OLE DB

*- PHDStart Service connects to all other services

• Note: If the SQL Server Configuration Database is installed upon the

• Note: Each of these services will be explained in detail, later in the

This page intentionally left blank

Configured PHD Server Copy of

1 The RDI or Link places collected data

Values within the +

This page intentionally left blank

You might also like