APC-4500VE SECCION 7. PROFIT CONTROLLER. Instalacion

Profit® Viewer - Profit Controller - Profit Optimizer - Profit Toolkit –
Profit Bridge – Profit SensorPro – Profit Design Studio – Profit Assistant
Profit Suite
Installation Guide
for Open Systems
Rev 2.0
08/02
RM20-501
Copyright, Notices, and Trademarks
Printed in U.S.A. – © Copyright 2001 by Honeywell International Inc.
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 customer.
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.
Profit, TDC 3000 and TotalPlant are U. S. registered trademarks of Honeywell International Inc.
Other product names are trademarks of their respective owners.
Honeywell
Industry Solutions
16404 North Black Canyon Highway
Phoenix, AZ 85053-3095
ii Profit Suite Installation Guide 8/02

Honeywell
Table of Contents
SECTION 1 — BEFORE YOU BEGIN................................................................................. 1

1.1 Overview........................................................................................................... 1
1.2 Profit Suite Component Overview .................................................................... 2
1.3 Installation Overview ........................................................................................ 4
1.4 TPS Node Installation Overview ...................................................................... 5
1.5 Non-TPS Node Installation Overview............................................................... 7
1.6 Hardware and Software Requirements ............................................................ 8
SECTION 2 — PREPARING FOR INSTALLATION ......................................................... 11
2.1 Overview......................................................................................................... 11
2.2 Shutdown Applications and Services ............................................................. 12
2.3 Uninstall Previous Releases .......................................................................... 14
SECTION 3 — INSTALLING PROFIT TPS SERVER FILES............................................ 15
3.1 Overview......................................................................................................... 15
3.2 Installing Profit TPS Server Files ................................................................... 16
SECTION 4 — INSTALLING EMBEDDED PHD COMPONENTS.................................... 18
4.1 Overview......................................................................................................... 18
4.2 Installing Embedded PHD Server .................................................................. 19
4.3 Installing PHD Patch ...................................................................................... 24
4.4 Installing Honeywell Uniformance Desktop.................................................... 25
SECTION 5 — INSTALLING MICROSOFT SYSTEM FILES ........................................... 31
5.1 Overview......................................................................................................... 31
5.2 Microsoft System Files – Installation Steps.................................................... 32
SECTION 6 — INSTALLING HCI RUNTIME .................................................................... 38
6.1 Overview......................................................................................................... 38
6.2 HCI Runtime – Installation Steps ................................................................... 39
SECTION 7 — INSTALLING PROFIT VIEWER AND PROFIT TRENDER ...................... 40
7.1 Overview......................................................................................................... 40
7.2 Installing and Configuring Profit Viewer ......................................................... 41
SECTION 8 — INSTALLING PROFIT CONTROLLER (RMPCT) .................................... 44
8.1 Overview......................................................................................................... 44
8.2 Installing and Configuring Profit Controller..................................................... 45
8/02 Profit Suite Installation Guide iii

Honeywell
Table of Contents
8.3 Initializing Profit Controller’s Messages ......................................................... 50

SECTION 9 — INSTALLING PROFIT OPTIMIZER.......................................................... 51
9.1 Overview ........................................................................................................ 51
9.2 Installing and Configuring Profit Optimizer .................................................... 52
9.3 Initializing Profit Optimizer’s Messages ......................................................... 57
SECTION 10 — INSTALLING PROFIT TOOLKIT .......................................................... 58
10.1 Overview ........................................................................................................ 58
10.2 Installing Profit Toolkit Applications ............................................................... 59
10.3 Installing the FCCU Modeling Spreadsheet .................................................. 64
10.4 Initializing Profit Toolkit’s Messages .............................................................. 65
SECTION 11 — INSTALLING PROFIT BRIDGE............................................................ 66
11.1 Overview ........................................................................................................ 66
11.2 Profit Bridge Installation Scenarios................................................................ 68
11.3 Installing Profit Bridge .................................................................................... 70
11.4 Installing Profit Controller Gain Mapper and Profit Optimizer Gain Mapper.. 74
SECTION 12 — INSTALLING PROFIT SENSORPRO................................................... 76
12.1 Overview ........................................................................................................ 76
12.2 Installing Profit SensorPro ............................................................................. 77
SECTION 13 — INSTALLING PROFIT DESIGN STUDIO ............................................. 81
13.1 Overview ........................................................................................................ 81
13.2 System and Software Requirements ............................................................. 82
13.3 Quick Reference to Installation...................................................................... 83
13.4 Installing the Profit Design Studio.................................................................. 84
SECTION 14 — INSTALLING PROFIT ASSISTANT ..................................................... 92
14.1 Overview ........................................................................................................ 92
14.2 Installing ProfitAssistantAddin ....................................................................... 94
14.3 Installing ProfitAssistant................................................................................. 97
SECTION 15 — INSTALLATION WRAP-UP ................................................................ 102
15.1 Starting Services.......................................................................................... 102
SECTION 16 — BRINGING PROFIT CONTROLLER ONLINE................................... 103
16.1 Overview ...................................................................................................... 103
16.2 Installing Off-Line Design Files .................................................................... 105
16.3 Removing Controllers .................................................................................. 107
16.4 Activating the Program and Reading In the Design Files ............................ 108
iv Profit Suite Installation Guide 8/02

Honeywell
Table of Contents
SECTION 17 — BRINGING PROFIT TOOLKIT ONLINE ............................................. 111

17.1 Bringing Profit Toolkit Online........................................................................ 111
SECTION 18 — SECURITY ........................................................................................... 113
18.1 Overview....................................................................................................... 113
18.2 Application Security...................................................................................... 114
18.3 Security Role Configuration.......................................................................... 115
18.4 TPS Domain Security ................................................................................... 117
18.5 Security Scenario TPS Domains – Application Security and Security Role
Configuration ............................................................................................................ 122
18.6 Non-TPS Domain Security ........................................................................... 125
18.7 Security Scenario Non-TPS Domains – Application Security and Security
Role Configuration .................................................................................................... 129
APPENDIX A — DATAPOOL DESCRIPTIONS............................................................. 133
A.1 Datapool Overview ....................................................................................... 133
A.2 Profit Controller Datapool Parameters ......................................................... 134
A.3 Profit Optimizer Datapool Parameters ......................................................... 153
A.4 Profit Toolkit Datapool Parameters .............................................................. 163
APPENDIX B PROFITSUITE CONFIGURATION FILES ............................................... 172
B.1 Configuration File Structure.......................................................................... 172
B.2 OPC Servers / DssOPCLink ........................................................................ 180
APPENDIX C – INSTRUCTIONS FOR COLLECTING DATA THROUGH ORACLE-
BASED PHD ONLY............................................................................................................... 191
C.1 Interfacing Profit Controller/Optimizer/Toolkit to PHD.................................. 191
C.2 Building the Oracle-based PHD Database for Profit Controller ................... 198
C.3 Configuring Oracle-based PHD for Profit Controller .................................... 204
C.4 Synchronizing RDI Execution with Controller MV Interface Points .............. 206
C.5 PHD Security Groups ................................................................................... 208
APPENDIX D – SERVER REGISTRAR/REGISTERING AN APPLICATION ................ 209
D.1 Using the Server Registrar ........................................................................... 209
D.2 Registering an Application............................................................................ 211
D.3 Modifying an Existing Application................................................................. 213
D.4 Profit Assistant Configuration ....................................................................... 216
D.5 Application Security Settings........................................................................ 217
D.6 Viewing a Registered Application................................................................. 222
D.7 Activating/Inactivating a Registered Application .......................................... 223
D.8 Terminating a Registered Application .......................................................... 224
D.9 Removing a Registered Application ............................................................. 225
8/02 Profit Suite Installation Guide v
Honeywell
Table of Contents
D.10 Sorting the Non-Registered or Registered Applications .............................. 226

APPENDIX E — USING THE SPECIAL TASK MANAGER.......................................... 227
E.1 Privtaskmgr.exe (Formerly TaskMgr_ed.exe) ............................................. 227
RD
APPENDIX F — USING DSS RDI, RDI SERVER TO COMMUNICATE WITH 3 PARTY
SYSTEMS………. ................................................................................................................. 231
F.1 Overview of DSS RDI and RDI Server ........................................................ 231
F.2 Installation Considerations........................................................................... 233
F.3 How RDI Server is configured to Get/Put Parameters ................................ 234
F.4 How to View the Detailed Status of RDI Server .......................................... 236
APPENDIX G — PROFIT SUITE INTEGRATION WITH ALERT MANAGER............... 238
G.1 Overview of DSS2SFF and Alert Manager .................................................. 238
APPENDIX H — PROFIT SUITE EMBEDDED HISTORY ............................................. 239
H.1 Overview ...................................................................................................... 239
H.2 Troubleshooting ........................................................................................... 241
H.3 “Interesting” Features .................................................................................. 242
H.4 Detailed Description of “Update History” Function ...................................... 248
H.5 Profit Suite Embedded PHD Data Retrieval Configuration Example........... 249
vi Profit Suite Installation Guide 8/02

Honeywell
About This Publication
Purpose This book explains how to install the following products or components.
· Profit TPS Server Files
· Embedded PHD Components
· Microsoft System Files
· HCI Runtime (for Non-TPS Systems)
· Profit Viewer and Trender
· Profit Controller
· Profit Optimizer
· Profit Toolkit Applications
· Profit Bridge
· Profit SensorPro
· Profit Design Studio
· Profit Assistant
Release This document, Revision 2.0, is for:
Information
· Profit Controller software R205.00 and above,
· Profit Optimizer software R205.00 and above,
· Profit Toolkit software R205.00 and above,
· Profit Assistant software R205.00 and above,
· Profit Viewer software R205.00 and above,
· Lab Update software R205.00 and above and
· Profit Design Studio 235 and above.
For additional release information, or releases after R205, see the Release Notes.
Who Should Use Anyone responsible for installing the Profit software can use this book.
This Book
Other Books in See the user’s guides for help with field definitions on the graphics. See
the Profit Library “References” later in this section for a list of other publications.
8/02 Profit Suite Installation Guide vii

About this Publication
Profit Course Honeywell offers several courses that explain the math and conceptual
Information underpinnings of Profit Controller (RMPCT) as well as application
implementation of the Advanced Process Control suite of products.
Engineers wanting a more technical exposure to Profit Controller can contact:
Honeywell Automation College
2500 W. Union Hills Dr.
Phoenix, AZ 85027
Phone (602) 313-5669
(800) 852-3211
viii Profit Suite Installation Guide 8/02

About This Publication
Writing The following writing conventions have been used throughout this book and
Conventions Used
in This Book other books in the Profit Suite library.
§ Words in double quotation marks " " name sections or subsections in this
publication.
§ Words in italics name book titles, add grammatical emphasis, introduce
words that are being referenced or defined, or represent mathematical
variables. The context makes the meaning and use clear.
§ Words in bold type indicate paragraph topics or bring important phrases to
your attention.
§ Shading brings paragraphs and table entries to your attention.
§ Windows pull down menus and their options are separated by an angle
bracket >. For example, Under Settings> Communications, set the baud rate.
§ Messages and information that you type appear in Courier font.
§ Acronyms, Scan parameters, point names, file names, and paths appear in
UPPERCASE. The context makes the meaning and use clear.
§ Command keys appear in UPPERCASE within angle brackets. For example,
press <ENTER>.
§ TPS user station touch-screen targets appear in rounded boxes. For example,
MODIFY NODE
touch .
§ Graphic buttons appear in UPPERCASE within brackets [ ]. For example,
touch [TAG].
§ Point-dot-parameter means a point name and one of its parameters. For
example, point-dot-SP means the SP parameter for the point.
§ Zero as a value and when there is a chance for confusion with the letter O is
given as Ø. In all other cases, zero as a numerical placeholder is given as 0.
For example, 1.0, 10, 101, CVØ1, parameter PØ.
§ The terms screen and display are used inter changeably in discussing the
graphical interfaces. The verbs display a screen and call a screen are also
used inter changeably.
§ These names, and may be used interchangeably.
Former Name Product Name
RMPCT Profit Controller
DQP Profit Optimizer
APC Development Environment or APCDE Profit Design Studio
RPID Profit PID
8/02 Profit Suite Installation Guide ix

Honeywell
References
Documentation The following documents comprise the Profit Suite library.

Title Number
General
Profit Controller (RMPCT) Concepts Reference RM09-400
Profit Controller (RMPCT) Designer’s Guide (Off-Line Design) RM11-410
Profit Optimizer Designer’s Guide (Off-Line Design) PR11-400
Profit Toolkit Designer’s Guide AP11-400
APC Identifier User’s Guide AP09-200
Profit Loop User’s Guide RM11-110
Profit-PID (RPID) User’s Guide RM11-100
Open
Profit Suite Installation Guide for Open Systems RM20-501
Viewer - Controller - Optimizer - Toolkit
Profit Controller (RMPCT) User’s Guide for Open Systems RM11-401
Profit Assistant User’s Guide RM11-441
Profit Optimizer User’s Guide for Open Systems PR11-421
Profit Trender User’s Guide RM11-431
Profit Toolkit User’s Guide for Open Systems AP11-401
Profit Toolkit Function Reference AP11-410
FCCU Toolkit User’s Guide for Open Systems AP13-201
Fractionator Toolkit User’s Guide for Open Systems AP13-101
Lab Update User’s Guide AP13-111
Wrapper Builder User’s Guide AP11-411
Profit Bridge User’s Guide AP20-401
Profit SensorPro User's Guide PS11-100
Profit Stepper User’s Guide
TPS System
Profit Controller (RMPCT) Installation Reference for AM, AxM and Open LCN-Side RM20-400
Profit Controller (RMPCT) Commissioning RM20-410
Profit Controller (RMPCT) User’s Guide for AM, AxM and Open LCN-Side RM11-400
Profit Optimizer Installation Reference for AM and Open LCN-Side PR20-400
Profit Optimizer User’s Guide for AM and Open LCN-Side PR11-420
Profit Suite ToolKit AP09-300
TDC Data Converter Performance Monitor Simulation BackBuilder
Data Collector RMPCT Cascade Gain Scheduler
Step Test Builder PV Validation
Fractionator Toolkit (LCN) AP13-100
FCCU Toolkit (LCN) AP13-200
Furnace Pass Balance Temperature Control User’s Guide AP13-600
Non-Linear Level Control User’s Guide AP09-700
Embedded Uniformance
Excel Companion User’s Guide (Profit Embedded PHD) AP20-510
Power Point Companion User’s Guide (Profit Embedded PHD) AP20-520
Process Trend User’s Guide (Profit Embedded PHD) AP20-530
x Profit Suite Installation Guide 8/02

Honeywell
References
Release Notes
Documentation The following Release Notes are available for the Profit Suite Product Line.
Title
Profit Controller/Profit Viewer/Profit Trender Release Notes
Profit Controller (LCN) Release Notes
Profit Optimizer (Open) Release Notes
Profit Optimizer (LCN) Release Notes
Profit Assistant Release Notes
Profit Stepper Release Notes
Profit Bridge Release Notes
Profit SensorPro Release Notes
Profit Design Studio Release Notes
FCCU Toolkit Release Notes
Fractionator Toolkit Release Notes
Lab Update Release Notes
Wrapper Builder Release Notes
Profit PID Release Notes
Profit Loop Release Notes
Profit Suite Toolkit Release Notes
8/02 Profit Suite Installation Guide xi

Honeywell
For Technical Assistance
If You Need If you need technical assistance, contact your local Honeywell Service
Assistance Organization, as explained in the following paragraphs.
International Outside of the United States, contact your local Honeywell Service Organization.
Customers If you are not sure of the location or telephone number, call your Honeywell
representative for information.
Customers Inside Within the United States, call the Technical Assistance Center (TAC) at the toll
the United States free number 1-800-822-7673.
Arizona Within Arizona, the local number for TAC is 602-313-5558.
Customers
Services Provided Calls to TAC are answered by a dispatcher from 6:00 A.M. to 4:00 P.M.,
Mountain Standard Time.
Outside of these hours, emergency calls—those that affect your ability to control
or view a process—will be received by an answering service, and returned within
one hour. TAC maintains its own TPS network, and frequently can duplicate
problems on this equipment.
Time Saving Tip It is a good idea to make specific notes about the problem before making the call.
This helps to reduce delays and expedite answers.
xii Profit Suite Installation Guide 8/02

Honeywell
Section 1 — Before You Begin
1.1 Overview
Scope of this This section reviews the hardware, software, and network configuration
Document
requirements for implementing Profit® Viewer, Controller, Optimizer and
Toolkit on Windows NT 4.0 and Windows 2000.
Check the Details Hardware communication errors, configuration errors, and insufficient system
resources can delay getting your controller online.
TPS System vs. Please note that the terms TPS system and TDC 3000 are used interchangeably.
TDC 3000
TPS system is the evolution of TDC 3000.
Terminology
08/02 Profit Suite Installation Guide 1

Honeywell
1.2 Profit Suite Component Overview
Profit Suite The following is a list of the software components that make up Profit Suite, along
Software
with descriptions of each component.
Components
Profit TPS Server This component is installed on the Primary TPS Domain Controller node. It installs
Files
the files required to support the R205 security functionality.
Embedded PHD This component is installed on each node running Profit Controller and Profit
Optimizer. It installs PHD Server and uses a Microsoft Access Database instead of
Oracle. Embedded PHD allows you to historize controller, optimizer and toolkit
parameters. If PHD Server 150.1 is currently installed on the node, do not install
this component. Although this component is optional, it is highly recommended
that it be installed to support future Profit Suite product enhancements and tools.
Note: PHD Server must be installed prior to installing Uniformance Desktop.
PHD Patch This package installs selected released patches for the PHD Server 150.1 and must
be installed after the Embedded PHD installation.
Uniformance This component can be installed on each client node subject to license agreements.
Desktop R160
NOTE: Due to differences in the Microsoft Access versus Oracle Databases, all
Uniformance Desktop functions are not supported by Embedded PHD. Refer to the
documentation for further information.
Microsoft The Microsoft System Files must be updated on each node on which Profit Suite
System Files
software is being installed and will require a reboot on Windows NT.
HCI Runtime HCI Runtime is a required update for R205. The required version is already
installed in Honeywell TPS GUS 210 (and later) and APP 120 (and later) nodes.
Profit Viewer Profit Viewer is the main engineer’s display for Profit Controller, Optimizer and
Toolkit applications. It can be run on a GUS or APP node and other client machines.
The Profit Viewer installation also installs Profit Trender – a tool for trending past,
current and future values for controller variables.
Profit Controller Profit Controller provides the multivariable predictive control software.
Note: It can not be installed on Honeywell TPS system GUS nodes.
Profit Optimizer Profit Optimizer provides the capability to coordinate and optimize the operating
targets for multiple Profit Controllers. Profit Optimizer can be installed on the same
node as the Profit Controllers, or on its own node.
Profit Assistant Profit Assistant is the operator’s interface to Profit Controller. It has a significant
amount of monitoring and diagnostics information presented in a single page. It can
be installed on the same node as the controller and on client nodes.
Profit Stepper Profit Stepper is a powerful process stepper, data collection and model identification
tool. Its goal is to produce better models and reduce step testing and commissioning
time.
2 Profit Suite Installation Guide 8/02

Honeywell
Section 1 – Before you Begin
1.2 Profit Suite Component Overview
Profit Bridge Profit Bridge automates the on-line updating of process model gains in Profit
Controller and Profit Optimizer applications. Part of this product is installed on the
same node as the controllers and optimizers and part is installed on the node with the
process modeling software.
Profit SensorPro Profit SensorPro is a multivariable analysis/regression package that supports the
creation of static models for prediction purposes. These models can be used stand
alone or in conjunction with any appropriate Profit Suite component.
Profit Toolkits The Toolkit suite provides a variety of calculations and functions to support control
strategies. The suite includes FCCU Toolkit, Fractionator Toolkit, Lab Update, and
Wrapper Builder.
Profit Design Profit Design Studio is the off-line builder for Profit Suite Controllers, Optimizers
Studio and Toolkits. It includes tools for model identification and history collection
configuration. This component requires installation of a hardware dongle and related
software.
Honeywell TPS The *.lcn is an emulated Bernoulli file that contains the graphics, CL and CDS files
System files
for viewing and manipulating controllers from a Honeywell TPS Native Window.

Honeywell
1.3 Installation Overview
Installation The next two subsections give an overall picture of the installation steps for
Overview
controller and client nodes for Honeywell TPS systems and non-TPS systems
on Windows NT 4.0 and Windows 2000 platforms. The overview will direct
the user to other sections of the manual for detailed installation instructions for
each software component.
Warning! This release will require several reboots of the node, especially if the
installation is on a Windows NT node. If the node is already functioning as a
control node on your process, take appropriate actions to allow this node to go
offline. Software requiring reboots has been identified, however, additional
reboots may be required if locked files are detected during the install. This will
occur if applications and services have not been shutdown and disabled prior to
installing the software.
Important · For upgrades from previous installations, refer to the Release Notes for
Considerations
additional instructions.
· Because of the software dependencies, it is recommended that the software
be installed in the order listed.
· Depending on your control strategy, all of the components may not be
required.
Target Node The installation steps will vary depending upon the type of node the software
will be installed on:
· For TPS nodes, refer to Section 1.4 TPS Node Installation Overview.
Included here are the Primary TPS Domain Controller, APP and GUS
nodes.
· For non-TPS nodes, refer to Section 1.5 Non-TPS Node Installation
Overview.

Honeywell
1.4 TPS Node Installation Overview
Primary TPS 1. Install Profit TPS Server files on the Primary TPS Domain Controller. (See
Domain Controller
Section 3)
Note: This installation is new for R205 and is required on Honeywell TPS
systems.
APP Node 1. Check hardware and software requirements. (See Section 1.6)
2. Prepare node for software installation (See Section 2)
· Shutdown existing applications and services (See Section 2.2)
· Check the timestamp of Program Files\Honeywell\TPS\HCI
Runtime\gopc.dll. If the timestamp is earlier than the dates listed
below, the HCI Runtime will need to be upgraded.
1. Windows NT nodes – gopc.dll dated 1/10/01 or later.
2. Windows 2000 nodes – gopc.dll dated 1/9/02 or later.
Note: The HCI Runtime files included on the R205 Profit Suite CD
are for Non-TPS system nodes only. If the HCI components on a
TPS system node need to be upgraded, refer to the TPS System
Implementation Guide and perform the install using the
appropriate version of the TPS System Software CD for your site.
· Uninstall previous releases. (See Section 2.3)
3. Install Embedded PHD (optional, but recommended), but do not reboot at
this time. Change the PHD Service Startup to Manual. (See Section 4)
4. Install PHD Patch (required if Embedded PHD installed). (See Section 4)
5. Install Uniformance Desktop (optional). (See Section 4)
6. Install the Microsoft System Files (required). (See Section 5)
7. Install Profit Viewer. (See Section 7)
8. Install Profit Controller. (See Section 8)
9. Install Profit Optimizer. (See Section 9)
10. Install Profit Toolkits. Included here are FCCU Toolkit, Fractionator
Toolkit, Lab Update, and Wrapper Builder. (See Section 10)
11. Install Profit Bridge (See Section 11)
12. Install Profit SensorPro (See Section 12)
13. Install Profit Design Studio (optional on this node). (See Section 13)
14. Install Profit Assistant (optional). (See Section 14)
15. Start the TPS Admin service and set the Startup to Automatic. (See Section
15)
16. Start the Honeywell PHD service and set the Startup to Automatic (if
installed). (See Section 15)

Honeywell
Section 1- Profit Suite Component Overview
1.4 TPS Node Installation Overview
GUS Node 1. Check hardware and software requirements. (See Section 1.4)
2. Prepare node for software installation. (See Section 2)
· Shutdown existing applications and services. (See Section 2.2)
below, the HCI Runtime will need to be upgraded.
Note: The HCI Runtime files included on the R205 Profit Suite CD
are for Non-TPS system nodes only. If the HCI components on a
TPS system node need to be upgraded, refer to the TPS System
Implementation Guide and perform the install using the
appropriate version of the TPS System Software CD for your site.
4. Install the Microsoft System Files. (See Section 5)
7. Install Profit Design Studio (optional). (See Section 13)
8. Start the TPS Admin service and set the Startup to Automatic. (See Section
15)

Honeywell
1.5 Non-TPS Node Installation Overview
Non-TPS System 1. Check hardware and software requirements. (See Section 1.6)
Node
2. Prepare node for software installation. (See Section 2)
· Shutdown existing applications and services. (See Section 2.2)
below, the HCI Runtime will need to be upgraded. For non-TPS
nodes, the HCI Runtime can be upgraded using the HCI files included
on R205 Profit Suite CD. Before upgrading, shutdown all Profit Suite
applications and deinstall HCI Runtime. (See Section 2)
3. Install Embedded PHD (optional but recommended) but don’t reboot at this
time. Change the PHD Service Startup to Manual. (See Section 4)
4. Install PHD Patch (required if Embedded PHD installed). (See Section 4)
6. Install the Microsoft System Files (required). (See Section 5)
7. Install HCI Runtime and reboot (required). (See Section 6)
9. Install Profit Controller. (See Section 8)
10. Install Profit Optimizer. (See Section 9)
11. Install Profit Toolkits. Included here are FCCU Toolkit, Fractionator
Toolkit, Lab Update, and Wrapper Builder. (See Section 10)
12. Install Profit Bridge. (See Section 11)
13. Install Profit SensorPro. (See Section 12)
14. Install Profit Design Studio (optional on this node). (See Section 13)
16. Start the Honeywell PHD service and set the Startup to Automatic (if
installed). (See Section 15)

Honeywell
1.6 Hardware and Software Requirements
Requirements These are the hardware and software requirements.
Minimum Requirement
Hardware Pentium II 266 MHz with 128 Mbytes of RAM configured with at least:
30 Mbytes of disk space available for the first Profit Suite installation and an
additional 5Mbytes for each incremental installation.
10 Mbytes for Embedded PHD.
35 Mbytes for Uniformance Desktop
15 Mbytes for Profit Design Studio
Note Hard drives must be formatted NTFS (NT file system) before the installation of Profit
Controller or Profit Viewer.
Use the “Convert” command to convert a file system to NTFS.
Click Start>Programs>Command Prompt.
Type convert c:fs:ntfs where c is the drive you want to convert.
Software Microsoft Window NT 4.0 with SP5 or SP6a
Microsoft Windows 2000 with SP1 or SP2
Internet Explorer Version 5.5 SP1
For APP Nodes – see Release Notes.
Windows To install the off-line software, controller and display software, you must have
NT Access Administrator privileges on the PC.
Security Note To support inter-process communications, Profit Suite applications are registered as
Microsoft Distributed Component Object Model (DCOM) servers under Windows
NT or Windows NT Server. To support open but secure inter-process
communications, DCOM enforces various registration requirements. In order to
comply with these requirements, Profit Suite applications are configured to execute
as a specific NT user. For convenience this user is created by installation software.
The identity of this user depends on the environment in which the Profit Suite is
installed.

Honeywell
Three distinct environments and three different users are possible:

1) TPS Domain - Profit Suite software is installed in a TPS domain generally on
a GUS or APP Node (note that Profit Controller, Profit Optimizer and Profit
Toolkits do not run on a GUS). The TPS system installation software
provides the domain user: TPSComServer. TPSComServer is configured
such that no interactive user can log in as this user. Only programs can use
this identity. Therefore, TPSComServer's password is automatically
assigned at install time and should never be changed. An unchanging
password is crucial for maintaining systems utilizing DCOM servers because
the user id and password are specified in the registration of each server.
DCOM servers supporting the Honeywell Communications Infrastructure
(HCI components) generally are configured to run as TPSComServer. When
Profit Suite applications are executed in a TPS Domain, they are HCI
Components and are configured to execute as TPSComServer.
2) NT Server without TPS Domain
Profit Suite applications to be executed on an NT Server serving as the
Primary or Backup Domain controllers for an NT Domain must be configured
to run as a Domain - not a local - user. In this configuration, Profit Suite
installation software creates the user ProfitComServer in the domain. Like
the TPSComServer referenced in 1) above, this user cannot be used for
interactive login, its password is assigned at creation time, and its password
should not be changed. In order for the installation software to
successfully perform this task, you must log in as a user with domain
administration privileges the first time any Profit Suite software is
installed in the domain. Also, install software onto the Primary Domain
Controller prior to installing on other nodes. This way the ProfitComServer
user id will be present prior to installations performed on NT workstations
belonging to the domain.
3) NT Workstation only
Profit Suite is to be executed on NT workstations belonging to a workgroup
or belonging to a domain in which no TPS domain software is present AND
no Profit Applications are executed on the Primary or Backup domain
controller for the domain. In this configuration, no domain users are
necessary. Therefore, the Profit Suite installation software creates the local
NT user: ProfitUser on each node where Profit software is installed. This user
is also unavailable for interactive log in, has its password assigned at
installation time, and should never have its password changed. In this
configuration all Profit Suite applications are configured to run as the local
user ProfitUser.

Honeywell
Local/Remote The following table defines various ways you can run and view Profit Controller,
Workstations
Profit Optimizer, and Profit Toolkit, and what needs to be installed on the given
and What to
Install workstation to accommodate that requirement.
Install Profit Install Profit Install Profit
If you want to Controller/ Optimizer Viewer
Toolkit
Run Profit Controller/Toolkit at the local workstation X
View Profit Controller/Toolkit running at another
X
workstation
View Profit Controller/Toolkit running at the local X
X
workstation
Run Profit Optimizer at the local workstation X
View Profit Optimizer running at another workstation X
View Profit Optimizer running at the local workstation X* X X
· Only needs to be installed if Profit Optimizer is optimizing a Profit Controller on the local workstation.

Honeywell
Section 2 — Preparing for Installation
2.1 Overview
New Installations For first time installations of Profit Suite, the node should be checked to meet the
minimum hardware/software requirements. The node should already be a member
of the domain or TPS Domain if applicable.
Upgrades Although sections of this document point out procedures that pertain to system
upgrades, it is critical to follow the procedures in the Release Notes for specific
tasks to upgrade to this release.
Warning! This release will require several reboots of the node. If this node is already
functioning as a control node on your process, take appropriate actions to allow
this node to go offline.
Administrator To install Profit Suite components, you must minimally be able to log in as the
Permission local administrator. For TPS Systems, the TPS Administrator account is
Required recommended. Refer to the security note in Section 1.6 Hardware and Software
Requirements for discussion of the different system configurations and account
requirements.

Honeywell
2.2 Shutdown Applications and Services
Shutdown Profit Applications configured to use the Embedded PHD functionality will have
Existing their processes launched by the history collection cycle. Turn off the PHD Server
Embedded PHD prior to terminating Profit Suite applications.
Service
1. On Windows NT, click on Start>Settings>Control Panel>Services and scroll
down to the Honeywell PHD service.
On Windows 2000, click on Start>Settings>Control Panel>Administrative
tools/Services and scroll down to the Honeywell PHD service.
2. From the Services window, double click on the Honeywell PHD service. Set
the Startup Type to Manual and then select [OK].
Shutdown 1. Make sure all controllers, optimizers and toolkits are OFF and the main
existing Profit controller points are set INACTIVE.
Suite 2. Terminate the controller programs as described in Appendix E Using the
Applications Special Task Manager.
Shutdown TPS Profit Suite R205 may require a new version of the HCI Runtime software than
System you have loaded on your system. Check the timestamp of Program
Applications on Files\Honeywell\TPS\HCI Runtime\gopc.dll. If the timestamp is earlier than the
dates listed below, the HCI Runtime will need to be upgraded.
GUS and APP
Nodes · Windows NT nodes – gopc.dll dated 1/10/01 or later.
· Windows 2000 nodes – gopc.dll dated 1/9/02 or later.
Note: The HCI Runtime files included on the R205 Profit Suite CD are
for Non-TPS system nodes only. If the HCI components on a TPS
system node need to be upgraded, refer to the TPS System
Implementation Guide and perform the install using the appropriate
version of the TPS System Software CD for your site.
It is important that all other processes that use HCI Runtime be stopped prior to
installation.
1. Close the TPS Status display, and any other clients (including GUS
displays) that might be using HCI runtime functionality. This may
include clients on remote nodes accessing servers on this node.
2. Stop HCI servers, (TPN Server, CL Server and PHD-OPC Server) by
navigating to the node on the TPS Status display, highlighting the server
and selecting the right mouse click /Stop function.
3. Open up Start>Settings>Control Panel>Services (Start>Settings>Control
Panel>Administrative tools/Services on Windows 2000) and scroll down
to the TPS Admin service. Set its startup to Disable and stop the service.

Honeywell
Section 2 – Preparing for Intallation
2.2 Shutdown Application and Services
Shutdown Other To avoid the possibility of locked files, it is advisable to close down all Windows
Applications applications prior to installation. As the installation procedures require multiple
system restarts, it may be necessary to disable startup of services through Control
Panel/Services.
Shutdown Profit Stop any Profit Suite services that may be running before uninstalling earlier
Suite Services versions of Profit Suite software. These services are HSCmdSvc(R200 & R205)
and HiSpec AppStatusFinder(R205 only). Follow the procedure below to stop
these services.
1. On Windows NT, click on Start>Settings>Control Panel>Services and scroll
down to the HSCmdSvc service.
On Windows 2000, click on Start>Settings>Control Panel>Administrative
tools/Services and scroll down to the HSCmdSvc service.
2. From the Services window, double click on the HSCmdSvc service. If the
service is running, select [STOP]. Set the Startup Type to Manual and then
select [OK].
3. Repeat steps 1 and 2 to stop the HiSpec AppStatusFinder service.

Honeywell
2.3 Uninstall Previous Releases
Check the Prior to uninstalling, verify any special procedures covered in the Release Notes.
Release Notes
Uninstall earlier 1. Go to Start>Settings>Control Panel >Add/Remove Programs.

versions of
2. Select the program to be removed: HiSpec – Profit Controller.
Profit Suite
Software 3. Click the Add/Remove button.
4. Click the Yes button to verify.
5. Also uninstall HiSpec – Profit Viewer, HiSpec - Optimizer and any Profit
Toolkits (as required).
Uninstall HCI Note: Only uninstall HCI Runtime if you have verified the version requires an
Runtime upgrade.
a. Go to Start>Settings>Control Panel >Add/Remove Programs.
b. Select the program to be removed: TPS – HCI Runtime
c. Click the Add/Remove button.
d. Click the Yes button to verify.

Honeywell
Section 3 — Installing Profit TPS Server Files
3.1 Overview
In This Section This section tells how to install the Profit TPS Server Files needed for R205 of
Profit Suite. The setup will install seven capability files required to support the
R205 security functionality. The files are:
· PS_Administrator
· PS_Engineer
· PS_Supervisor
· PS_Supervisor2
· PS_Operator
· PS_Operator2
· PS_Operator3
On most TPS Domain Controller nodes, the files will be installed at the
following location:
C:\WINNT\system32\Repl\Export\HWIAC\TPSDomain1\Security\
Note: If there happen to be several TPS Domains configured on the same

Primary Domain Controller node, the installation will automatically detect this
and install the capability files in the appropriate folder for each TPS Domain.
Important · This installation is required for TPS systems only. Do not install on non-
TPS systems.
· Only run the Profit TPS Server setup program on the Primary TPS Domain
Controller node (i.e. the node running Windows NT Server 4.0 or Windows
2000 Server that was specified as the TPS server).
· Administrator access is needed to run the install program.

Honeywell
3.2 Installing Profit TPS Server Files
Installation Follow the steps below to install the Profit TPS Server files onto the Primary TPS
Domain Controller node:
1. From the Primary TPS Domain Controller node, log in as an
Administrator.
2. Insert the Profit CD into the CD-ROM drive.
3. Click [Start] and choose Run. From the Run window, select [Browse].
4. Use the “Look In:” drop down menu to select the CD drive.
5. Double Click on the ProfitTPSServer folder.
6. Double Click on Setup.exe. The action selects the file, closes the
Browse window, and returns the user to the Run window.
7. Select [OK] to begin the installation.
8. The following window will be displayed:

Honeywell
Section 3- Installing Profit TPS Server Files
3.2 Installing Profit TPS Server Files
9. Click [Next] on the Welcome window.
10. Click on [Yes] to accept the license agreement.

11. Click [Finish] to complete the setup.

Honeywell
Section 4 — Installing Embedded PHD Components
4.1 Overview
In This Section This section tells how to install Embedded PHD, PHD Patch, and Uniformance
Desktop to historize and trend Profit Suite parameters.
Important · Administrator access is needed to run the install program.
· Only run the Embedded PHD setup program on PCs that will be running
Profit Controllers, Optimizers and Toolkits, and that do not currently have
PHD installed.
· If the node is also to run the Uniformance Desktop, it is critical to install the
Embedded PHD before the Uniformance Desktop.

Honeywell
4.2 Installing Embedded PHD Server
Already using Embedded PHD Server is not supported on nodes that have Oracle-based PHD
Oracle-based
Server already installed.
PHD?
Installation Follow the steps below to install the Embedded PHD:
1. Log in as an Administrator.
5. Double Click on the Embedded PHD folder.
6. Double Click on Setup.exe. The action selects the file, closes the Browse
window, and returns the user to the Run window.
9. Click [Accept] to accept the License Agreement.

10. Click [Next] to accept the default Destination Directory.

Honeywell
Section 4 – Installing Embedded PHD Components
11. On the Select Components window, select both PHD Data Server and
Interface Server. Click [Next] to continue.
12. On the Select PHD Listening Port window, click [Next] to accept the default
Port number of 3000. If 3000 is already in use (as indicated by an Event Log
error message during runtime), select another port number or contact TAC.

Honeywell
13. Click [Next] to accept the Archive Directory.
14. On the Select Database Type window, select the [ODBC] radio button, then
click [Next].

Honeywell
15. On the Select Interface DCS Types window, select Remote PHD and click
[Next].
16. On the Select Remote PHD Port window, enter 3010 under Port number and
click [Next].
17. Click [Next] on the Ready to Install window

Honeywell
18. Select [Finish] on the Installation Completed window

19. Select [Cancel] on the final Install window. Restart must not occur at this
time.
20. On NT systems; click on Start->Settings->Control Panel/Services.

On Windows 2000; click on Start>Settings>Control Panel>Administrative
tools/Services.
21. From the Services window, double click on the Honeywell PHD service. Set
the Startup Type to Manual and then select [OK].
22. Now go to Subsection 4.3 Installing PHD Patch.

Honeywell
4.3 Installing PHD Patch
Install PHD Follow the steps below to install PHD Patch:
Patch
5. Double Click on the PHDPatch folder.
8. Click [Next] on the Information – PHD Patch Files window.
9. Click [Finish] when the installation is complete.

Honeywell
4.4 Installing Honeywell Uniformance Desktop
Important Notes · In order for the new summary and tuning reports in R205 to work, Microsoft
Excel must be installed on the node where Profit Viewer is running. To work
properly, the Performance Monitor report needs to also have the Uniformance
Companion for MS Excel Add-In, which is part of the Uniformance Desktop
installation. If Excel isn't installed on the node before the Uniformance
Desktop installation, it will not install the Excel Add-In and the Performance
Monitor report will not work.
· If you are installing on a Windows NT machine, you will be required to
reboot during the installation.
Installation To install the Honeywell Uniformance Desktop R160.1:
5. Double Click on the Uniformance Desktop folder.
8. If Windows Installer or Microsoft Data Access is not at the correct revision
levels, they will be installed automatically and you will be prompted to reboot
the node. Select [Yes] to reboot. After the reboot, log in as an Administrator
and the installation will continue.

Honeywell
9. Click [Next] on the welcome screen for the Honeywell Uniformance Desktop
–InstallShield Wizard.
10. After accepting the License Agreement, click [Next].

Honeywell
11. Accept the defaults for the user information (or modify as desired) and then
click [Next].
12. Select the default destination folder (generally c:) or change to the desired
drive then click [Next].
8/02 Profit Suite Installation Guide

27
Honeywell
13. For the Setup Type, select the Standard install. Note: Visual PHD and Tag
Explorer are not supported by Embedded History. Click [Next] to continue.
14. If you are not on a machine that has Embedded PHD installed, the next two
windows to come up will apply. The first will be the Set PHD Server Host
Computer Name display. Input the name of the computer where Embedded
PHD is located.

Honeywell
15. The next window to come up if you are not on a machine with Embedded
PHD will be the Set PHD Host Communications Port Number. Accept the
default port of 3000 and click [Next] to begin installation.
16. On the Ready to Install Honeywell Uniformance Desktop window, click

[Install].
17. Once installation has completed the following window will appear. Click
[Finish].

29
Honeywell
18. If you are installing on a Windows NT machine, the following window will
appear. Select [Yes] to restart the node. If you are installing on Windows
2000, a reboot is not required.

Honeywell
Section 5 — Installing Microsoft System Files
5.1 Overview
Important Notes · Administrator access is needed to run the install program.
· If you are installing on a Windows NT machine, you may be required to
reboot during and after the installation.
Installation The Microsoft System Files is a required installation for all Profit Suite
Requirements Applications.

Honeywell
5.2 Microsoft System Files – Installation Steps
Upgrading From If this installation is an upgrade, you will be required to run this package.
Previous Versions
Installation To install the Microsoft System Files:

5. Double Click on the MicrosoftSystemFiles folder.
8. Select [Next] on the Information window.
Note: If you have already installed the Uniformance Desktop components or
if the correct version of MDAC was already loaded, skip to Step 15.

Honeywell
Section 5 – Installing Microsoft System Files
9. If the install determines that MDAC needs to be updated, select [OK] to

install MDAC. You will also get a message if a system reboot is required.
10. After MDAC is installed, if a reboot is required, the following message will
appear. Select [Ok].
11. On the Reboot Required window, select [Yes] and [Finish] to reboot the
machine.

Honeywell
12. Once the computer reboots, log in as an administrator.
13. Select [Next] on the Information window to continue installation of the

Microsoft System Files.
Note: If the installation screen is not visible on the desktop, it may be because
it is hidden behind other applications that are open on the desktop (e.g.
Windows Explorer, Native Window, etc.). Simply minimize these windows.
14. Select [Yes] if you receive any prompts about read only files detected.
15. If some files were locked during the installation of the system files, you will
be prompted to reboot again. Select [OK]. If no locked files were detected,
skip to Step 18.

Honeywell
16. If a reboot is required, you will get the following message. Select [Yes] and
click [Finish] to restart your computer.

35
Honeywell
17. Once the computer reboots, log in as an administrator. On the information

setup display, select [Next].

Honeywell
18.On the Setup Complete window, select [Finish] to complete the Installation.

37
Honeywell
Section 6 — Installing HCI Runtime
6.1 Overview
Important · The HCI Runtime files included on the R205 Profit Suite CD are for
Non-TPS system nodes only. If the HCI components on a TPS system
node need to be upgraded, refer to the TPS System Implementation
Guide and perform the install using the appropriate version of the TPS
System Software CD for your site.
· All applications using HCI Runtime must be stopped prior to the
installation. See Section 2.2 Shutdown Applications and Services.
Installation HCI Runtime is a required component.

Requirements
TPS Nodes HCI Runtime will already be installed on TPS Nodes. Profit Suite components
check for the version and will you alert you if they need to be upgraded. You
can choose to continue with the component install, but must upgrade HCI
Runtime. As noted above, if HCI Runtime needs to be upgraded on a TPS node,
do not upgrade it using the HCI Runtime version that is included on the R205
Profit Suite CD. Instead, refer to the TPS System Implementation Guide and
perform the install using the appropriate version of the TPS System Software CD
for your site.
Non-TPS Nodes If an older version of HCI Runtime is detected, or missing during the Profit
Controller, Optimizer or Toolkit installations, the program will ask if you want to
install HCI Runtime. You may install it at that time, or run this procedure to
update the files.

Honeywell
6.2 HCI Runtime – Installation Steps
Upgrading From See the Release Notes. It is preferable to uninstall the old version before the
Previous Versions upgrade.
Installation To install the HCI Runtime software:

5. Double Click on the hcirt folder.
6. Double Click on the disk1 folder.
9. Click [Next] on the Welcome.
10. Click [Yes] on the License Agreement screen.
11. Enter your Company and User name on the TPS Setup screen. Enter 1 for
the Serial number, then click [Next].
12. On the Enter Information screen, enter the desired drive letter (generally the
C drive) and click [Next].
13. If the folder does not exist, a message box will appear. Click [Yes] to create
the folder.
14. On the Setup Type screen, select [Typical] and then [Next].
15. Click [Next] on the Start Copying Files window.
16. Click [Finish] on the Setup Complete window.
17. Restart the station before proceeding with other component installations.
Profit Suite Installation Guide 39

8/02
Honeywell
Section 7 — Installing Profit Viewer and Profit Trender
7.1 Overview
Important · Administrator access is needed to run the install program.
· Only run the setup program for Profit Viewer on PCs that need to view a
controller.
Microsoft System These programs require the additional Microsoft System Files. The installation
Files will prompt you if the files are not installed and will abort the installation. Run
the procedure in Section 5, Installing Microsoft System Files.
Software/Hardware See Section 1.6

Requirements

Honeywell
7.2 Installing and Configuring Profit Viewer
Upgrading From Refer to the Release Notes for full details.
Previous Versions
Prepare GUS and Follow the directions in Section 2 Preparing for Installation.
APP Nodes for
Installation
Installation Before installing Profit Viewer, make sure the following software has been
Dependencies installed:
· Microsoft System Files (See Section 5)
· Internet Explorer 5.5
Microsoft Internet Microsoft Internet Explorer 5.5 or later is required. If it is not installed yet, it can
Explorer be downloaded and installed from the Microsoft web site. Or you can install it
from the CD by double clicking ie5setup.exe from the IE55SP1 folder. It will
install Internet Explorer 5.5 Service Pack 1.
Installation To install Profit Viewer:
5. Double Click on the ProfitViewer folder.
8. If Microsoft System Files are not updated or you don’t have Microsoft Data
Access 2.51 installed you will be prompted to install them now. If you are
prompted to install them, do so now by performing the steps in Section 5,
Installing Microsoft System Files. Once the Microsoft System Files are
installed, rerun ProfitViewer Setup.

8/02
Honeywell
Section 7- Installing Profit Viewer and Profit Trender
10. Click on [Yes] to accept the License agreement.
11. If other Profit applications are already installed on a certain drive, the
following message appears. Select [Yes] to continue.

Honeywell
Section 7- Installing Profit Viewer and Profit Trender
12. If there are no other Profit Suite applications installed on the node, the
following screen will be displayed. Click [Next] to accept the default
destination location or enter a single letter for a different drive.
13. During the installation, you may be prompted to confirm overwrite of read
only files. If so, select [Yes to All].
14. During the installation you may receive a message that the PHD Patches were
not installed. If you have not installed the Embedded PHD History function,
you can ignore this warning. Otherwise, after completion of this installation,
run the PHD Patch install.
15. Click [Finish] to complete the installation. Now perform step 16 to initialize
Server Registrar.
Initializing Server 16. After installing Profit Viewer and while still logged on as an Administrator,
Registrar use the desktop icon to launch Profit Viewer. From the Program Applications
drop down menu, select “Add Profit Viewer Local Application (Server
Registrar)” and select [GO] to invoke the Server Registrar display. This
action enables Server Registrar to create the registry settings it needs the first
time it runs. If this action is not taken, when someone logs on as a different
user they may not be able to run Server Register and the following error
message may be generated - "Unexpected error; quitting".

Honeywell
Section 8 — Installing Profit Controller (RMPCT)
8.1 Overview
Profit Controller The Profit Controller can reside in the standard Application Module (AM), the
(RMPCT) Platforms UNIX-based Application Modulex (AxM), the APP node on Windows NT or
Windows 2000, and a stand alone Windows NT 4.0 or Windows 2000 PC. This
document is specifically aimed at the Windows NT or Windows 2000 user.
Important Administrator access is needed to run the install program.
Microsoft System These programs require the additional Microsoft System Files. The installation
Files Required program will prompt you if the Microsoft System Files are not installed and will
abort the installation. Run the procedure in Section 5 Installing Microsoft System
Files.
HCI Runtime These programs require the HCI Runtime software. If it is not present or an older
Required version is detected, the installation program will inform you it requires updating.
For non-TPS nodes, the install script will install HCI Runtime, reboot and
proceed with the Profit Controller installation. HCI Runtime can only be installed
on NTFS formatted drives.
Note: The HCI Runtime files included on the R205 Profit Suite CD are for
Non-TPS system nodes only. If the HCI components on a TPS system node
need to be upgraded, refer to the TPS System Implementation Guide and
perform the install using the appropriate version of the TPS System
Software CD for your site.
Software/Hardware See Section 1.6

Requirements

Honeywell
8.2 Installing and Configuring Profit Controller
Important:
GUS Profit Controller does not work on GUS workstations. So, do not attempt to
Workstations - install Profit Controller on a GUS workstation.
Important!
Profit Controller The Profit Controller (RMPCT) CD contains all the files needed for the
(RMPCT) Media installation of Profit Controller (RMPCT).
NOTE: Administrator access is needed to run the install program.
Installation Before installing Profit Controller, make sure the following software has been
· HCI Runtime (See Section 6)
· CL Server (APP nodes only, not on the Profit Controller CD)

Installation To install the Profit Controller (RMPCT) PC-Side software:
1. Verify that TPS services and Profit Suite applications are not running. See
procedures in Section 2 Preparing for Installation.
3. Insert the Profit Controller CD into the CD-ROM drive.
6. Double Click on the ProfitController folder.
9. If the node is not at Windows NT 4.0 SP5 or SP6a (Windows 2000 SP1 or
SP2) you will have to install the appropriate service pack before continuing.
If the service pack on the computer is higher than these listed, the following
warning is given. Installation can proceed, but check with TAC to determine
if there are any known issues with later service packs.

Honeywell
Section 8— Installing Profit Controller (RMPCT)
10. If there is no PHD Server installed on the node, the following message will
appear. Select [Yes] to continue the installation or select [No] to abort the
installation and install Embedded PHD.
11. If Microsoft System files were not previously installed, you will be
prompted to install them now. Select [Ok] to abort the installation. After
installing the Microsoft System Files (see Section 5 Installing Microsoft
System Files), rerun the setup for Profit Controller.
12. If this is an APP node and CL Server has not been installed, the following
message will appear. CL Server software is required if Profit Controller is
running on an APP Node.
Note: CL Server is a Honeywell software package purchased separately
from Profit Controller.

Honeywell
Warning 13. After the checks above have been performed by the installation software, the
following message will appear reminding the user to stop any Profit
Controller and Profit Optimizer processes. Failure to stop any controller
or optimizer processes will result in the installation failing. Click [Yes]
after verifying all processes are stopped.
Note: If you are not sure how to determine if any Profit Controller or Profit
Optimizer processes are running or if you don’t know how to stop them,
select [No] to abort the installation and then go to Appendix E of this
document. There you will find instructions on how to use the Private Task
Manager utility (privtaskmgr) to see if any controller or optimizer processes
are running. If they are, you will be able to stop them. Once the processes
are stopped, rerun the setup for Profit Controller.
14. If this is a non-TPS node and the HCI Runtime is not currently installed, or
is an older version, you will be asked if you want to install it now. Click on
[Yes] to install, and [Yes] to reboot after the installation.
15. If this is a TPS node and the HCI Runtime is not at the correct version level
or it is not found, you will get a message that it needs to be updated or
installed. Select [OK] to abort the installation. Once the correct version of
HCI Runtime has been installed, rerun the setup for Profit Controller.
Note: If the HCI Runtime components on a TPS system node need to be
upgraded, refer to the TPS System Implementation Guide and perform the
install using the appropriate version of the TPS System Software CD for
your site.

Honeywell
16. Click [Next] on the Welcome window to continue.
17. Select [Yes] to accept the license agreement.
18. If other Profit applications are already installed on the node, the following
message appears (with the blanks filled in correctly). Select [Yes] to
continue.

Honeywell
19. If this is the first Profit Suite component to be installed, enter a destination
drive or accept the default. Click [Next] to continue.
20. During the installation you may receive a message that the PHD Patches
were not installed. If you have not installed the Embedded PHD History
function, you can ignore this warning. Otherwise, after completion of this
installation, run the PHD Patch install.
21. Click [Finish] to complete the installation.

Honeywell
8.3 Initializing Profit Controller’s Messages
In This Section This section describes the procedure for changing the Profit Controller messages
to another language.
Text for the controller messages is contained in message files that are installed by
the setup program. The controller program reads these files when it starts up. You
do not have to do anything with the message files unless you want to translate
them to another language.
Here are instructions to translate messages to another language:
· First run the Profit Controller (RMPCT) setup program.
· The messages are contained in files having the extension “.msg”. Use the NT
‘Find’ command to locate them.
· Use NT Explorer to copy the message files to some other directory. This
provides a backup set of files to which you can refer if you encounter
problems while you are modifying the original files.
· Use NT Notepad or other text editor to edit each message file. Change the
text as desired.
· Each record in a message file is one message.
· The messages are in pairs. The first record of a pair is the message that the
controller sends when the condition described by the message goes into
effect. The second record of a pair is the message that the controller sends
when the condition clears.
· An all-blank record is not sent. This is typically used as the second message
of a pair when there is no need to send a message when the condition clears.
These records must not be deleted. The position of the records in the file must
be maintained.
· You generally should not change a record that contains some information into
an all-blank record. This is because the second message of a pair is used to
clear the first message from the Profit Controller status display, and this will
not occur if the second message is blank, because all-blank messages are not
sent.
· You will note that many messages contain fields that start with a percent sign
(%) and end with one of the following characters: c, d, i, o, u, x, e, f, g, n, p,
or s. These fields designate a place in the message where the controller will
insert variable information, such as a numerical value or a name, when it
sends the message. You must not change these fields or their order, but you
can remove or add any text, including blanks, before or after these fields.

Honeywell
Section 9 — Installing Profit Optimizer
9.1 Overview
Profit Optimizer The Profit Optimizer can reside in the standard Application Module (AM), the
(DQP) Platforms UNIX-based Application Modulex (AxM), the APP node on Windows NT or
Windows 2000, and a stand alone Windows NT 4.0 or Windows 2000 PC. This
document is specifically aimed at the Windows NT or Windows 2000 user.
Important Administrator access is required to install this program.
Microsoft System These programs require the additional Microsoft System files. The installation
Files Required program will prompt you if the Microsoft System Files were not installed and will
abort the installation. Run the procedure in Section 5 Installing Microsoft System
Files.
HCI Runtime These programs require the HCI Runtime software. If it is not present or an older
Required version is detected, the installation program will inform you it requires updating.
For non-TPS nodes, the install script will install HCI Runtime, reboot and proceed
with the Profit Optimizer installation. HCI Runtime can only be installed on
NTFS formatted drives.
Note: The HCI Runtime files included on the R205 Profit Suite CD are for
Non-TPS system nodes only. If the HCI components on a TPS system node
need to be upgraded, refer to the TPS System Implementation Guide and
perform the install using the appropriate version of the TPS System Software
CD for your site.

Honeywell
9.2 Installing and Configuring Profit Optimizer
Profit Optimizer The Profit Optimizer (DQP) CD contains all the files needed for the installation of
(DQP) Media Profit Optimizer.
NOTE: Administrator access is needed to run the install program.
Installation Before installing Profit Optimizer, make sure the following software has been
· CL Server (APP nodes only, not on the Profit Optimizer CD)

Installation To install the Profit Optimizer (DQP) PC-Side software:
1. Verify that TPS services and Profit Suite applications are not running. See
3. Insert the Profit Optimizer CD into the CD-ROM drive.
6. Double Click on the ProfitOptimizer folder.
9. If the node is not at Windows NT 4.0 SP5 or SP6a (Windows 2000 SP1 or
SP2) you will have to install the appropriate service pack before continuing.
If the service pack on the computer is higher than these listed, the following
warning is given. Installation can proceed, but check with TAC to determine
if there are any known issues with later service packs.

Honeywell
Section 9— Installing Profit Optimizer
10. If Microsoft System files were not previously installed, you will be prompted
to install them now. Select [Ok] to abort the installation. After installing the
Microsoft System Files (see Section 5 Installing Microsoft System Files),
rerun the setup for Profit Controller.
Warning 11. After the checks above have been performed by the installation software, the
following message will appear reminding the user to stop any Profit
Controller and Profit Optimizer processes. Failure to stop any controller or
optimizer processes will result in the installation failing. Click [Yes] after
verifying all processes are stopped.
Note: If you are not sure how to determine if any Profit Controller or Profit
Optimizer processes are running or if you don’t know how to stop them,
select [No] to abort the installation and then go to Appendix E of this
document. There you will find instructions on how to use the Private Task
Manager utility (privtaskmgr) to see if any controller or optimizer processes
are running. If they are, you will be able to stop them. Once the processes
are stopped, rerun the setup for Profit Controller.

Honeywell
12. If this is a non-TPS node and the HCI Runtime is not currently installed, or is
an older version, you will be asked if you want to install it now. Click on
[Yes] to install, and [Yes] to reboot after the installation.
13. If this is a TPS node and the HCI Runtime is not at the correct version level
or it is not found, you will get a message that it needs to be updated or
installed. Select [OK] to abort the installation. Once the correct version of
HCI Runtime has been installed, rerun the setup for Profit Optimizer.
Note: If the HCI Runtime components on a TPS system node need to be
upgraded, refer to the TPS System Implementation Guide and perform the
install using the appropriate version of the TPS System Software CD for your
site.

Honeywell
16. If other Profit applications are already installed on a certain drive, the
following information box appears (with the blanks filled in appropriately)
Select [Yes] to continue. Selecting [ No] will abort the installation.

Honeywell
18. During the installation you may receive a message that the PHD Patches were
not installed. If you have not installed the Embedded PHD History function,
you can ignore this warning. Otherwise, after completion of this installation,
run the PHD Patch install.
19. Click [Finish] to complete the installation.

Honeywell
9.3 Initializing Profit Optimizer’s Messages
In This Section This section gives the procedure for changing the messages that Profit Optimizer
sends to another language.
Text for the controller messages is contained in message files that are installed by
the setup program as described in Section 3.3. The controller program reads these
files when it starts up. You do not have to do anything with the message files
unless you want to translate them to another language.
· First run the Profit Optimizer (DQP) setup program as described in Section
10.2.
Find command to locate them.
provides a backup set of files to which you can refer if you encounter problems
while you are modifying the original files.
· Use NT Notepad or other text editor to edit each message file. Change the text
as desired.
controller sends when the condition described by the message goes into effect.
The second record of a pair is the message that the controller sends when the
condition clears.
· An all-blank record is not sent. This is typically used as the second message of
a pair when there is no need to send a message when the condition clears.
be maintained.
clear the first message from the Profit Optimizer (DQP) status display, and this
will not occur if the second message is blank because all-blank messages are
not sent.
· You will note that many messages contain fields that start with a percent sign
(%) and end with one of the following characters: c, d, i, o, u, x, e, f, g, n, p, or
s. These fields designate a place in the message where the controller will insert
variable information, such as a numerical value or a name, when it sends the
message. You must not change these fields or their order, but you can remove
or add any text, including blanks, before or after these fields.

Honeywell
Section 10 — Installing Profit Toolkit
10.1 Overview
Software/Hardware Refer to Section 1.6 for these requirements.
Requirements
Using PHD? If you are using Oracle-based (not embedded) PHD see Appendix C.

Honeywell
10.2 Installing Profit Toolkit Applications
In This Section This section describes how to install Profit Toolkit Applications. This procedure
is applicable for the following toolkits:
· FCCU Toolkit
· Fractionator Toolkit
· Lab Update Toolkit
· Wrapper Builder Toolkit
Installation Before installing a Profit Toolkit application, make sure the following software
Dependencies has been installed:

Installation 1. Verify that TPS services and Profit Suite applications are not running. See
6. Double Click on the desired toolkit folder (e.g. FCCUToolkit,
FractionatorToolkit, etc.).
9. If the service pack on the computer has not been tested against the Profit
Toolkit Application software the following warning is given. Installation
can proceed, but check with TAC to determine if there are any known issues
with later service packs.

Honeywell
Section 10— Installing Profit Toolkit
10. The following reminder is displayed to allow installation to be halted.

Failure to stop any toolkit processes will result in the installation failing.
Click [Yes] after verifying all processes are stopped.

Honeywell
message appears (with the blanks filled in accordingly.). Select [Yes] to
continue.
Note: To install Profit Toolkit Application on a different drive, you must
uninstall the currently installed Profit Toolkit Applications and re-install
them in a new drive.

Honeywell
16. If there are no locked files, go to Step 18, otherwise the following message
will appear. Select [Ok] to continue.

Honeywell
17. Select Yes to restart the computer and click [Finish] to exit.
18. If there were no locked files, click [Finish] to complete the installation.

Honeywell
10.3 Installing the FCCU Modeling Spreadsheet
In This Section This section describes how to install the FCCU Excel modeling spreadsheets.
Purpose of FCCU The FCCU modeling coefficients are generated via the FCCU spreadsheets by
Modeling
Spreadsheets
running the Excel solver for sets of plant data.
Installation Run the FCCU Toolkit installation setup program on the target machine using the
installation instructions in Section 10.2. This will install the necessary DLLs for
the FCCU spreadsheets to run.
Copying the The setup program does not install the modeling spreadsheets. You must copy
Modeling these files from the FCCU Toolkit installation disk (in directory FCCU Modeling
Spreadsheets Spreadsheets) to a directory of your choice on the target machine.
A Few Words There are three modeling spreadsheets: Open_Severity.xls, Open_Product.xls and
about the Open_Octane.xls. Open_Severity is the master spreadsheet as the raw plant data
Spreadsheets (i.e. temperature, pressure, etc.) is entered in this spreadsheet. Open_Severity also
contains some important modeling information in its “ReadMe” worksheet.
Open_Product and Open_Octane rely on data in Open_Severity. So,
Open_Severity needs to be configured first.
Linking modeling The modeling spreadsheet is hard-coded to find the FCCU DLLs in the directory
spreadsheets to C:\Program Files\Honeywell\HiSpec Solutions\ProfitToolkit\FCCU. So, if the
toolkit DLLs DLLs are installed in another directory – for example in drive D: - then the hard-
coded reference must be changed in the Excel spreadsheet.
The toolkit function DLLs are called using Excel Visual Basic for applications
code (VBA). To change the reference, open the VBA Module "DLL" (get there by
pressing ALT-F11 from the worksheet) and change the "Declare Function" path
for each function at the top of the module. This must be done in each spreadsheet.
64 Profit Suite Installation Guide

8/02
Honeywell
10.4 Initializing Profit Toolkit’s Messages
In This Section This section gives the procedure for changing Profit Toolkit messages to another
language.
Text for the Profit Toolkit messages is contained in message files that are installed
by the setup program. The Profit Toolkit program reads these files when it starts
up. Do not change the message files unless you want to translate them to another
language.
· First run the Profit Toolkit setup program.

‘Find’ command to locate them.
provides a backup set of files to which you can refer if you encounter
problems while you are modifying the original files.
· Use NT Notepad or other text editor to edit each message file. Change the
text as desired.
Toolkit sends when the condition described by the message goes into effect.
The second record of a pair is the message that the Toolkit sends when the
condition clears.
· An all-blank record is not sent. This is typically used as the second message
of a pair when there is no need to send a message when the condition clears.
be maintained.
clear the first message from the status display, and this will not occur if the
second message is blank because all-blank messages are not sent.
· Please note that many messages contain fields that start with a percent sign
(%) and end with one of the following characters: c, d, i, o, u, x, e, f, g, n, p,
or s. These fields designate a place in the message where the Toolkit will
insert variable information, such as a numerical value or a name, when it
sends the message. You must not change these fields or their order, but you
can remove or add any text, including blanks, before or after these fields.

Honeywell
Section 11 — Installing Profit Bridge
11.1 Overview
Requirements
Items Included on The following items are included on the Profit Bridge CD.
Profit Bridge CD v Profit Bridge Toolkit, which includes:
Ø Profit Toolkit Engine
Ø Gain Extraction toolkit
Ø GainMappers for Profit Controller and Profit Optimizer
v Profit Design Studio
v Profit Viewer
v Common components for any “Profit” application
Ø Embedded PHD Components (optional)
Ø Microsoft System Files and Internet Explorer 5.5 SP 1
Ø HCI Runtime
v Documentation
How to Install Profit Profit Bridge is a Profit Toolkit application. The installation steps are similar
Bridge to those of other Profit Toolkit installations. However, because a Profit Bridge
application has multiple components that can be distributed across different
nodes, Profit Bridge has a number of installation configurations. The general
Profit Toolkit installation steps are detailed in Section 10 Installing Profit
Toolkit and summarized below. Five Profit Bridge installation scenarios are
described following the general installation summary.
Where to Install Profit 1. Profit Bridge components must be installed on machines where PDS is to
Bridge Components be used to configure a Profit Bridge application.
2. Profit Bridge components must also be installed on machines where a
simulation or runtime Profit Bridge application is to execute.
3. Gain Mappers must be installed on the machines where associated Profit
Controller and Profit Optimizer applications are to execute.
What’s not Included The Third-Party Model Sockets (FCC-Sim Socket or NOVA socket, for
on Profit Bridge CD example) are not included on the Profit Bridge CD. These are supplied
separately.
66
Profit Suite Installation Guide 8/02
Honeywell
Section 11— Installing Profit Bridge
11.1Overview
Additional Details on Although the GainMappers are installed from the Profit Bridge CD, the
Installing the Gain Mappers run as toolkit functions that are part of Profit Controller and Profit
Mappers Optimizer applications. After the Profit Bridge Toolkit CD has been installed,
ensure that any Profit Controller or Profit Optimizer applications that require
gain mapping have the gain mapping records in their configuration (CFG) file.
To determine if the gain mapping records are in the Profit Controller and/or
Optimizer configuration file, view the appropriate CFG file and look for a
record similar to this: (Note that the Profit Optimizer application references
GainMapperPO instead of GainMapperPC.)
Server, HS_Toolkit_1_0, order 999
…
Options, HSTool_GainMapperPC, HS_GainMapperPC, Begin, GainMapperPC1
If this record is found in the CFG file, you only need to set the Profit
Controller/Optimizer Inactive, then Active. This will load and run the newly
installed GainMapper DLLs.
If the record is not found in the CFG file, you must regenerate the
configuration file from the Profit Design Studio using the appropriate Runtime
Configuration utility. This will put the GainMapper records in the CFG file.
Subsequently, set the Profit Controller/Optimizer Inactive, then Active. This
will load and run the newly installed GainMapper DLLs.

Honeywell
11.2 Profit Bridge Installation Scenarios
Installation This scenario includes Profit Bridge for design simulation and configuration
Scenario 1 build on a different node than the runtime application.
1. Install Profit Design Studio (PDS 235.0 or newer)
See Section 13 Installing Profit Design Studio.
2. Follow the steps in Section 11.3 to install Profit Bridge.
3. Install other necessary toolkits using their specific installation instructions.
For example, install the nonlinear model functions that are to be used by
Profit Bridge.
Installation This scenario includes running Profit Bridge on a different node than associated
Scenario 2 Profit Controller and Profit Optimizer applications. (Assume PDS is not to be
installed on these runtime nodes.)
1. On the modeling system node (where Profit Bridge will reside), use
procedures in Sections 1 through 7 to install the following:
a. Embedded PHD Components (optional) (See Section 4)
i. Embedded PHD Server
ii. PHD Patch
iii. Uniformance Desktop
b. Microsoft System Files (See Section 5)
c. HCI Runtime (See Section 6)
d. Profit Viewer (See Section 7)
2. On the modeling system node, install Profit Bridge following the steps in
Section 11.3.
3. On the nodes with associated Profit Controllers, install the Gain Mapper for
Profit Controller, following the steps in Section 11.4.
4. On the node with the associated Profit Optimizer, install the Gain Mapper
for Profit Optimizer, following the steps in Section 11.4.

Honeywell
11.2 Profit Bridge Installation Scenarios
Installation This scenario includes Profit Bridge for Runtime on the same node as existing
Scenario 3 Profit Controller and/or Profit Optimizer applications. (Assume PDS is not to be
installed on this runtime node.)
1. Install Profit Bridge following the steps in Section 11.3.
2. On the nodes with associated Profit Controllers, install the Gain Mapper for
Profit Controller, following the steps in Section 11.4.
3. On the node with the associated Profit Optimizer, install the Gain Mapper
for Profit Optimizer, following the steps in Section 11.4.
Installation This scenario includes Profit Bridge for Runtime on the same node as existing
Scenario 4 pre-R205 Profit Controller and/or Profit Optimizer applications.
1. Upgrade the existing pre-R205 Profit Controller and Profit Optimizer
applications to R205 following the procedures in this document and the
Profit Controller/Profit Viewer/Profit Trender Release Notes.
2. Follow the procedures outlined in Scenario 3.
Installation This scenario includes Profit Bridge for Runtime on the same node as non-
Scenario 5 existing Profit Controller and/or Profit Optimizer applications.
1. Install Profit Controller and Profit Optimizer applications following the
procedures in this document.
2. Follow the procedures outlined in Scenario 3.

Honeywell
11.3 Installing Profit Bridge
In This Section This section describes how to install Profit Bridge
Installation Before installing a Profit Bridge, make sure the following software has been

Installation 1. Verify that TPS services and Profit Suite applications are not running. See
3. Insert the Profit Bridge CD into the CD-ROM drive.
6. Double Click on the ProfitBridgeToolkit folder.
Profit Suite Installation Guide 8/02

70
Honeywell
Section 11 – Installing Profit Bridge


Honeywell
continue.

Honeywell
19. To install Gain Mapper for Profit Controller or Profit Optimizer, follow the
installation procedure in the next subsection.

Honeywell
11.4 Installing Profit Controller Gain Mapper and Profit
Optimizer Gain Mapper
In This Section This section describes how to install Gain Mapper for either Profit Controller or
Profit Optimizer.
2. Insert the Profit Bridge CD into the CD-ROM drive.
5. Double Click on either the ProfitControllerGainMapper folder or
ProfitOptimizerGainMapper folder.

Honeywell
11.4 Installing Profit Controller Gain Mapper and Profit Optimizer Gain Mapper
8. If you are installing Profit Controller Gain Mapper and Profit Controller has
not been installed, you will get a message and the installation will abort.
Likewise if you are installing Profit Optimizer Gain Mapper and Profit
Optimizer has not been installed, you will get a message and the installation
will abort. After installing the appropriate application, rerun Setup for Gain
Mapper.

11. When the installation is complete, select [Finish].

Honeywell
Section 12 — Installing Profit SensorPro
12.1 Overview
Requirements
Using PHD? If you are using Oracle-based (not embedded) PHD see Appendix C.

Honeywell
12.2 Installing Profit SensorPro
In This Section This section describes how to install Profit SensorPro
Installation Before installing Profit SensorPro, make sure the following software has been
· Embedded PHD (See Section 4)

· PHD Patch (See Section 4)
· Uniformance Desktop (See Section 4)

· Profit Viewer (See Section 7)
· Profit Design Studio for SensorPro (For Offline Configuration) (See

Section 13) Note that the Profit Design Studio from the Profit
SensorPro CD must be used in order to install the correct offline design
Profit SensorPro DLLs .
Installation 1. Log in as an Administrator.
2. Insert the Profit SensorPro CD into the CD-ROM drive.
5. Double Click on either the ProfitSensorPro folder.

Honeywell
Section 12 – Installing Profit SensorPro


Honeywell
Section 12— Installing Profit SensorPro
continue.

Honeywell
Section 12— Installing Profit SensorPro

Honeywell
Section 13 — Installing Profit Design Studio
13.1 Overview
In This Section Profit Design Studio consists of a main environment and many components
within this environment.
System and Software Requirements This section lists the system and
software requirements for loading and using the Profit Controller (RMPCT)
Designer’s builder and simulator software.
Installation Quick Reference A quick reference is provided indicating the
major tasks involved with installing the Profit Design Studio (APCDE) software
package. If you have installed Profit Design Studio (APCDE) before, use the
quick reference to install the software package.
Installation Instructions Step-by-step installation instructions are provided for
new users of Profit Design Studio (APCDE). If this is your first installation, use
these instructions rather than the quick reference to install the software.

Honeywell
13.2 System and Software Requirements
Software The Profit Design Studio (APCDE) package either comes on the Profit
Requirements Controller CD, Profit Optimizer CD, Profit Toolkit CDs, Profit Stepper CD or
may be obtained on a separate CD.
PC Requirements The following table lists the recommended and minimum PC system
requirements for using Profit Design Studio (APCDE). Depending on system
size, simulation can be computationally demanding. Although slower systems
may function, maximum computational resources are recommended.
Recommended Configuration Minimum Configuration
• Windows NT, 98 or 2000 • Windows NT, 98 or 2000
• Pentium 300 MHz • 80486 w/math coprocessor
• 24 MB RAM • 16 MB RAM
• 50MB disk space • 12MB disk space
• Profit Design Studio (APCDE) • Profit Design Studio (APCDE)
version 235 or greater version 235 or greater
• VGA • VGA
• Standard Windows video driver • Standard Windows video driver
• CD Rom • CD Rom
• Mouse • Mouse

Honeywell
13.3 Quick Reference to Installation
How to Use the Read and perform the following procedures to install Profit Design Studio
Quick Reference (APCDE). For detailed instructions and help, see the referenced sections.
Quick Reference The following table outlines the major tasks involved with Profit Design Studio
Table installation. Use this table if you have installed Profit Design Studio before. If
this is your first installation, use the detailed instructions provided in Section
13.4.
Step Action Section Reference
1. Make sure your computing systems meet the See Section 13.2 “System and
minimum requirements. Software Requirements”.
2. Install Profit Design Studio (APCDE) See Section 13.4 “Installing

Profit Design Studio”.
If Dongle Driver has not been installed already,
Install Dongle Driver on the PC.

Honeywell
13.4 Installing the Profit Design Studio
PC Installation To run the SETUP program for Profit Design Studio (APCDE), perform the
following steps:
1. Make sure no other programs are running. Installation may fail or take a
very long time to complete.
2. Insert the CD titled Profit Controller, Profit Optimizer, Profit Toolkit,
Profit Stepper or Profit Design Studio into the CD-ROM drive.
3. Right click on Start. Choose Explorer. This will activate Windows
Explorer.
Microsoft System
Files
4. Click once on the CD Drive to display the contents of the CD Drive.
5. Double Click on the MicrosoftSystemFiles folder.
6. Double click on Setup.exe.
7. Follow the prompts to install the Microsoft system files
Microsoft Internet 8. If you are installing Profit Design Studio on a Windows 98 or 2000
Explorer machine, Microsoft Internet Explorer 5.5 or later is required. If it is not
installed yet, it can be downloaded and installed from Microsoft web site.
Or you can install it from the CD by double clicking ie5setup.exe from
the IE55SP1 folder. It will install IE5.5.
Profit Design 9. Click once on the CD Drive to display the contents of the CD Drive.
Studio
10. Double Click on the ProfitDesignStudio folder.
11. Double click on Setup.exe.

Honeywell
Section 13 – Installing Profit Design Studio
12. After the Information, Welcome and Licensing screens the “Destination
Drive Selection” screen will be presented.
13. Either accept the default destination drive or enter a single letter for an
alternate drive. Click [Next].
Note: If other Profit applications are already installed on the machine,
you will not be able to select an alternate drive location. In this case,
Click [Yes] to continue.
14. After the Profit Design Studio software has been installed, a dialog box
may show up asking you whether you want to install the Sentinel Dongle
Driver now. If it does, proceed to the next step. If it does not, the driver
has already been installed and the installation will complete.
Installing the 15. After ensuring that the physical Dongle is attached to your computer and
Dongle Driver
you have System Administration privileges, click [Yes] to proceed with
the Dongle installation.
Note: The driver needs to be installed only when you first install the 32-
bit version of Profit Design Studio (APCDE). You do not need to install
it again when you upgrade or add optional products to the Profit Design
Studio (APCDE).
16. If setup detects an older version of the Sentinel System Driver, you will
be prompted to confirm the upgrade. The older version is uninstalled
immediately after you confirm the upgrade. If you cancel out of the
installation after this, you will not have your older version installed.
17. After the Welcome screen for the Sentinel System Driver, the Setup Type
screen will appear. Select "Complete" for the setup type and then Click
[Next].
18. On the Ready to Install screen, select [Install]. If you are running
Windows 95/98/ME, you will have to reboot if you upgraded from a
previous version. This is necessary to start the parallel driver. Windows
NT and 2000 do not require a reboot.
Note: If at anytime during the installation procedure you begin receiving
error messages, make sure that you have the Dongle in place AND
administration privileges on the computer!
19. Select [Finish] to complete the Dongle Driver Installation.

Honeywell
Installing the 20. If you are on a computer that supports USB, an Information screen will
USB Dongle then appear for the SentinelSuperPro Server installation. If you have a
USB dongle, select [Yes] to install it now, otherwise, select [No]. If you
Server
do not get the Information screen, the server is already installed or your
computer does not support USB.
Note: If the SentinelSuperPro Server has not been installed on the
machine before, you may be required to reboot the machine. Select [Yes]
to reboot now or select [No] and remember to reboot later.
21. Click [Finish] to complete the installation process.
22. Select Start>Programs>Honeywell HiSpec Solutions>ProfitDesignStudio
235.00
Or from the desktop, click on the ProfitDesignStudio 235.00 icon. If all
the software was installed correctly, the About Profit Design Studio
dialog box will have the appropriate check marks and version information
displayed.

Honeywell
Check the Log If you would like to check the version numbers of the dlls, check the log file. To
File view a log file, open it with a text editor (Notepad). The log file can be found at
c:\users\HiSpec\Apps\ProfitDesignStudio.log. An example of the information
contained in the log file is shown below.
12:53:56 26Jun02
Profit Design Studio: 32 bit Version 235.00.0000
Loaded Math Library: HMATH32.DLL Version 200.00.0000
Loaded Utility Library: HUTIL32.DLL Version 220.02.0000
Loaded Identification Library: HIDENT32.DLL Version 300.00.0000

Loaded Controller Build Library: HBUILD32.DLL Version 205.00.0000
Loaded Controller Library: HCNTRL32.DLL Version 205.0000
Loaded Run Block Library: HBLOCK32.DLL Version 205.0000
Loaded Process Simulator Library: HSIM32.DLL Version 205.0000
Loaded Advanced Identification Library: HADVID32.DLL Version 110.00.0100
Loaded Profit Finder Library: HFINDER32.DLL Version 205.00.0000

Loaded Finder Prediction Library: HPRED32.DLL Version 205.00.0000
Loaded Profit PID Library: HPID32.DLL Version 205.00.0000

Loaded Profit Loop Build Library: HSPID32.DLL Version 100.01.0100

Loaded Profit Loop Controller Library: HSCTRL32.DLL Version 100.0100
Loaded Profit Optimizer Builder Library: HBLDQP32.DLL Version 205.00.0000
Loaded Signal Generation Library: HSIG32.DLL Version 100.02.0000
Loaded RMPCT Point Builder Library: HBLDEB32.DLL Version 205.00.0000
Loaded DQP Point Builder Library: HDBLDEB.DLL Version 205.00.0000
Loaded TDC Data Converter Library: HCONV32.DLL Version 105.00.0000
Loaded Scout File Converter Version 100.00.
Loaded Model Converter Library: HDMCNV32.DLL Version 100.00.0100
Loaded Vector Tool Library: HVTOOL32.DLL Version 110.00.0100
Loaded Profit Toolkit Designer Library: HSTOOL32.DLL Version 205.00.0000

Honeywell
NOTE Due to historical reasons any reference to the name “Finder” is equivalent
to the name “SensorPro”. These names can be used interchangeably. Any file with
the name Finder can be considered to apply to a SensorPro application
Prior to Profit Design Studio 235, log file was in “c:\Winnt\APCDE32.log”.
Any problems with loading libraries will be described here. Inability to locate a
library or library version incompatibility will prevent a library load.

Honeywell
Check Registry Default parameters that can be adjusted by the user are contained in the registry
for Options under: “HKEY_CURRENT_USER\Software\Honeywell IAC\HiSpec
Solutions\Profit Design Studio”. After ProfitDesignStudio is launched once, the
registry will be automatically updated to include default settings. Use registry
editor to view or edit the registry. Clcik “Start >Run…”. Type “regedit” in the open
edit box and click “OK”. An example of the default information contained in the
registry is shown below:
Note that before release 235 of Profit Design Studio, “APCDE32.ini” file under
SYSTEM or WINNT directory was used for default parameters. The contents and
structure in the ini file map to the registry under key
“HKEY_CURRENT_USER\Software\Honeywell IAC\HiSpec Solutions\Profit
Design Studio”.

Honeywell
Options in [SSC options] – This option supports a Dongle bypassing code. You have to
Registry
obtain the code from Hi Spec and manually add a new String Value under “SSC
options” with name “Code” and enter the code value you have obtained. To do so,
open registry editor, browse to “HKEY_CURRENT_USER\Software\Honeywell
IAC\HiSpec Solutions\Profit Design Studio”, select “SSC options”. Click menu
“Edit > New > String Value”. Change the name of the new string value to be
“Code”. Double click on “Code”. In the “Edit String” dialog box, enter the value
you have obtained into “Value Data” edit box and click OK.
[Engine Debug Flags] – This option supports change file creation in Profit
Controller offline simulation. The default is not creating change file. To modify
the default setting, you have to manually add a new String Value under “Engine
Debug Flags” with name “CreateChgFile” and enter value of 1 or 0 for creating
change file or not creating change file. To do so, open registry editor, browse to
“HKEY_CURRENT_USER \ Software\Honeywell IAC \ HiSpec Solutions \
Profit Design Studio”, select “Engine Debug Flags”. Click menu “Edit > New >
String Value”. Change the name of the new string value to be “CreateChgFile”.
Double click on “CreateChgFile”. In the “Edit String” dialog box, enter 1 to
“Value Data” edit box if you want to create change file. Otherwise, enter 0.
[Memory Buffer] - This option pertains directly to identification and is discussed

in “Identifier User’s Guide”.
[User Options] - This option pertains directly to identification and is discussed in
“Identifier User’s Guide”.
[PFOptions] – This option allows user to set a default threshold for PCA
calculations in percent cumulative variance. The default is 90. To modify the
default, you have to manually add a new String Value under “PFOptions” with
name “PCADefault” and enter the desired value. To do so, open registry editor,
browse to “HKEY_CURRENT_USER \ Software\Honeywell IAC \ HiSpec
Solutions \ Profit Design Studio”, select “PFOptions”. Click menu “Edit > New >
String Value”. Change the name of the new string value to be “PCADefault”.
Double click on “SkipChangeScaling”. In the “Edit String” dialog box, enter the
desired value into “Value Data” edit box.
[Toolbar preference] – This option is pertains to the identification toolbar
preference of the user. Zero implies the use of the standard toolbar while one
implies the use of the detailed toolbar.
[MultiThread Option] – If the Profit Design Studio is intended for use on a
online machine where other on-line applications are running, this option should be
set to 1. Such that all calculation intensive functions in PDS will be executed in

Honeywell
Section 13 –– Installing Profit Design Studio
separate low-priority threads in order not to interfere with mission critical on-line
applications. If this option does not exist, the default value is 1. If PDS is intended
to be running on an off-line machine, this option can be set to 0 and PDS
calculation intensive functions will still be executed in the same high priority
thread. This option is available since PDS235.
[Version] – In PDS235 and later, multiple versions of controller/optimizer are
supported. When PDS is started, it reads the version number from .ini file and
uses it to be the default controller/optimizer version. If the Version option does
not exist, the default version is “R205”. You can change it to “R160” or “R200”.
[Scaling Flags] – In Profit Controller Release 200 and later, user can change
default scaling factors in controller build. This option allows user to skip scaling
changes in controller build. The default is user changeable scaling. To modify the
default setting, you have to manually add a new String Value under “Scaling
Flags” with name “SkipChangeScaling” and enter value of 1 or 0 for skip scaling
change or not skip scaling change. To do so, open registry editor, browse to
“HKEY_CURRENT_USER \ Software\Honeywell IAC \ HiSpec Solutions \
Profit Design Studio”, select “Scaling Flags”. Click menu “Edit > New > String
Value”. Change the name of the new string value to be “SkipChangeScaling”.
Double click on “SkipChangeScaling”. In the “Edit String” dialog box, enter 1 to
“Value Data” edit box if you want to skip scaling change. Otherwise, enter 0.
[Recent EB File List] – The last opened *.ebb file for Profit Controller (RMPCT)
Point Builder. It will be created automatically when an *.ebb file was opened in
Profit Controller Point Builder and will be used as the default-starting file when a
RMPCT Point Builder is opened next time.
[Recent DEB File List] - The last opened *.ebd file for Profit Optimizer (DQP)
Point Builder. It will be created automatically when an *.ebd file was opened in
Profit Optimizer Point Builder and will be used as the default-starting file when a
DQP Point Builder is opened next time.
[Recent File List] - The list of last opened files in Profit Design Studio. It will be
created automatically when Profit Design Studio is closed. They will be used in
the recently opened file list when “File” menu is clicked when Profit Design
Studio is opened next time.
[Recent SIM File List] - The last opened *.sim file for Generic Profit Toolkit
Simulator. It will be created automatically when an *.ebd file was opened in
Generic Profit Toolkit Simulator and will be used as the default-starting file when
Generic Profit Toolkit Simulator is opened next time.
[Color options] – Color options for all views in Profit Design Studio. They are
automatically created and user should not change them manually.
[Settings] – Not used.
Caution Changing default parameters is ill-advised without contacting a Honeywell
consultant.

Honeywell
Section 14 — Installing Profit Assistant
14.1 Overview
In this Section This section explains how to install Profit Assistant.
Important · Profit Assistant has two installation components, one is ProfitAssistant and the
other is ProfitAssistantAddin.
1. Install the ProfitAssistant component on each of the nodes that will be
used to view the controller applications. This includes GUS, APP and
non-TPS nodes.
2. Install the ProfitAssistantAddin component only on the APP or non-
TPS node(s) where the controller applications you want to connect to
with Profit Assistant are running.
· Administrator access is needed to run the install programs.

Honeywell
Section 14 –– Installing Profit Assistant
14.1 Overview
Hardware See Section 1.6 Hardware and Software Requirements.

Requirements
Profit Suite The following Profit Suite software will need to be installed on the APP node or non-
Software TPS node where the controller application is running.
Requirements 1. PHD (Embedded or Oracle-based, needed for trends) (See Section 4) Note
that the Oracle-based PHD doesn’t need to reside on the same node as the
controller applications it just needs to exist.
2. PHD Patch (Needed for Embedded PHD) (See Section 4)
3. Uniformance Desktop (Optional - only required if Profit Assistant will be
used to view controller applications from the node where the applications
reside) (See Section 4)
4. Microsoft System Files (See Section 5)
5. Profit Viewer (Optional - only required if Profit Assistant will be used to
view controller applications from the node where the applications reside)
(See Section 7)
6. Profit Controller (See Section 8)
7. Profit Assistant Addin (See Section 14)
8. Profit Assistant (Optional - only required if Profit Assistant will be used to
view controller applications from the node where the applications reside)
(See Section 14)
The following Profit Suite software will need to be installed on the GUS node or non-
TPS nodes that will be used to view a controller application with Profit Assistant.
1. Uniformance Desktop (See Section 4)
2. Microsoft System Files (See Section 5)
3. Profit Viewer (See Section 7)
4. Profit Assistant (See Section 14)

Honeywell
14.2 Installing ProfitAssistantAddin
Important Only install the ProfitAssistantAddin component on the APP or non-TPS node(s)
where the controller applications you want to connect to with Profit Assistant are
running.
Upgrading Refer to the Release Notes for full details.

From Previous
Versions
Prepare Nodes Follow the directions in Section 2 Preparing for Installation.

for Installation
Installation Before installing ProfitAssistantAddin, make sure the following software has been
· PHD (Embedded or Oracle based, needed for trends) (See Section 4)

· PHD Patch (Needed for Embedded PHD) (See Section 4)
· Uniformance Desktop (Optional - only required if Profit Assistant will be
used to view controller applications from this node) (See Section 4)
· Profit Viewer (Optional - only required if Profit Assistant will be used to
view controller applications from this node) (See Section 7)
· Profit Controller (See Section 8)
Installation To install ProfitAssistantAddin:

4. Double Click on the ProfitAssistantAddin folder.
6. Select [OK} to begin the installation.

Honeywell
Section 14— Installing Profit Assistant
7. Select [Next] on the Information window.
8. If Profit Controller has not been installed, you will get the following
message and the installation will not continue. Select [Ok] to abort the
installation. After installing Profit Controller, rerun the setup for
ProfitAssistantAddin.
Note: For instructions on how to install Profit Controller, refer to Section 8

Installing Profit Controller.

Honeywell
9. If any controller processes are currently active on the machine, you will get
the following message. Select [No] to discontinue the installation. Use the
Private Task Manager utility (privtaskmgr) to stop the controller processes.
Once the processes are stopped, rerun the setup for ProfitAssistantAddin.
Note: For information on how to use the Private Task Manager, see Appendix E.
10. If no controller processes are running, the Welcome window will appear.
Click [Next] to continue the installation.
11. On the Setup Complete window click [Finish] to complete the installation.

Honeywell
14.3 Installing ProfitAssistant
Important Install the ProfitAssistant component on each of the nodes that will be used to view
the controller applications. This includes GUS, APP and non-TPS nodes.
Upgrading Refer to the Release Notes for full details.
From Previous
Versions
Prepare GUS Follow the directions in Section 2 Preparing for Installation.

and APP Nodes
for Installation
Installation Before installing ProfitAssistant, make sure the following software has been
· Uniformance Desktop (See Section 4)

· Profit Viewer (See Section 7)
Installation To install ProfitAssistant:

2. Click [Start]and choose Run. From the Run window, select [Browse].
3. Use the “Look In:’ drop down menu to select the CD drive.
4. Double Click on the ProfitAssistant folder.
5. Double Click on Setup.exe. This action selects the file, closes the Browse
window, and returns the user to the Run Window.
6. Select [OK] to begin installation.

Honeywell
7. Select [Next] on the Information screen
8. If Uniformance Desktop has not been installed, you will get the following
message and the installation will not continue. Select [Ok] to abort the
installation. After installing Uniformance Desktop, rerun the ProfitAssistant
Setup application.
Note: For instructions on installing Uniformance Desktop, refer to Section 4

Installing Embedded PHD Components.

Honeywell
9. If Microsoft System files were not previously installed, you will be prompted to
install them now. Select [Ok] to abort the installation. After installing the
Microsoft System Files (see Section 5 Installing Microsoft System Files), rerun
the ProfitAssistant Setup application.
10. If Profit Viewer has not been installed, you will get the following message and
the installation will not continue. Select [Ok] to abort the installation. After
installing Profit Viewer, rerun the ProfitAssistant Setup application.
11. If any controller processes are currently active on the machine, you will get the
following message. Select [No] to discontinue the installation. Use the Private
Task Manager utility (privtaskmgr) to stop the controller processes. Once the
processes are stopped, rerun the ProfitAssistant Setup application.
Note: For information on how to use the Private Task Manager to view and stop
controller processes, go to Appendix E.

Honeywell
13. Click on [Yes] to accept the License agreement.
14. If other Profit applications are already installed on a certain drive, the following
information box appears indicating the drive where the software will be installed.
Select [Yes] to continue the installation.

Honeywell
15. If there are no locked files, go to Step 16, otherwise the following message will
appear. Select [Ok] to continue.
16. On the Setup Complete window, select [Yes] to restart the computer and click
[Finish].

Honeywell
Section 15 — Installation Wrap-up
15.1 Starting Services

Starting the PHD 1. Click on Start->Settings->Control Panel/Services (Start>Settings>Control
Service Panel>Administrative tools/Services on Windows 2000).
2. On the Services window, click on the Honeywell PHD service set the
Startup Type to Automatic and select [OK].
Starting the TPS 1. Click on Start->Settings->Control Panel/Services (Start>Settings>Control
Admin Service Panel>Administrative tools/Services on Windows 2000).
2. On the Services window, click on the TPS Admin service set the Startup
Type to Automatic and select [OK].
Starting other 1. Click on Start->Settings->Control Panel/Services (Start>Settings>Control
Applications
Panel>Administrative tools/Services on Windows 2000).
2. Restore the original Startup settings for any other services that you
modified in preparation for the upgrade.
Reboot the node Reboot the node to restart the services.

Honeywell
Section 16 — Bringing Profit Controller Online
16.1 Overview
In This Section This section tells you how to install the controller files from the offline design,
enter the initial controller configuration parameters, and link and activate points
for TPS Systems.
With these steps completed, commissioning begins.
Using the Controller Configuration Parameters Configuration parameters are set
Controller Detail
through the Controller Detail screen. Profit Controller (RMPCT) uses control,
Screen
tuning, optimization, and configuration parameters. The start-up parameters you
are going to set here are configuration parameters.
These start-up parameters provide the minimum configuration information that
Profit Controller (RMPCT) requires to link and activate points.
Displaying the Controller Detail Screen To display the Controller Detail
screen, start the display program, Profit Viewer. Select the controller from the
Application Menu and click on the [Controller Detail] button.
For Help For help displaying and using the Profit Controller (RMPCT) screens, see
Section 2.0 in the Profit Controller (RMPCT) Users Guide.
For help making entries on the Controller Detail screen, see:
Section 4.2 in the Profit Controller (RMPCT) Users Guide, and
Section 2.4 in the Profit Controller (RMPCT) Commissioning Reference.

Honeywell
Section 16 – Bringing Profit Controller Online
16.1 Overview
Sharing If the controller will be accessed by Profit Viewer on other nodes, some
directories must be “shared”. The share of C:\users\HiSpec\config directory is
set to MODEL with Read Write Execute permission for authenticated users. The
share of C:\users\HiSpec\Apps directory is set to PROFIT with Read Write
Execute permission for authenticated users. The share of
C:\users\HiSpec\Reports directory is set to REPORT with Read Write Execute
permission for authenticated users. The shares were created when the folders
were created during installation.
Procedure Four files are needed to define a Profit Controller instance. They are:
· Specification file (extension “.xs”) , it contains values for the various
parameters the operator and engineer can set to specify controller
operation. You can optionally specify that this file be read when the
controller is activated to provide starting values for the parameters, or
later to reset the parameter values. If this file is not read when the
controller is activated, the parameter values in the interface points on
the process DCS (e.g. TPS system) will be used as initial values, if they
exist. Otherwise, values in the checkpoint file are used, if it exists.
Limits in the interface points are never overwritten.
· Model file (extension “.xm”), it contains the information that defines the
dynamic model of the process that is being controlled. This file is read
when the controller is activated, and can be read later to update the
model coefficients.
· Configuration file (extension “.cfg”), includes information about the
controller, and it tells the controller where its parameters reside on the
DCS.
· History tag definition file (extension “.csv”) contains the list of
controller parameters to be historized by embedded PHD.

Honeywell
16.2 Installing Off-Line Design Files
This table contains the steps to install the off-line design files onto a PC. Part of this installation
requires that you initialize the Profit Controller (RMPCT) graphics, then enter the .XS and .XM
filenames on the Controller Detail display.
Installing Off-Line Design Files on a PC
Step Action Comment
1 Use NT Explorer to copy the .xs, .xm, .cfg and .csv The Profit Controller setup program created the
files into the directory C:\users\HiSpec\config directory. The off-line RMPCT package created the
on the PC in which the controller is to run. files (in Profit Design Studio ).
2 Run the controller registration utility program See Appendix D.1 on how to use Server Registrar.
ServerRegistrar.exe located in: Important
\Program Files\Honeywell\HiSpec Administrator access is necessary to run this program.
Solutions
This program adds the controller to the registry on the
Or from MS Windows [Start] choose
computer and makes necessary entries in the DCOM
ProgramsàHoneywell HiSpec SolutionsàServer Registrar configuration tables.
3 Select the controller configuration file for the controller to If the controller file is not listed, go back to Step One.
be run on this PC.
4 Click on the [Register] button. A window showing the name
of the controller and the associated configuration,
specification, and model files appears.
THIS STEP IS NECESSARY FOR EACH CONTROLLER.
5 Click the [Register] button.
6 For APP Nodes Only: Configuration Utility is under the Start menu in
Use the Configuration Utility to replicate the controllers Programs>Honeywell TPS. See the TPS System
across the TPS domain. Configuration Utility User’s Guide (TP20xxx - Where
xxx = current revision) for more information on its use.
Note: You must be logged on as the TPS_Administrator to Important: You must use the [Commit and Replicate]
replicate the configuration. button to make the registration permanent. “Replicate”
by itself will overwrite the new registration with the
previously committed information. The new registration
information will be lost if the node is rebooted before
the registration has been committed and replicated.
7 Run the Profit Viewer program.
8 Click [APP MENU] if you are not seeing the list of Profit
Controllers.

Honeywell
Section 16 – Bringing Profit Controller Online
16.2 Installing Off-Line Design Files
9 To access remote applications from nodes not If the controller was not registered, an error message is
participating in a TPS Domain: displayed and Steps 2-6 need to be completed.
Click [Add Profit Viewer Remote Applications], select [GO] Registration of remote controllers in TPS Domains
and browse the network for the computer containing the systems was accomplished during replication in step 6.
controller you want to connect to. Select [Get Apps].
Select the application you wish to connect to. This will
register the controller as a remote DCOM server, on the
local computer. You must repeat this step on each
computer on which you want to use Profit Viewer to
connect to a remote controller.
11 From the Application Status window, click on the This displays the CV Summary for the selected
controller and select [VIEW]. application.
12 Click [CONTROLLER DETAIL] (upper left of the screen). This displays the Controller Detail screen.
13 On the Controller Detail screen, check the .cfg, .XM and The model and spec files are specified when a controller
.XS filenames. is registered using Server Registrar. They can be
· The name of the .XM file is in the Model File field. changed any time from Profit Viewer. Changes from
Profit Viewer are stored in the checkpoint file only and
· The name of the .XS file is in the Specification File
will be used by the controller on startup. Only if the
field.
checkpoint is deleted, or on new controller startup, will
· The name of the .cfg file is in the Configuration file. the registry value be used. See Appendix D for
instructions on how to use the Server Registrar.
14 Keep the Controller Detail screen displayed, and
continue with Section 16.4 (Activating the Program and
Reading in the Design files).

Honeywell
16.3 Removing Controllers
\Removing A controller must only be installed on one and only one PC at a time. If you want
Controllers
to move a controller to a different PC or reinstall a controller, the controller must
first be removed from the PC it is currently installed on.
Follow these steps to remove a controller properly:
1. Log on as an Administrator (TPS Administrator for TPS Domains)
2. Run ServerRegistrar (Start->Programs->Honeywell HiSpec-
>ServerRegistrar).
3. Verify that the application is in the OFF mode (Status shown as “Control
Off” or “Optimizer Off”). Use the [View] button to run ProfitViewer to
change the status if necessary.
4. Verify that any application using this controller is also in the OFF mode.
Use ProfitViewer to change the status if necessary.
5. If any other applications are using this application, use the [Inactivate]
button to set their status to Inactive. This will prevent this application from
being re-activated by another application.
6. Close any Profit Viewers that are connected to the application. Select the
application to remove, and press the [Terminate] button to stop the
application from execution. The TPS Status Display, Stop function may also
be used for this purpose.
7. After the status of the application becomes “Not Running”, press the
[Remove] button to remove the registration of this application. If you are in
a TPS domain, replicate the domain now.
Once the controller has been removed, follow procedures in this section to install
it on another PC.

Honeywell
16.4 Activating the Program and Reading In the Design Files
Invoke the Start Profit Viewer either from the desktop icon or through
Controller Start\Programs\Honeywell HiSpec Solutions. This will display the App Menu. An
example is shown below.
If this is a node in the TPS Domain, all local and remotely registered applications
should be listed in the Profit Viewer Application Status frame. If this node is not
in a TPS Domain, and the controller is located remotely select the Program
Applications pull down menu and select Add Profit Viewer Remote Application.

Honeywell
Section 16— Bringing Profit Controller Online
On the Add Remote Application window, select the node then the [Get Apps]
button. Select the desired controller and click [Add].
Add Controller to The plant workspace allows you to customize your access by listing, in your
the Plant predetermined order, the controllers that interest you. Browse the list on the Profit
Viewer Application Status frame and click on the desired controller. Drag the
Workspace
controller from this frame over to the desired position in the Plant Workspace
frame.

Honeywell
Section 16— Bringing Profit Controller Online
Remove To remove the controller, select the controller in the Plant Workspace and drag the
Controller from icon to the garbage bin icon on the upper right side of the screen. This will remove
the controller from the Plant Workspace.
the Plant
Workspace
Access the Click on the controller in the Plant Workspace. Click [Yes] to the prompt asking if
Controller you want to connect to the controller. The CV Summary page will be displayed.
To pick another controller to view, select the [App Menu] button and repeat the
above procedure.
Activating the In the lower right portion of the Controller Detail display is a field showing the
Controller Point Application Status. If it shows INACTIVE, click on it to change it to ACTIVE.
Checking the When an application is first installed the [File Read] and [Last Execution] fields
Read-File on the Controller Detail screen will be blank. These fields indicate when the
controller last read the controller files and executed.
Stamps
The model file is read automatically at start-up. The Read Model [Model] target
will be back-lit until the file has been read. If you want to overwrite the settings
currently being used by the controller with the settings in the .xm file, click the
[Read Model File] Button.
First-Time Start- If this is the first time ever that the controller has been started, click [Read Spec
up File]. This will read starting default values for all parameters except limits (which
should be entered manually). On subsequent restarts, the values will be obtained
from the controller’s checkpoint file, or from the DCS if the value is configured
for read from the DCS. Generally, you do not want to use [Read Spec File] after
the first-ever start, because this would overwrite any modifications that have been
made to the default starting values.
Note: Anytime that you change significant parameters, it is a good idea to click
the [checkpoint] button to ensure that the changes are saved for subsequent
restarts.
Commissioning With the controller successfully online, you are ready to commission. If you are
the Controller on a TPS System, see the Profit Controller (RMPCT) Commissioning manual for
help.

Honeywell
Section 17 — Bringing Profit Toolkit Online
17.1 Bringing Profit Toolkit Online

Configuration File Once the user configures a Toolkit application using the Profit Design Studio
(APCDE) application, a configuration file (ApplicationName.cfg) is built and put
in the users\HiSpec\config folder of the current machine. Copy this file into the
users\HiSpec\config folder of the NT machine on which Toolkit application is to
be executed online.
Sharing If the toolkit application will be accessed by Profit Viewer on other nodes, some
directories must be “shared”. The share of C:\users\HiSpec\config directory is
set to MODEL with Read Write Execute permission for authenticated users. The
share of C:\users\HiSpec\Apps directory is set to PROFIT with Read Write
Execute permission for authenticated users. The share of
C:\users\HiSpec\Reports directory is set to REPORT with Read Write Execute
permission for authenticated users.
Procedure There is only one file that is needed to define a Toolkit application instance.
· Configuration file (extension “.cfg”), which tells the toolkit application
where its parameters reside.

Honeywell
Section 17 - Bringing Profit Toolkit Online
17.1 Bring Profit Toolkit Online
The following table contains the steps required to bring a Toolkit application online.
Step Action Comment
1 Use NT Explorer to copy the .cfg file into the NT The Profit Suite setup program created the directory. The
directory off-line PDS package created the file and stored it in the
C:\users\HiSpec\config config directory of the current machine.
in the PC the toolkit is to run in.

2 Run the registration utility program See Appendix D.1 on how to use Server Registrar.
ServerRegistrar.exe located in: Important
\Program Files\Honeywell\HiSpec Administrator access is necessary to run this program.
Solutions
The registration utility must be run on the computer
Or from MS Windows [Start] choose that the Profit Toolkit is going to execute on.
ProgramsàHoneywell HiSpec SolutionsàServer The first time a Profit Toolkit is registered on the
Registrar computer, a local user “ProfitUser” with a password of
“password” will be assigned as the user. All Profit
Toolkits run under this user account.
This program adds the Toolkit to the registry on the
computer and makes necessary entries in the DCOM
configuration tables.
3 Select the toolkit configuration file for the toolkit to be If the toolkit file is not listed, go back to Step One.
run on this PC.
4 Click on the [Register] button
THIS STEP IS NECESSARY FOR EACH TOOLKIT.

Honeywell
Section 18 — Security
18.1 Overview
Security Basics Security configuration has two aspects:
1. Application Security - Defines which users and/or computers have

write access to a Profit Suite application.
2. Security Role Configuration – Defines the security role assigned to a
given user. For instance, the logged in user may be treated as an
Operator, Supervisor, Engineer, or Administrator.
Important Note The TPS SignOn Manager impersonates a user. The Security Role is determined
about the SignOn based on this effective user (i.e. the one signed in from the SignOn Manager) if
Manager the SignOn Manager is installed, and based on the logged-in user if the SignOn
Manager is not installed.
The TPS SignOn manager – even if installed - has no impact on the
determination of Application Security settings. Application Security settings are
always based on the logged in user.

Honeywell
18.2 Application Security
Application Application security determines which users have write access to a given
Security application. Application security also defines from which computers a given
application permits write access.
Application Security is configured via the Server Registrar. When an application
is first registered the default application user security is for “Everyone” (meaning
all users) to have write access. Access may be restricted by removing
“Everyone” and adding specific groups and/or users.
Via the Server Registrar the computers from which write access is permitted may
also be configured. When an application is first registered the default application
computer security is for write access to be permitted from all computers. Write
access to a given application may be restricted to only specific computers.
Application Security is described in more detail in the Server Registrar section of

this document.
What is the Some sites set up their system so that operators always log in under a blanket
Purpose of “Operator” account. This diminishes the use of user-based security because there
Application is no way to distinguish between different operators.
Computer
These sites may configure Profit Suite applications to only allow write access
Security?
from specific computers where the responsible operator works. For example, it is
possible to say that APP1 may only be controlled from COMPUTERS 1 and 2.

8/02
Honeywell
18.3 Security Role Configuration
Security Roles The Profit Suite Graphical User Interfaces (GUIs), such as ProfitViewer ,
ProfitAssistant, and ServerRegistrar allow or disallow various functions based on
the security role assigned to the currently logged in user. For instance,
ProfitViewer will only allow limit changes for a specific security role.
Historically, the security role was determined by requiring the user to log in to
the graphical application each time it was run. Starting with Release 205,
individual programs do not require a local log in and the user’s security role is
assigned as described below.
Basics This section does not discuss what privileges a particular GUI grants a user with
a specific security role (this is detailed in the GUI documentation).1 Rather this
section explains how a particular logged-in user’s security role is established. For
example, this section explains how to configure the system so that the GUIs treat
one user like an engineer while another user is treated like an operator.
The Security Roles Eight security roles are supported. They are listed in order of decreasing
responsibility. A user belonging to a given security role may perform the
functions allowed for the role to which they are assigned, and all lower roles:
· Administrator
· Engineer
· Supervisor2
· Supervisor
· Operator3
· Operator2
· Operator
· View Only
Capability Files Users are assigned to a security role based on whether or not they have Execute
(RX) permissions on a capability file. A user is assigned to the security role
1Note that some GUIs allow the end-user to configure what a logged-in user with a specific capability
has. For example, what a user with “Operator” capability is allowed to do.
Honeywell
Section 18- Security
18.3 Security Role Configuration
matching the highest capability file to which they have Execute permission.
For example, users with RX permissions on the engineer capability file will be
treated by the GUIs as an engineer. Similarly users with RX permissions on the
operator capability file have operator capability.
TPS Domain The security for a TPS Domain is setup slightly differently than the security for a
Versus Non-TPS non-TPS domain. These scenarios are discussed separately below.
Domain

Honeywell
18.4 TPS Domain Security
Step by Step The following describes a step-by-step approach to setting up security. The
Approach to following sections go into more detail. Please also refer to the TPS
Setting TPS documentation (TPS Administration Guide: TPS Security) for greater detail.
Security
1. Determine which of your users are to be assigned to the roles operator,
supervisor, engineer and administrator.
2. On the Primary Domain Controller (PDC) for the Microsoft Windows
domain hosting the TPS Domain make the operators’ members of the
Operators group, supervisors’ members of the Supervisors group,
engineers’ members of the Engineers group, and administrators’
members of the TPS Administrators group.
3. On the PDC remove the “Everyone” group from the PS_Administrator
file (if you don’t everyone will have administrator access).
4. Do a Replicate, and the security files will be copied to the other nodes
on the TPS domain and the capability configuration will be complete.
5. When registering an Application on the Server Registrar, do the
application security settings for that application.
Default The TPS system installation software creates several Domain groups (Operators,
Configuration Supervisors, Engineers, TPS Administrators). When the Profit Suite software is
installed, these groups are also automatically associated with an appropriate
capability file. For example, the Operators group will be granted privileges on
the “operator” capability file; the Supervisors group privileges on the
“supervisor” capability file, and so on.
In order for your operators to be assigned to the “operator” security role, all you
need to do is add all your operators to the Operators group.
Capability Files The privileges associated with seven capability files that are created during the
Profit Software installation determine the access levels. The files are:
Filename Security File Description
PS_ADMINISTRATOR Users having RX permission on this file
have administrator rights.
PS_ENGINEER Users having RX permission on this file
have engineer rights.
PS_SUPERVISOR Users having RX permission on this file
have supervisor rights.
PS_SUPERVISOR2* Users having RX permission on this file
have supervisor2 rights.

Honeywell
PS_OPERATOR Users having RX permission on this file

have operator rights.
PS_OPERATOR2* Users having RX permission on this file
have operator2 rights.
PS_OPERATOR3* Users having RX permission on this file
have operator3 rights.
The users and groups that have Execute permissions to these files determine
security permissions. For instance, if a group and/or user is configured with
Execute permissions on the PS_Engineer files, then the user is assigned to the
Engineer security role. Similarly a user/group with permission to the
PS_Operator file will be assigned to the Operator security role.
Note that except for removing “Everyone” permissions from the

PS_Administrators file there should be no reason to change the permissions on
any of the other capability files.
* The extra operator and supervisor capability files have no associated groups. In
order to use this extra functionality the users must associate these files with an
appropriate group. For example, all supervisors who also have administrative
privileges (i.e. assigned to both Administrators and Supervisors groups) or
operators who also have supervisor privileges, etc.

Honeywell
How to Determine Determining the security role is simple.

Security Role
1. Right-click on the desired capability file.
2. Select the Security tab.
3. Select a particular user (e.g. Everyone is selected in the diagram below).
4. View the Permissions settings. Users with RX privileges have
permission. Users that do not have RX privileges do not have
permission. (Note that as one would expect, in the example below the
TPS Administrators group has RX privileges to the PS_Administrator
file).
The following is an example of the default PS_Administrator file:
Important Note: Because the Everyone group has Read and Execute permissions in the
Remove PS_Administrator file, the default for every user is Administrator. This means
“Everyone” that every user logging into the system will have Administrator access to all
Permissions From Profit Suite GUIs. In order to disable this, the Everyone group must be removed
PS_Administrator from PS_Administrator file.
File

Honeywell
Section 18— Security
TPS Groups The following Microsoft Windows groups are automatically created by the TPS
installation software:
· Operators
· Supervisors
· Engineers
· TPS Administrators
· View Only Users
Important Note: Do not confuse the Operators group with the “TPS Operators”
group. It is the Operators group that is associated with the PS_Operators
capability file. The same is true for Supervisors and Engineers, however there is
only one administrators group and it is called “TPS Administrators”; as such it is
the relevant group.
Also note that the following local groups are created by Profit Suite installation
software but are not used in a TPS domain (they are only used in a non-TPS
domain) PS_Operators, PS_Supervisors, PS_Engineers and PS_Administrators.
Assigning Users to The main configuration step is for the end-user to add the appropriate users to the
the TPS Groups TPS groups. This should be done on the PDC. For example, operators should be
added to the Operators group, etc.

Honeywell
TPS Domain Security
Replication On a TPS domain the capability files are located on the Primary Domain
Controller (PDC). When replication occurs, these files are copied to all the
computers in the TPS domain. Because of this it is imperative that any
configuration of the security files be done on the PDC. Note that any
configuration to the capability files done on the other computers in the domain
will be overwritten when replication occurs.
For the capability configuration to become active, a replication should be

invoked after any changes are made to the capability files.
What Directory on On a TPS system, the seven capability files are created in the
the PDC are the /winnt/system32/repl/export/HWIAC/TPSDomainx/security directory (where x is
Capability Files the number of the Domain) when the Profit TPS Server software is installed on
Located in? the TPS Domain’s PDC. If there is only one domain, then x is 1. The name of
the TPS domain is given by the name of the file in the TPSDomainx directory
with a .nam suffix. For instance, if a domain is named BlueZone, then a file
named BlueZone.nam appears in the
/winnt/system32/repl/export/HWIAC/TPSDomainx directory on the PDC.
During replication, the files are copied to the following directory on the TPS
domain computers: /HWIAC/Security.

Honeywell
18.5 Security Scenario TPS Domains – Application Security
and Security Role Configuration
Security Scenario Let us assume security is configured for two Profit Controller applications. One
controller controls the fractionator and is called FRAC, and the other application
controls the FCCU and is called FCCU.
Consider the following personnel:
FRAC FCCU FRAC FCCU Engineers

Operator Operator Supervisor Supervisor FRAC &
FCCU
Microsoft FRACOPR1 FCCUOPR1 FRACSUP1 FCCUSUP1 ENG1

Windows
FRACOPR2 FCCUOPR2 FRACSUP2 FCCUSUP2
Login Name
FCCUOPR3
Consider the following computer configuration at site:
Computer1 Computer2 Computer3 PDC
Fractionator FCCU
Control Room
What NT/WIN2K This describes the configuration required to allow only fractionator personnel to
Configuration is access the FRAC application from computers 1 and 2, and FCCU personnel
Required? access to the FCCU application only from computers 2 and 3.
The first thing to do is create the user accounts on the primary domain controller;
FRACOPR1, FRACOPR2, FCCUOPR1, FCCUOPR2, FCCUOPR3, FRACSUP1, FRACSUP2,
FCCUSUP1, FCCUSUP2, and ENG1.

8/02
Honeywell
18.5 Security Scenario TPS Domains – Application Security and Security Role Configuration
What Application The following application security is required for the FRAC application:
Security
· Remove the “Everyone” group via the Server Registrar security (if you
Configuration is
don’t everyone will have access to the application).
Required?
· Add the FRAC Operators (FRACOPR1, FRACOPR2), FRAC
Supervisors (FRACSUP1, FRACSUP2) and Engineer ENG1 to the
users/groups with access to the application via the Server Registrar
security.
· Add Computer1 and 2 to the computers with access to the application

via the Server Registrar security.
The following application security is required for the FCCU application:

· Add the FCCU Operators (FCCUOPR1, FCCUOPR2), FCCU
Supervisors (FCCUSUP1, FCCUSUP2) and Engineer ENG1 to the
users/groups with access to the application via the Server Registrar
security.


123
Honeywell
18.5 Security Scenario TPS Domains – Application Security and Security Role Configuration
Security Role The following security role configuration is required:

Configuration
· On the PDC add the FCCU Operators (FCCUOPR1, FCCUOPR2) and
FRAC Operators (FRACOPR1, FRACOPR2) to the Operators group.
· On the PDC add the FCCU Supervisors (FCCUSUP1, FCCUSUP2) and

FRAC Supervisors (FRACSUP1, FRACSUP2) to the Supervisors
group.
· On the PDC add the Engineer ENG1 to the Engineers group.

Do a replicate and the security configuration job is complete.
NT/WIN2K
Global Group Operators Supervisors Engineers
NT/WIN2K FRACOPR1 FRACSUP1 ENG1
Member FRACOPR2 FRACSUP2
FCCUOPR1 FCCUSUP1
FCCUOPR2 FCCUSUP2
FCCUOPR3
Outcome of If FRACOPR1 is logged in to any computer and attempts to operate the FCCU
Security Scenario application then he will only be granted view only privileges.
If FRACOPR1 is logged in to Computer 3 and attempts to operate the FRAC

application then he will only be granted view only privileges.
If FRACOPR1 is logged in to Computer 1 or 2 and attempts to operate the FRAC

application then he will only be granted “operator” privileges.
If FCCUOPR1 is logged in to Computer 2 or 3 and attempts to operate the FCCU

If ENG1 is logged in to Computer1, “engineer” privileges are granted by FRAC
and view only privileges are granted by FCCU.
If ENG1 is logged in to Computer2, “engineer” privileges are granted by both
FRAC and FCCU.
If ENG1 is logged in to Computer3, “engineer” privileges are granted by FCCU

and view only privileges are granted by FRAC.

Honeywell
18.6 Non-TPS Domain Security
Step by Step The following describes a step-by-step approach to setting up security. The
Approach to following sections go into more detail.
Setting TPS 1. Determine which of your users are to be assigned to the roles operator,
Security supervisor, engineer and administrator.
2. On each computer that will host Profit Suite applications, make the
operators’ members of the PS_Operators group, supervisors’ members
of the PS_Supervisors group, engineers’ members of the PS_Engineers
group, and administrators’ members of the PS_Administrators group.
3. On each computer that will host Profit Suite applications, remove the
“Everyone” group from the PS_Administrator file (if you don’t
everyone will have administrator access).
4. When registering an Application via the Server Registrar do the
application security settings for that application.
Default The Profit Suite installation software creates the local groups: PS_Operators,
Configuration PS_Supervisors, PS_Engineers, PS_Administrators on each node on which it is
installed. These groups are also automatically associated with an appropriate
capability file. For example, the PS_Operators group will be granted privileges
on the “operator” capability file; the PS_Supervisors group privileges on the
“supervisor” capability file, and so on.
In order for your operators to be assigned to the “operator” security role, all you
need to do is add all your operators to the PS_Operators group on each node that
they will log into.
Capability Files The privileges associated with seven capability files that are created during the
Profit Software installation determine the access levels. The files are:
Filename Security File Description
PS_ADMINISTRATOR Users having RX permission on this
file have administrator rights.
PS_ENGINEER Users having RX permission on this
file have engineer rights.
PS_SUPERVISOR Users having RX permission on this
file have supervisor rights.
PS_SUPERVISOR2* Users having RX permission on this
file have supervisor2 rights.
PS_OPERATOR Users having RX permission on this
file have operator rights.
PS_OPERATOR2* Users having RX permission on this
file have operator2 rights.

Honeywell
Section 18 – Security
PS_OPERATOR3* Users having RX permission on this

file have operator3 rights.
The users and groups that have Execute permissions to these files determine
security permissions. For example, if a group and/or user is configured with
Execute permissions on the PS_Engineer files, then the user is assigned to the
Engineer security role. Similarly, a user/group with permission to the
PS_Operator file will be assigned to the Operator security role.
It should be noted, that except for removing “Everyone” permissions from the
PS_Administrators file, there should be no reason to change the permissions on
any of the other capability files.
* The extra operator and supervisor capability files have no association to
standard capability groups. In order to use this extra functionality, the user must
associate these files with the appropriate groups for which the capability will be
used (e.g. to identify Supervisors who also have engineer capability).

Honeywell
How to Determine Determining the security role is simple.

Security Role
1. Right-click on the desired capability file.
2. Select the Security tab.
3. Select a particular user (e.g. Everyone is selected below).
4. View the Permissions settings. Users with RX privileges have permission.
Users that do not have RX privileges do not have permission. (Note that as
one would expect, in the example below the PS_Administrators group has
RX privileges to the PS_Administrator file).
The following is an example of the default PS_Administrator file:
Important Note: Because the Everyone group has Read and Execute permissions in the

Honeywell
Remove PS_Administrator file, the default for every user is Administrator. This means
“Everyone” that every user logging into the system will have Administrator access to all
Permissions From Profit Suite GUIs. In order to disable this, the Everyone group must be removed
PS_Administrator from PS_Administrator file.
File
Profit Suite Local The following Microsoft Windows local groups are automatically created by the
Groups Profit Suite installation software:
· PS_Operators
· PS_Supervisors
· PS_Engineers
· PS_ Administrators
Assigning Users to The main configuration step is for the end-user to add the appropriate users to the
the local Profit Microsoft Windows groups. This should be done on each computer onto which
Suite Groups the users will login. For example, operators should be added to the PS_Operators
group, etc.
Ideally, Domain groups for each category of users are created on the PDC. The
appropriate domain users are added to each of these groups. Then the
appropriate group is added to the associated PS_* group on each node where
Profit Suite software is to execute.
No Replication on Since there is no replication capability on non-TPS domains, the end-user must
Non-TPS Domains make changes on each of the computers where security is required.
What Directory on On a non-TPS system, the seven capability files are created in the
the PDC are the \HWIAC\Security directory on each computer.
Capability Files Note: the \HWIAC\Security\PS_* capability files and the PS_* local groups are
Located in? only created the first time a Profit Suite package is installed. Configuration
changes made are not overwritten. Therefore, to return to default settings, the
files and groups must be deleted, the re-installed. All of the R205 and newer
Profit Suite packages install these files.

Honeywell
18.7 Security Scenario Non-TPS Domains – Application
Security and Security Role Configuration
Security Scenario Let us assume security is configured for two Profit Controller applications. One
controller controls the fractionator and is called FRAC, and the other application
controls the FCCU and is called FCCU.
Consider the following personnel at site:
FRAC FCCU FRAC FCCU Engineers

Operator Operator Supervisor Supervisor FRAC &
FCCU

Windows
Login Name
FCCUOPR3
Consider the following computer configuration at site:
Computer1 Computer2 Computer3 PDC
Fractionator FCCU
Control Room

Honeywell
18.7 Security Scenario Non – TPS Domains- Application Security and Security Role
Configuration
What NT/WIN2K This describes the configuration required to allow only fractionator personnel to
Configuration is access the FRAC application only from computers 1 and 2, and FCCU personnel
Required? access to the FCCU application only from computers 2 and 3.
The easiest thing to do is to first create the following NT/WIN2K Domain groups
on the PDC containing the following members.
Microsoft FRAC FCCU FRAC FCCU Engineers

Windows Operators Operators Supervisors Supervisors
Group

Windows
Group
Members FCCUOPR3

Honeywell
Configuration
What Application The following application security is required for the FRAC application:
Security
Configuration is
Required?
· Add the FRAC Operators, FRAC Supervisors and Engineers groups to
the users/groups with access to the application via the Server Registrar
security.

The following application security is required for the FCCU application:

· Add the FCCU Operators, FCCU Supervisors and Engineers groups to

the users/groups with access to the application via the Server Registrar
security.


Honeywell
Configuration
Security Role The following security role configuration is required:

Configuration
· On each computer add the FCCU Operators and FRAC Operators group
to the PS_Operators group.
· On each computer add the FCCU Supervisors and FRAC Supervisors

group to the PS_Supervisors group.
· On each computer add the Engineers group to the PS_Engineers group.
Outcome of If FRACOPR1 is logged in to any computer and attempts to operate the FCCU
Security Scenario application then he will only be granted view only privileges.
If FRACOPR1 is logged in to Computer 3 and attempts to operate the FRAC
application then he will only be granted view only privileges.
If FRACOPR1 is logged in to Computer 1 or 2 and attempts to operate the FRAC

If FCCUOPR1 is logged in to Computer 2 or 3 and attempts to operate the FCCU
If ENG1 is logged in to Computer1, “engineer” privileges are granted by FRAC

and view only privileges are granted by FCCU.
If ENG1 is logged in to Computer2, “engineer” privileges are granted by both
FRAC and FCCU.
If ENG1 is logged in to Computer3, “engineer” privileges are granted by FCCU
and view only privileges are granted by FRAC.

Honeywell
Appendix A — Datapool Descriptions
A.1 Datapool Overview

Overview For ease of use, the Datapool Table has been divided into separate tables as show
below.
The Profit Controller Datapool parameter tables
Profit Controller Common Parameters
Profit Controller CV Parameters
Profit Controller MV Parameters
Profit Controller DV Parameters
Profit Optimizer Datapool parameter tables
Profit Optimizer Controller Parameters
Profit Optimizer Combined Constraint Parameters
Profit Optimizer BOut Parameters
Profit Optimizer DVBIn Parameters
Profit Optimizer MVBIn Parameters
Profit Toolkit Datapool parameter table
Profit Toolkit Common Parameters
Gain Extraction Dependent Parameters
Gain Extraction Independent Parameters
Gain Extraction Gain Parameters
Gain Extraction Parameters

Honeywell
A.2 Profit Controller Datapool Parameters
Hint: To monitor a given item, select the Item Name field, copy, and paste into the New Item Id field in
HSMiniBrowser.
Profit Controller Common Parameters
Name Type Length Writeable Description
NumberofCVs Float 1 FALSE Number of controlled variables, from config file
NumberofMVs Float 1 FALSE Number of manipulated variables, from config file
NumberofDVs Float 1 FALSE Number of disturbance variables, from config file
InitializationPassCounter Float 1 TRUE Initialization pass counter
UseBridgeUFP Float 1 TRUE 0: don't use bridge UFP, 1: use bridged DVs UFP
OptimizerSpeedFactor Float 1 TRUE Normalized optimizer speed
Value of CV error minimization part of objective
TotalPredictedError Float 1 FALSE function
1: online gain delay changes allowed, !=1: not
GainDelayLock Float 1 TRUE allowed. Local to display.
CCFTolerance Float 1 TRUE External CCF tolerance.
External CCF display flag. 0: constraint conflict,
ControllerStatus Float 1 FALSE 1: optimizing, 4: control ok.
AutoRHPWeights Float 1 TRUE 1: auto weights for rhp poles, !=1: user weights
SSError Float 1 FALSE Error in SS
DesignExecPeriod Float 1 FALSE Design control execution interval (minutes)
URV tolerance for RCA. Controller reads this
URVTolerance Float 1 TRUE from the model file.

8/02
Honeywell
Appendix A- Datapool Descriptions
A.2 Profit Controllers Data Pool Parameters
PredictionBias Float 1 TRUE 1: y_sol_p starts at y, 0: starts at y_est

PerfRatioBackoffTolerance Float 1 TRUE External tolerance to control the ratio backing off
Non-LCN only (AxM, VAX, PC, etc). 0: PreRCA
should NOT be used, != 0: PreRCA should be
used. This value is read once when rmpc_setup
UsingPreRCA Float 1 TRUE is run, then it is ignored until program is restarted.
Display state, -2: shed, 0: off, 1: on, 2: init, 11:
ControllerMode Float 1 FALSE warm
Allows user to copy objective data from one set to
ObjectiveDataCopy Float 1 TRUE another.
SkipXMCheck Float 1 TRUE 0: force ym_consistency_check, else skip
if the current objective function value is within the
OptimizationAcceleration tolerance (in percent) then the optimization is
Tolerance Float 1 TRUE accelerated
under simulation divide execution interval by this
SpeedUpFactor Float 1 TRUE - when 0 pause simulation
IntervalCounter Float 1 FALSE increment after each interval is complete
0:Don't include integrators in resp. time calcs;
.LT.=1 Include fraction of integrators CLRI in
IncludeIntegratorCLRI Float 1 TRUE calcs
1: online gain delay changes can be made,
!=1:online gain delay changes cannot be made.
GainDelayFlag Float 1 FALSE Used by US displays.
version of last .xm or .xs file read successfully or
FileVersion Float 1 FALSE not
DeflatedSingularValue Float 1 FALSE largest singular value dropped 'cause of URV_tol'
SSDeflatedSingularValue Float 1 FALSE largest singular value dropped 'cause of URV_tol'

Honeywell
Appendix A – Datapool Descriptions
SSObjectiveValue Float 1 FALSE SS Objective Function value of Local optimization

Cur Objective Function value of Local
CurObjectiveValue Float 1 FALSE optimization
DQP mode 1:NON-EXISTS, 1.5:NON-EXISTS
DQPMode Float 1 FALSE but establish pointers 2:OFF, 3:ON, 4:WARM
PredictorCounter Float 1 FALSE Useful in debugging, same as kt
RMPCTVersion Float 1 FALSE Available for info
DQPAliveFlag Float 1 TRUE Status of DQP point. 0: inactive, 1: active.
OverallResponseTime Float 1 FALSE Application Response Time
EffectiveOptimizerSpeed Float 1 FALSE Effective optimizer speed for integrators
NowAlarm FloatArray 25 FALSE Current alarms
PrevAlarm FloatArray 25 FALSE Previous alarms
UpdateFlags FloatArray 5 TRUE Update flag. Presently not used by OpenRMPCT.
WholeRMPCRecord FloatArray 109 FALSE Use to read all RMPC controller record
On loss of non-critical MV 1: Turn Controller OFF,
NonCriticalMVLoss Float 1 TRUE 0: No Action
Request controller state, 1: ON, 0: OFF, 11:
TurnONOFF Float 1 TRUE Warm
ReadModelFlag Float 1 TRUE 1: Read Model w/ Init, 2: Read Model w/o Init
ReadSpecFlag Float 1 TRUE 1: Read Specification File
Absolute, use Read_Model_Flag instead; delete
this after all reference to this parameter has been
ReadWhileON Float 1 TRUE removed.
ControllerState Float 1 FALSE Not used by OpenRMPCT
Number of initialization passes allowed for this
MaxIntervalsInInit Float 1 TRUE controller
Actual number of initialization passes that have
NumIntervalsInInit Float 1 FALSE occurred
UpdateHistory Float 1 TRUE 1: Update history, 2: update complete
DQP state 2:OFF, 3:ON, 4:WARM, 5:WAITING,
DQPState Float 1 TRUE 6:INIT
Simulation server in use (0: no; 1: yes). Only for
SimServerUsed Float 1 TRUE DSS simulation.
ExecutionInterval Float 1 FALSE Actual execution interval, minutes.
Actual execution interval, minutes - as measured
MeasuredExecutionInterval Float 1 FALSE by the exec
ExecutionSubInterval Float 1 FALSE Execution sub interval, minutes.
ExecutionOffset Float 1 FALSE Execution offset, minutes.

Honeywell
Max consecutive intervals allowed for bad input

MaxNotAllowedBad Float 1 TRUE for not-allowed-bad parameter
Number of consecutive intervals with bad input
NumNotAllowedBad Float 1 FALSE for not-allowed-bad parameter
Overruns Float 1 TRUE Overruns for this process
SubOverruns Float 1 FALSE Sub overruns for this process
Simulation reset, 1: reset. Only for DSS
SimReset Float 1 TRUE simulation.
CheckPointInterval Float 1 TRUE Check Point Interval
DemandCheckPoint Float 1 TRUE Demand Check Point
Allows other processes to schedule intervals by
RunIntervalFlag Float 1 TRUE setting this to non-zero
ControlRestart Float 1 TRUE Reset control and prediction, !=0: reset.
Proceed with solver calculations. 1=True;
DoSolverCalcs Float 1 FALSE 0=False
KeepRunning Float 1 TRUE Set to 0 to terminate controller program.
Each entry controls a Pascal debug flag for
DebugFlags FloatArray 48 TRUE debug messages - 1.0 to turn on
1 means the 10 most recent executions, 0 means
NumDebugFiles Float 1 TRUE all executions
Number of Toolkit functions specified in the
NumberFunctions Float 1 TRUE configuration file
Number of functions that return non-zero
NumberFunctionsBad Float 1 TRUE Ret_Status in current interval
DisplayedStatus Float 1 FALSE ordinal indicating status string for displays

Honeywell
GDIdentity Float 1 FALSE Internal use only.

1: original gain, delay, and max_delay have been
written to cds from pool, !=1: write original
GainDelayWritten Float 1 FALSE parameters to cds.
GainDelayChanged Float 1 TRUE 1: process gain/delay changes.
ClearGainDelay Float 1 TRUE 1: clear gain/delay changes.
Gain FloatArray 2000 FALSE gain read from model file
DeadTime FloatArray 2000 FALSE delay read from model file
MaxDeadTime FloatArray 2000 FALSE max allowed delay read from model file
GainMultiplier FloatArray 2000 TRUE user specified multiplier for gains (default is 1)
DeadTimeBias FloatArray 2000 TRUE +/-' N115 value for delay (default is 0)
NumberofSubModels Float 1 FALSE The number of sub models for this controller
Max. number of overruns before controller shuts
MaxOverruns Float 1 TRUE itself off (when self-scheduled)
CalcStartIntTime String 0 FALSE Calculation start interval time
StartIntervalTime String 0 FALSE Start interval time
EndControlTime String 0 FALSE End control time
CalcStartSubIntTime String 0 FALSE calculation start sub interval time
StartSubIntervalTime String 0 FALSE Start sub interval time
EndSubIntervalTime String 0 FALSE End sub interval time
LastModelFileName String 0 TRUE Last Model File actually read
LastSpecFileName String 0 FALSE Last Spec File Actually read
ControllerName String 0 FALSE Controller Master Name
ControllerDescription String 0 TRUE Controller Description
ModelFileName String 0 TRUE Model File Name
SpecFileName String 0 TRUE Specification File Name
ConfigFileName String 0 FALSE Configuration File Name
Process Model File Name. Only for DSS
ProcessModelFileName String 0 TRUE simulation.
CheckPointName String 0 TRUE Check Point File Name
LastCheckpointFileName String 0 FALSE Name of last Checkpoint file read in
LastCheckpointReadTime String 0 FALSE Time of last checkpoint file read
LastCheckpointWriteTime String 0 FALSE Time of last checkpoint file was written
LastModelReadTime String 0 FALSE Time of last model file read
LastExecDuration String 0 FALSE Duration of last execution interval (mm:ss.sss)

Honeywell
LastHistoryUpdateTime String 0 FALSE Time of last history configuration update

ACTIVE - running control calculations, INACTIVE
ApplicationStatus String 0 TRUE not and default
OmodIdentity Float 1 FALSE Identity number
OddDQPModelID Float 1 TRUE model_id (odd model counter)
OddScalar1 Float 1 FALSE n_cv (number of CVs in this app)
OddScalar2 Float 1 FALSE n_mv (number of MVs in this app)
OddScalar3 Float 1 FALSE n_dv (number of DVs in this app)
n_exist_spr (number of non-null models in this
OddScalar4 Float 1 FALSE app)
OddScalar5 Float 1 FALSE design execution frequency
OddArray1 FloatArray 2000 FALSE packed IJp - index to non-null models
OddArray2 FloatArray 2000 FALSE packed unweighted SS gains
OddArray3 FloatArray 200 FALSE Dr (row/CV scaling)
OddArray4 FloatArray 100 FALSE Dc (column/MV scaling)
OddModelIFVersion Float 1 FALSE Version of RMPCT Model interface CDS
WholeOddModeltoDQP FloatArray 5008 FALSE
EMODIdentity Float 1 FALSE Identity number
EvenDQPModelID Float 1 TRUE model_id (odd model counter)
EvenScalar1 Float 1 FALSE n_cv (number of CVs in this app)
EvenScalar2 Float 1 FALSE n_mv (number of MVs in this app)
EvenScalar3 Float 1 FALSE n_dv (number of DVs in this app)
EvenScalar4 Float 1 FALSE app)

Honeywell
EvenScalar5 Float 1 FALSE design execution frequency

EvenArray1 FloatArray 2000 FALSE packed IJp - index to non-null models
EvenArray2 FloatArray 2000 FALSE packed unweighted SS gains
EvenArray3 FloatArray 200 FALSE Dr (row/CV scaling)
EvenArray4 FloatArray 100 FALSE Dc (column/MV scaling)
EvenModelIFVersion Float 1 FALSE Version of RMPCT Model interface CDS
WholeEvenModeltoDQP FloatArray 5008 FALSE
INIdentity Float 1 TRUE Identity number
InScalar1 Float 1 FALSE w_obj
InArray1 FloatArray 200 FALSE y_est
InArray2 FloatArray 200 FALSE y_soft_L_active
InArray3 FloatArray 200 FALSE y_soft_H_active
InArray3a FloatArray 200 FALSE y_L_ss
InArray3b FloatArray 200 FALSE y_H_ss
InArray4 FloatArray 200 FALSE W_y_L
InArray5 FloatArray 200 FALSE W_y_H
InArray6 FloatArray 200 FALSE alpha_y
InArray7 FloatArray 200 FALSE beta_y
InArray8 FloatArray 200 FALSE y_obj
InArray9 FloatArray 200 FALSE y_Opt_Err_Tol
InArray10 FloatArray 100 FALSE u_L_ss
InArray11 FloatArray 100 FALSE u_H_ss
InArray12 FloatArray 100 FALSE u_soft_L
InArray13 FloatArray 100 FALSE u_soft_H
InArray14 FloatArray 100 FALSE u_weight
InArray15 FloatArray 100 FALSE alpha_u
InArray16 FloatArray 100 FALSE beta_u
InArray17 FloatArray 100 FALSE u_obj
InArray18 FloatArray 100 FALSE u_solve
which set of RMPCT predictions is newest (1 or
InScalar2 Float 1 FALSE 2)
InArray19 FloatArray 200 FALSE y_bar1 - CV prediction (set 1)
InArray20 FloatArray 100 FALSE u1 - MV value (set 1)
InArray21 FloatArray 100 FALSE u_DV1 - DV value (set 1)

Honeywell
InArray22 FloatArray 200 FALSE y_bar2 - CV prediction (set 2)

InArray23 FloatArray 100 FALSE u2 - MV value (set 2)
InArray24 FloatArray 100 FALSE u_DV2 - DV value (set 2)
InArray25 FloatArray 100 FALSE CV spares
InputFromRMPCTVersion Float 1 FALSE Version of Output to RMPCT interface CDS
RMPCTVersiontoDQP Float 1 FALSE RMPCT engine version
RMPCTUseBDVUFP Float 1 FALSE RMPCT flag to use BDV unforced predictions
WholeInputtoDQP FloatArray 4706 FALSE
OutScalar1 Float 1 TRUE Identity number MUST be '-12'
Connect type: 1 = coop, 2 = direct, 3 = user
OutScalar2 Float 1 TRUE defined
OutScalar3 Float 1 TRUE Index of RMPCT application in DQP
1 = optimizing, 0 = not enough degrees of
OutScalar4 Float 1 TRUE freedom
OutScalar5 Float 1 TRUE T_dqp - design execution frequency
OutScalar6 Float 1 TRUE Optimizer speed value pushed to RMPCT
OutArray1 FloatArray 200 TRUE CV_wound_up (1 -.GT. CV is wound up)
OutArray2 FloatArray 100 TRUE u_soft_L_active (MV act low soft lim)
OutArray3 FloatArray 100 TRUE u_soft_H_active (MV act high soft lim)

Honeywell
OutScalar7 Float 1 TRUE indicates which set of dqp values is newest (1 or

2)
OutArray4 FloatArray 200 TRUE y_dqp1 - CV solution (set 1)
OutArray5 FloatArray 100 TRUE u_dqp1 - MV solution (set 1)
OutArray6 FloatArray 200 TRUE y_dqp2 - CV solution (set 2)
OutArray7 FloatArray 100 TRUE u_dqp2 - MV solution (set 2)
OutArray8 FloatArray 30 TRUE bdv_index
OutArray9 FloatArray 30 TRUE bdv_num_blks
OutArray10 FloatArray 330 TRUE bdv_blk
OutScalar8 Float 1 TRUE last_written_bdv_UFP (not an array)
OutArray11 FloatArray 330 TRUE bdv_UFP1
OutArray12 FloatArray 330 TRUE bdv_UFP2
OutArray13 FloatArray 30 TRUE bdv_dmean (mean deadtime)
OutputToRMPCTVersion Float 1 TRUE Version of Input from RMPCT interface CDS
DQPVersion Float 1 TRUE DQP engine version
WholeOutputToRMPCT FloatArray 2991 TRUE

Honeywell
Profit Controller CV Parameters
XfrmActiveLowLimit Float 1 FALSE CV Low Limit (Active) (Transformed)

XfrmActiveHighLimit Float 1 FALSE CV High Limit (Active) (Transformed)
XfrmLowLimitRampRate Float 1 TRUE CV low limit ramp rate change (Transformed)
XfrmHighLimitRampRate Float 1 TRUE CV high limit ramp rate change (Transformed)
LowLimitErrorWeight Float 1 TRUE CV low limit error weight
HighLimitErrorWeight Float 1 TRUE CV high limit error weight
QuadraticCoeff Float 1 TRUE Economic objective quadratic coefficient
LinearCoeff Float 1 TRUE Economic objective linear coefficient
XfrmDesiredValue Float 1 TRUE Economic objective desired value (Transformed)
Perfratio Float 1 TRUE Performance ratio - feedback
BalanceFactor Float 1 TRUE Balance Factor for integrating CVs .GT.0
ClosedLoopRespTime Float 1 TRUE Specified by users for integrators
FFtoFBPerfRatio Float 1 TRUE FF/FB performance ratio - for feedforward
CVCompensationRatio Float 1 TRUE CV compensation tuning, default = 1.0
NumberofBlocks Float 1 TRUE Entered number of CV block intervals
MinimumFunnel Float 1 TRUE Min funnel opening from y_UFP[0] or opposite
limit, not in graphics.
XfrmDeltaSoftLowLimit Float 1 TRUE Entered soft limit as a delta from y_L
(Transformed)

143
Honeywell
XfrmDeltaSoftHighLimit Float 1 TRUE Entered soft limit as a delta from y_H

(Transformed)
StateEstimation Float 1 TRUE 1: on, -1: off, 0: y_type, 2: on (manual)
XfrmErrorTolerance Float 1 TRUE Error tol at SS to stop optimizer (Transformed)
PVTrack Float 1 TRUE Non-LCN use only, 1: limit tracks val, 0: it doesn't
track
QuadraticCoeffDQP Float 1 TRUE Economic objective quadratic coefficient used by
DQP
LinearCoeffDQP Float 1 TRUE Economic objective linear coefficient used by
DQP
DesiredValueDQP Float 1 TRUE Economic objective desired value used by DQP
QuadraticCoeffcoop Float 1 TRUE Economic objective quadratic coefficient
cooperative
LinearCoeffcoop Float 1 TRUE Economic objective linear coefficient cooperative
DesiredValuecoop Float 1 TRUE Economic objective desired value cooperative
FunnelType Float 1 TRUE 0: standard funnel, 1: narrow opening, 2: use
decouple ratio
DecoupleRatio Float 1 TRUE 0: complete CV decoupling, 1: no CV decoupling
XfrmActiveValue Float 1 FALSE Active source value (Transformed)
XfrmFutureValue Float 1 FALSE Predicted value at 4 tau, see mc_control
(Transformed)
UnbiasedModelPV Float 1 FALSE CV current predicted value
XfrmPredictedValue Float 1 FALSE CV current best estimate (Transformed)
Modeltype Float 1 FALSE 0:stable, 1:integrator, LCN GUI uses it, 0.5:stable
except some integrator DVs, 2:double int, 3:
unstable.
XfrmPredictedSSValue Float 1 FALSE CV at steady-state, no moves, Pool?
(Transformed)
XfrmSSValue Float 1 FALSE Predicted optimal value, see mc_optss
(Transformed)
BadCount Float 1 FALSE Count-down of y_badok
Status Float 1 FALSE CV display status, 1: good, 2: predicted, 3:
dropped, 4: critical and bad, 5: init, .GT.10: init
(first interval)
XfrmActiveDeltaLowSoftLimit Float 1 FALSE Active soft limit as a delta from y_L (Transformed)
XfrmActiveDeltaHigh Float 1 FALSE Active soft limit as a delta from y_H
SoftLimit (Transformed)
LastGood Float 1 FALSE Last good y value
ScalingFactor Float 1 FALSE CV scaling value

Honeywell
WindupStatus Float 1 FALSE wind-up status of CV, set in mc_optss

CVCompConfig Float 1 TRUE 1=CV compensation is configured; 0=not
BiasFilterConst Float 1 TRUE Bias correction filter factor, calculated in
mc_update.
FilteredBias Float 1 TRUE Filtered y-bias for bias updating.
FilteredRamp Float 1 TRUE Filtered y-ramp difference for opt-state-est.
StateEstFilterConst Float 1 TRUE Filter constant for state estimator, calculated in
mc_update.
XfrmDQPValue Float 1 FALSE Solution from DQP, if DQP is attached and ON
(Transformed)
AppIndex Float 1 FALSE Index of this app in DQP, used in graphics
CVIndex Float 1 FALSE Index of this CV in this app, used in DQP
graphics
DQPWindUpStatus Float 1 FALSE Indicates whether CV is wound-up in DQP
CVInitMode Float 1 FALSE CV initialization mode
InferredValue Float 1 FALSE CV inferred value used in RMPCT graphics
BalanceTarget Float 1 FALSE Position in intervals where steady state value is
computed
NumDataPoints Float 1 FALSE Actual # of blocking intervals. For plotting.
Intervals FloatArray 21 FALSE CV blocking values
XfrmControlPrediction FloatArray 21 FALSE Projected CV values (Transformed)
XfrmUnforcedPrediction FloatArray 21 FALSE Unforced prediction (Transformed)
ModelIndex FloatArray 200 FALSE Model Index Information
XfrmLowLimit Float 1 TRUE Entered CV low limit (Transformed)
XfrmHighLimit Float 1 TRUE Entered CV high limit (Transformed)

145
Honeywell
EngineeringLowLimit Float 1 TRUE Entered Engineering CV low limit

EngineeringHighLimit Float 1 TRUE Entered Engineering CV high limit
ShadowPrice Float 1 FALSE Shadow/Error Price of SS CV constraint
Constrainttype Float 1 FALSE 0: free, +/-1: fixed hi/lo (hard), +/-2: fixed hi/lo
(soft), 3: setpoint
HoldIntegrator Float 1 TRUE 0:normal CV error tradeoffs, 1:does not share in
CV error
BadReadsAllowed Float 1 TRUE Number of bad reads allowed
CVCritical Float 1 TRUE !0: CV is critical, 0: non-critical
UpdateFrequency Float 1 TRUE 0: CV update freq GT= control freq, !=0: CV
update freq LT control frequency.
NewValueFlag Float 1 TRUE 1: New value available for 'asynchronous' data
DistCVSimValue Float 1 TRUE Output disturbance value (CV) for simulation. For
DSS simulation only.
BiasCVSimValue Float 1 TRUE Bias or reference value (CV) for simulation. For
DSS simulation only.
NoiseVarCVSimValue Float 1 TRUE Noise Variance (CV) for simulation. For DSS
simulation only.
ControlThisCV Float 1 TRUE Control this CV value, 0: control it, 1: DO NOT
control it.
XfrmReadValue Float 1 TRUE Read value (PV) (Transformed)
LinearizationType Float 1 TRUE Linearization algorithm type (future)
CVProcessLowLimit Float 1 TRUE CV process low limit
CVProcessHighLimit Float 1 TRUE CV process high limit
ControlPrediction FloatArray 21 FALSE Projected CV values (Real World)
UnforcedPrediction FloatArray 21 FALSE Unforced prediction (Real World)
LowLimit Float 1 TRUE Entered CV low limit (Real World)
HighLimit Float 1 TRUE Entered CV high limit (Real World)
ReadValue Float 1 TRUE Read value (PV) (Real World)
ActiveValue Float 1 TRUE Active source value (Real World)
FutureValue Float 1 FALSE Predicted value at 4 tau, see mc_control (Real
World)
PredictedValue Float 1 FALSE CV current best estimate (Real World)
PredictedSSValue Float 1 FALSE CV at steady state, no moves, Pool? (Real World)
SSValue Float 1 FALSE Predicted optimal value, see mc_optss (Real
World)
ActiveDeltaLowSoftLimit Float 1 FALSE Active soft limit as a delta from y_L (Real World)

Honeywell
ActiveDeltaHighSoftLimit Float 1 FALSE Active soft limit as a delta from y_H (Real World)
DQPValue Float 1 FALSE Solution from DQP, if DQP is attached and ON
(Real World)
ActiveLowLimit Float 1 FALSE CV Low Limit (Active) (Real World)
ActiveHighLimit Float 1 FALSE CV High Limit (Active) (Real World)
LowLimitRampRate Float 1 TRUE CV low limit ramp rate change (Real World)
HighLimitRampRate Float 1 TRUE CV high limit ramp rate change (Real World)
DesiredValue Float 1 TRUE Economic objective desired value (Real World)
DeltaSoftLowLimit Float 1 TRUE Entered soft limit as a delta from y_L (Real
World)
DeltaSoftHighLimit Float 1 TRUE Entered soft limit as a delta from y_H (Real
World)
ErrorTolerance Float 1 TRUE Error tolerance at SS to stop optimizer (Real
World)
PVValCnfg Float 1 TRUE Flag indicating whether PV Validation is
configured for CV (0=not configured,
1=configured)
PVValReset Float 1 TRUE Flag to reset PV Validation (0 = don't reset,
1=reset)
DisplayedCVStatus FloatArray 2 FALSE Enumerated Status/Color for CV Summary
Display
DisplayedCVValue FloatArray 2 TRUE Value/Color for CV Summary Display
DisplayedCVFutureValue FloatArray 2 FALSE Value/Color for CV Summary Display
DisplayedCVSSValue FloatArray 2 FALSE Value/Color for CV Summary Display
DisplayedCVLowLimit FloatArray 3 TRUE Value/Color/Ramp arrow for CV Summary
Display
DisplayedCVHighLimit FloatArray 3 TRUE Value/Color/Ramp arrow for CV Summary
Display
DisplayedCVSetpoint FloatArray 3 TRUE Value/Color/Ramp arrow for CV Summary
Display
SITRANSelector Float 1 TRUE Selects the trend line displayed in the SITRAN
display
CVVariableDescription String 0 TRUE CV Variable Description
CVGainMapTime String 0 TRUE the date and time that its gain was updated
WholeCVRecord FloatArray 404 FALSE Use to Read Whole CV Record

147
Honeywell
ActiveLowLimit Float 1 FALSE MV low limit

ActiveHighLimit Float 1 FALSE MV high limit
ActiveMaxMoveDown Float 1 FALSE MV low change limit
ActiveMaxMoveUp Float 1 FALSE MV high change limit
LowLimitRampRate Float 1 TRUE MV low limit ramp rate change
HighLimitRampRate Float 1 TRUE MV high limit ramp rate change
QuadraticCoeff Float 1 TRUE Economic objective quadratic coefficient
LinearCoeff Float 1 TRUE Economic objective linear coefficient
DesiredValue Float 1 TRUE Economic objective desired value
Weight Float 1 TRUE MV weight, default must be 1.0
NumberofBlocks Float 1 TRUE No. of blocking intervals override
PBAntiWindupRatio Float 1 TRUE 0-1, predict back tuning parameter
DeltaSoftLowLimit Float 1 TRUE Soft limit as delta from u_L
DeltaSoftHighLimit Float 1 TRUE Soft limit as delta from u_H
Non-LCN use only, 1:limit tracks value, 0: no
PVTrack Float 1 TRUE tracking
Economic objective quadratic coefficient used by
QuadraticCoeffDQP Float 1 TRUE DQP
Economic objective linear coefficient used by
LinearCoeffDQP Float 1 TRUE DQP
DesiredValueDQP Float 1 TRUE Economic objective desired value used by DQP
Economic objective quadratic coefficient
QuadraticCoeffcoop Float 1 TRUE cooperative
LinearCoeffcoop Float 1 TRUE Economic objective linear coefficient cooperative
DesiredValuecoop Float 1 TRUE Economic objective desired value cooperative
Output from controller (SP or OP), WARM/ON
SentValue Float 1 FALSE update
ActiveValue Float 1 FALSE Current active value
FutureValue Float 1 FALSE Predicted value at 4 tau
MV status (display), 1: on, 2: wound up hi, 3:
Status Float 1 FALSE would up lo, 4: ffwd, 5: service, 6: init
SSValue Float 1 FALSE Predicted optimal value
PreviousValue Float 1 FALSE MV at previous interval

Honeywell
Cascade status, 0: off, 1: init, 2: on. Use for mode

CascadeStatus Float 1 TRUE switching at DSS.
InitIntervals Float 1 FALSE No. of intervals in init space
LastStatus Float 1 FALSE u_solve from previous interval
MV move to be implemented, u_0 - u, WARM/ON
CurrentMove Float 1 FALSE update
ActiveDeltaLowSoftLimit Float 1 FALSE Active soft limit as a delta from u_L
ActiveDeltaHighSoftLimit Float 1 FALSE Active soft limit as a delta from u_H
ScalingFactor Float 1 FALSE MV scaling factor
ActiveProcessValue Float 1 FALSE PV of downstream PID
PredBackConfig Float 1 TRUE 1: predict back configured, 0: not
PredictedPV Float 1 FALSE Predicted value of PV of downstream controller
ShadowPrice Float 1 FALSE Shadow/Error Price of SS MV constraint
0: free, +/-1: fixed hi/lo (hard), +/-2: fixed hi/lo
ConstraintType Float 1 FALSE (soft)
DQPValue Float 1 FALSE Solution from DQP, if DQP is attached and ON
Index of this MV in this app, used in DQP
MVIndex Float 1 FALSE graphics

149
Honeywell
Actual number of blocking intervals + 1, for

NumDataPoints Float 1 FALSE plotting.
Intervals FloatArray 21 FALSE MV blocking values
ControlPrediction FloatArray 21 FALSE Predicted future MV values
LowLimit Float 1 TRUE Entered MV low limit
HighLimit Float 1 TRUE Entered MV high limit
EngineeringLowLimit Float 1 TRUE Entered Engineering MV low limit
EngineeringHighLimit Float 1 TRUE Entered Engineering MV high limit
MVCritical Float 1 TRUE MV is critical=0.0; non-critical!=0.0
1=drop from model prediction calculations;
MVManAction Float 1 TRUE 0=FFWD
MaxMoveDown Float 1 TRUE MV max move Down
MaxMoveUp Float 1 TRUE MV max move up
Start Value (MV) for simulation. DSS simulation
StartMVSimValue Float 1 TRUE only.
Bias value for process input (MV) for simulation.
BiasMVSimValue Float 1 TRUE Dss simulation only.
!=0: use this MV for control, 0: do not use this MV
UseThisMV Float 1 TRUE for control.
ModeChanged Float 1 FALSE This MV mode has changed.
ProcessHighLimit Float 1 TRUE Process setpoint high limit
ProcessLowLimit Float 1 TRUE Process setpoint low limit
ReadValue Float 1 TRUE The SP/OP value read into the controller
The pv value read into the controller. Used for
predict-back option, but must be supplied even if
ReadProcessValue Float 1 TRUE option not used (can use u_read source).
Windup status for this MV, 1: normal, 2: hi, 3: lo,
WindupStatus Float 1 TRUE 4: hilo.
SentValueIfON Float 1 FALSE Output from controller if mode is ON
CurrentMoveIfON Float 1 FALSE MV move if mode is ON
Selects the trend line displayed in the SITRAN
SITRANSelector Float 1 TRUE display
-1: no resolution calc, 0: auto resolution, .GT. 0:
Resolution Float 1 TRUE entered resolution
Estimated resolution if auto, else max output
CalculatedResolution Float 1 FALSE mismatch
ResolutionMismatch Float 1 FALSE Output mismatch at this interval

Honeywell
Accumulated residual output less than DCS

ResolutionResidual Float 1 FALSE resolution
DCSSP FloatArray 5 TRUE Cascaded loop's SPs
DCSPV FloatArray 5 TRUE Cascaded loop's PVs
DCSOP FloatArray 5 TRUE Cascaded loop's OPs
DCSMode FloatArray 5 TRUE Cascaded loop's modes
DCSWindupStatus FloatArray 5 TRUE Cascaded loop's windup statuses
DCSSPHighLimit FloatArray 5 TRUE Cascaded loop's SP high limits
DCSSPLowLimit FloatArray 5 TRUE Cascaded loop's SP low limits
DCSOPHighLimit FloatArray 5 TRUE Cascaded loop's OP high limits
DCSOPLowLimit FloatArray 5 TRUE Cascaded loop's OP low limits
MVVariableDescription String 0 TRUE MV Variable Description
WholeMVRecord FloatArray 174 FALSE Use read whole MV record
Profit Controller DV Parameters
PredBackRatio Float 1 TRUE 0-1, predict back tuning parameter

ScalingFactor Float 1 FALSE Scaling factor
ActiveValue Float 1 FALSE ACTIVE actual value
PreviousValue Float 1 FALSE DV at previous interval
ActiveProcessValue Float 1 FALSE PV of downstream PID
PredBackConfig Float 1 FALSE 1.0 = predict back configured, 0.0=not
PredictedPV Float 1 FALSE Predicted value of PV of downstream controller

151
Honeywell
DVHasPrediction Float 1 FALSE DV has prediction

Status Float 1 FALSE DV status (solver)
Index of this DV in this app, used in DQP
DVIndex Float 1 FALSE graphics
Bridge Model Status 0: not ready, 1:good,
BridgeModelStatus Float 1 FALSE 2:predict, 3:drop, 4:critical, 5:no prediction
BridgeDVTuning Float 1 FALSE
NumberofPredictedValues Float 1 FALSE # of future predicted points + 1, for plotting.
DVBlockingValues FloatArray 21 FALSE DV blocking values
PredictedFutureValues FloatArray 21 FALSE Predicted future DV values
DV Windup Status (Only need w/ Pred-back)
WindupStatus Float 1 TRUE 1.0=NORMAL; 2.0=HI; 3.0=LO
DVIsBad Float 1 TRUE Indicates that DV is BAD
DVCritical Float 1 TRUE DV is critical=0.0; non-critical !=0.0
UseThisDV Float 1 TRUE 1.0 = Use; 0.0 = Drop
Start Value (DV) for simulation. For DSS
StartDVSimValue Float 1 TRUE simulation only.
Bias value for process disturbance (DV) for
BiasDVSimValue Float 1 TRUE simulation. For DSS sim only.
ReadValue Float 1 TRUE The SP/OP value read into the controller
ReadProcessValue Float 1 TRUE The pv value read into the controller
Selects the trend line displayed in the SITRAN
SITRANSelector Float 1 TRUE display
DVVariableDescription String 0 TRUE DV Variable Description
WholeDVRecord FloatArray 79 FALSE use to read the whole DC record
Entry to indicate the last entry in the Datapool
LastEntryofDatapool String 0 TRUE (last HPAR)

Honeywell
A.3 Profit Optimizer Datapool Parameters
HSMiniBrowser.
Profit Optimizer Common Parameters
NumberofRMPCTs Float 1 FALSE user_n_RMPCT

NumberofBridgeOutputs Float 1 FALSE user_n_bout
OptimizerSpeedFactor Float 1 TRUE opt_speed
URVTolerance Float 1 TRUE URV_tol
ReadModelFlag Float 1 TRUE read_YM_flag
OptimizerSpeedCoordination Float 1 TRUE
ReadSpecFlag Float 1 TRUE read_YS_flag
MaxConsecBadBinTurnOff Float 1 TRUE
MaxConsecBadBin
Reinitialize Float 1 TRUE
SkipYMCheck Float 1 TRUE 0: force ym_consistency_check, else skip
multiplier for optimization speed when
CoordinatingSpeedupFactor Float 1 TRUE coordinating
DQPState Float 1 FALSE DQP State
Engineversion Float 1 FALSE Program Version
ModelFileBuilderVersion Float 1 FALSE YM File Version
NumberofCVsplusdividers Float 1 FALSE Display # of CVs
NumberofMVsplusdividers Float 1 FALSE Display # of MVs
NumberofDVsplusdividers Float 1 FALSE Display # of DVs

153
Honeywell
SSDeflatedSingularValue Float 1 FALSE Maximum Defaulted SS Value

SSError Float 1 FALSE Steady State Error
SSObjectiveValue Float 1 FALSE Steady State Objective
CurrentObjectiveValue Float 1 FALSE Current Objective
NumberofDVBridgeInputs Float 1 FALSE ext_n_DV_bin
NumberofBridgeInputs Float 1 FALSE ext_n_bin
NumberofCombined
Constraints Float 1 FALSE ext_comb
DQP ready flag (mostly for CL/display
ModelReadinessFlag Float 1 FALSE coordination)
SpecFileBuilderVersion Float 1 FALSE YS File Version
DesignExecPeriod Float 1 FALSE Available
ModelReadRequiredFlag Float 1 FALSE '
OptimizationFlag Float 1 FALSE DQP optimization flag
DQPVersion Float 1 FALSE DQP version number
RequestedState Float 1 TRUE DQP On/Off/Warm flag
NowAlarm FloatArray 50 FALSE DQP now_alarm
PrevAlarm FloatArray 50 FALSE DQP prev_alarm
ExecutionInterval Float 1 FALSE Actual execution interval, minutes.
ExecutionOffset Float 1 FALSE Execution offset, minutes.
Max consecutive intervals allowed for bad input
MaxNotAllowedBad Float 1 TRUE for not-allowed-bad parameter
Number of consecutive intervals with bad input
NumNotAllowedBad Float 1 FALSE for not-allowed-bad parameter
Overruns Float 1 FALSE Overruns for this process
Simulation reset, 1: reset. Only for DSS
SimReset Float 1 TRUE simulation.
allows other apps to schedule intervals by writing
RunIntervalFlag Float 1 TRUE non-zero to this parameter
ControlRestart Float 1 TRUE Reset control and prediction, !=0: reset.
DoSolverCalcs Float 1 TRUE

Honeywell
KeepRunning Float 1 TRUE Set to 0 to terminate controller program

Each entry controls a Pascal debug flag for
DebugFlags FloatArray 48 TRUE debug messages - 1.0 to turn on
1 means the 10 most recent executions, 0 means
NumDebugFiles Float 1 TRUE all executions
MaxOverruns Float 1 TRUE Max Overruns before self shutdown
(Simulation Only) if 0 - pause, otherwise divide
SpeedUpFactor Float 1 TRUE execution interval
IntervalCounter Float 1 FALSE Incremented after each interval completes
DisplayedStatus Float 1 FALSE Enumeration indicating the status string to display
NumberFunctions Float 1 TRUE Total number of Toolkit functions configured
Number of Toolkit functions returning bad status
NumberFunctionsBad Float 1 TRUE for current interval
GMUpdate Float 1 TRUE GM_Update
GMErrorAction Float 1 TRUE GM_Error_Action
GMBMGain FloatArray 2000 TRUE GMBM_Gain
GMBIAppIndex FloatArray 2000 TRUE GMBI_AppIndex
GMBIMVDVIndex FloatArray 2000 TRUE GMBI_MVDVIndex
GMBOAppIndex FloatArray 2000 TRUE GMBO_AppIndex
GMBODVIndex FloatArray 2000 TRUE GMBO_DVIndex
GMBMStatus FloatArray 2000 TRUE GMBM_Status
GMCCGain FloatArray 200 TRUE GMCC_Gain
GMCCIndex FloatArray 200 TRUE GMCC_Index
GMCCAppIndex FloatArray 200 TRUE GMCC_AppIndex
GMCCMVDVIndex FloatArray 200 TRUE GMCC_MVDVIndex
GMCCStatus FloatArray 200 TRUE GMCC_Status
LastModelFileName String 0 FALSE Last Model File actually read

155
Honeywell
LastSpecFileName String 0 FALSE Last Spec File Actually read

OptimizerName String 0 FALSE DQP instance name
OptimizerDescription String 0 TRUE User specified optimizer description
ModelFileName String 0 TRUE Model File Name
SpecFileName String 0 TRUE Specification File Name
ConfigFileName String 0 TRUE Configuration File Name
Process Model File Name. Only for DSS
ProcessModelFileName String 0 TRUE simulation.
CheckPointName String 0 TRUE Check Point Name
LastCheckpointFileName String 0 FALSE Name of last checkpoint file read
LastCheckpointReadTime String 0 FALSE Time last checkpoint read in
LastCheckpointWriteTime String 0 FALSE Time last checkpoint written out
LastModelReadTime String 0 FALSE Time last model file was read in
'ACTIVE' - control calcs running, 'INACTIVE' - not
ApplicationStatus String 0 TRUE running
Status Float 1 FALSE RMPCT application state

Critical Float 1 TRUE RMPCT critical flag: 1 = crit, 0 = non-crit
RMPCT connect type: 1 = coop, 2 = direct, 3 =
ConnectionType Float 1 TRUE user-defined
LastModelUsedID Float 1 FALSE RMPCT last_model_id
AliveFlag Float 1 TRUE 1.0 = Alive (active); 0.0 = Dead (inactive)
Display state, -2: shed, 0: off, 1: on, 2: init, 11:
ControllerMode Float 1 TRUE warm
OddModelID Float 1 TRUE ID of odd model in RMPCT (read up always)
EvenModelID Float 1 TRUE ID of even model in RMPCT (read up always)
ControllerDescription String 0 TRUE RMPCT Controller Names
OddDQPModelID Float 1 TRUE model_id (odd model counter)
OddScalar1 Float 1 TRUE n_cv (number of CVs in this app)
OddScalar2 Float 1 TRUE n_mv (number of MVs in this app)
OddScalar3 Float 1 TRUE n_dv (number of DVs in this app)

Honeywell

OddScalar4 Float 1 TRUE app)
OddScalar5 Float 1 TRUE design execution frequency
OddArray1 FloatArray 2000 TRUE packed IJp - index to non-null models
OddArray2 FloatArray 2000 TRUE packed unweighted SS gains
OddArray3 FloatArray 200 TRUE Dr (row/CV scaling)
OddArray4 FloatArray 100 TRUE Dc (column/MV scaling)
OddModelIFVersion Float 1 TRUE Version of RMPCT Model interface CDS
EvenDQPModelID Float 1 TRUE model_id (odd model counter)
EvenScalar1 Float 1 TRUE n_cv (number of CVs in this app)
EvenScalar2 Float 1 TRUE n_mv (number of MVs in this app)
EvenScalar3 Float 1 TRUE n_dv (number of DVs in this app)
EvenScalar4 Float 1 TRUE app)
EvenScalar5 Float 1 TRUE design execution frequency
EvenArray1 FloatArray 2000 TRUE packed IJp - index to non-null models
EvenArray2 FloatArray 2000 TRUE packed unweighted SS gains
EvenArray3 FloatArray 200 TRUE Dr (row/CV scaling)
EvenArray4 FloatArray 100 TRUE Dc (column/MV scaling)
EvenModelIFVersion Float 1 TRUE Version of RMPCT Model interface CDS
InScalar1 Float 1 TRUE w_obj
InArray1 FloatArray 200 TRUE y_est
InArray2 FloatArray 200 TRUE y_soft_L_active
InArray3 FloatArray 200 TRUE y_soft_H_active
InArray3a FloatArray 200 TRUE y_L_ss
InArray3b FloatArray 200 TRUE y_H_ss
InArray4 FloatArray 200 TRUE W_y_L
InArray5 FloatArray 200 TRUE W_y_H
InArray6 FloatArray 200 TRUE alpha_y
InArray7 FloatArray 200 TRUE beta_y
InArray8 FloatArray 200 TRUE y_obj
InArray9 FloatArray 200 TRUE y_Opt_Err_Tol
InArray10 FloatArray 100 TRUE u_L_ss

157
Honeywell
InArray11 FloatArray 100 TRUE u_H_ss

InArray12 FloatArray 100 TRUE u_soft_L
InArray13 FloatArray 100 TRUE u_soft_H
InArray14 FloatArray 100 TRUE u_weight
InArray15 FloatArray 100 TRUE alpha_u
InArray16 FloatArray 100 TRUE beta_u
InArray17 FloatArray 100 TRUE u_obj
InArray18 FloatArray 100 TRUE u_solve
which set of RMPCT predictions is newest (1 or
InScalar2 Float 1 TRUE 2)
InArray19 FloatArray 200 TRUE y_bar1 - CV prediction (set 1)
InArray20 FloatArray 100 TRUE u1 - MV value (set 1)
InArray21 FloatArray 100 TRUE u_DV1 - DV value (set 1)
InArray22 FloatArray 200 TRUE y_bar2 - CV prediction (set 2)
InArray23 FloatArray 100 TRUE u2 - MV value (set 2)
InArray24 FloatArray 100 TRUE u_DV2 - DV value (set 2)
InArray25 FloatArray 100 TRUE RMPCT DV status
InputFromRMPCTVersion Float 1 TRUE Version of Input From RMPCT interface CDS
RMPCTVersion Float 1 TRUE Version of RMPCT engine
RMPCTUseBDVUFP Float 1 TRUE RMPCT flag to use BDV unforced predictions
OutScalar1 Float 1 FALSE Identity number MUST be '-12'
Connect type: 1 = coop, 2 = direct, 3 = user
OutScalar2 Float 1 FALSE defined
OutScalar3 Float 1 FALSE Index of RMPCT application in DQP
1 = optimizing, 0 = not enough degrees of
OutScalar4 Float 1 FALSE freedom
OutScalar5 Float 1 FALSE T_dqp - design execution frequency
OutScalar6 Float 1 FALSE Optimizer speed value pushed to RMPCT
OutArray1 FloatArray 200 FALSE CV_wound_up (1 -.GT. CV is wound up)
OutArray2 FloatArray 100 FALSE u_soft_L_active (MV act low soft lim)
OutArray3 FloatArray 100 FALSE u_soft_H_active (MV act high soft lim)
indicates which set of dqp values is newest (1 or
OutScalar7 Float 1 FALSE 2)

Honeywell
OutArray4 FloatArray 200 FALSE y_dqp1 - CV solution (set 1)

OutArray5 FloatArray 100 FALSE u_dqp1 - MV solution (set 1)
OutArray6 FloatArray 200 FALSE y_dqp2 - CV solution (set 2)
OutArray7 FloatArray 100 FALSE u_dqp2 - MV solution (set 2)
OutArray8 FloatArray 30 FALSE bdv_index
OutArray9 FloatArray 30 FALSE bdv_num_blks
OutArray10 FloatArray 330 FALSE bdv_blk
OutScalar8 Float 1 FALSE last_written_bdv_UFP (not an array)
OutArray11 FloatArray 330 FALSE bdv_UFP1
OutArray12 FloatArray 330 FALSE bdv_UFP2
OutArray13 FloatArray 30 FALSE bdv_dmean (mean deadtime)
OutputToRMPCTVersion Float 1 FALSE Version of Output to RMPCT interface CDS
DQPVersion Float 1 FALSE Version of RMPCT interface CDS
Profit Optimizer Combined Constraint Parameters
LowLimit Float 1 TRUE Comb Const comb_L

HighLimit Float 1 TRUE Comb Const comb_H
LowLimitErrorWeight Float 1 TRUE Comb Const W_comb_L
HighLimitErrorWeight Float 1 TRUE Comb Const W_comb_H
QuadraticCoeff Float 1 TRUE Comb Const alpha_comb
LinearCoeff Float 1 TRUE Comb Const beta_comb
DesiredValue Float 1 TRUE Comb Const comb_obj
PredictedValue Float 1 FALSE Comb Const comb_est
Comb Const comb_val (potential future use for
Value Float 1 TRUE measurement)
SSValue Float 1 FALSE Comb Const comb_opt
Status Float 1 FALSE Comb Const comb_status
ScalingFactor Float 1 FALSE Comb Const comb_DR
ErrorTolerance Float 1 TRUE Comb Const comb_Opt_Err_Tol
SoftDeltaLowLimit Float 1 TRUE Comb Const comb_soft_L
SoftDeltaHighLimit Float 1 TRUE Comb Const comb_soft_H

159
Honeywell
SoftActiveLowLimit Float 1 TRUE Comb Const comb_soft_L_active

SoftActiveHighLimit Float 1 TRUE Comb Const comb_soft_H_active
UnbiasedValue Float 1 FALSE Unbiased constraint value
Bias Float 1 TRUE Combined constraint bias value
Description String 0 TRUE Comb Const Description

Honeywell
Profit Optimizer Bridge Output Parameters
ForceBadFlag Float 1 TRUE Use this DV (DV_force_bad)

Critical Float 1 TRUE Critical DV (DV_critical)
MaxConsecutiveBad Float 1 TRUE Max Bad value Allowed
RMPCTAppIndex Float 1 FALSE DV_app
RMPCTVarIndex Float 1 FALSE DV_real_idx
ReadValue Float 1 TRUE DV
UnbiasedModelPV Float 1 FALSE DV_hat
PredictedValue Float 1 FALSE DV_est
LastGood Float 1 FALSE DV_last
FilteredBias Float 1 TRUE DV_Filt_bias
FilterConst Float 1 TRUE DV_Filt_Const
PredictedSSValue Float 1 TRUE DV_bar
SSValue Float 1 FALSE DV_ss
Status Float 1 FALSE
NumDataPoints Float 1 FALSE (DV_num_blks)
Intervals FloatArray 21 FALSE Indicates (i-1)th DV Block
UnforcedPrediction FloatArray 21 FALSE Projected DV at (i-1)th Block
DistSimValue Float 1 TRUE Profit Simulation Load Value
BiasSimValue Float 1 TRUE Profit Simulation Bias Value
NoiseVarSimValue Float 1 TRUE Profit Simulation Noise Variance
Description String 0 TRUE Bridge Output Description
Profit Optimizer DV Bridge Input Parameters
ActiveValue Float 1 FALSE DV Bridged Input Value used by solver
ReadValue Float 1 TRUE DV Bridged Input Value read from DSS
UsethisDV Float 1 TRUE 1.0 = Use; 0.0 = Drop
StartSimValue Float 1 TRUE Profit Simulation DV Bin Start Value
BiasSimValue Float 1 TRUE Profit Simulation DV Bin Bias Value

161
Honeywell
Profit Optimizer MV Bridge Inputs
ActiveValue Float 1 FALSE MV Bridged Input Value used by solver
ReadValue Float 1 TRUE MV Bridged Input Value read from DSS
Status Float 1 TRUE MV status - see RMPCT for values
MVManAction Float 1 TRUE 1=Drop; 0=FFWD
StartSimValue Float 1 TRUE Profit Simulation MV Bin Start Value
BiasSimValue Float 1 TRUE Profit Simulation MV Bin Bias Value

Honeywell
A.4 Profit Toolkit Datapool Parameters
HSMiniBrowser.
Profit Toolkit Common Datapool Parameters
KeepRunning Float 1 TRUE Set to 0 to terminate controller program.

Allows other processes to schedule intervals by
RunIntervalFlag Float 1 TRUE setting this to non-zero
DesignExecPeriod Float 1 TRUE Design control execution interval (minutes)
Toolkit application state: 0:off, 1:on, 11:warm,
ToolkitMode Float 1 FALSE ??:inactive.
TurnONOFF Float 1 TRUE Turn application ON or OFF.
ExecutionInterval Float 1 TRUE Actual execution interval, minutes.
ExecutionOffset Float 1 TRUE Execution offset, minutes.
Number of Toolkit functions specified in the
NumberFunctions Float 1 TRUE configuration file
Number of functions that return non-zero
NumberFunctionsBad Float 1 TRUE Ret_Status in current interval
Overruns Float 1 TRUE Overruns for this process
Max. number overruns before controller shuts
MaxOverruns Float 1 TRUE itself off (when self-scheduled)
under simulation divide execution interval by this -
SpeedUpFactor Float 1 TRUE when 0 pause simulation
IntervalCounter Float 1 FALSE increment after each interval is complete
Application is executed under Offline (APCDE)
OfflineSimulation Float 1 TRUE simulation (0:no; 1:yes).
ConfigFileVersion Float 1 TRUE Config File Version number
LastEntryofFloatSection String 0 TRUE Entry to indicate the last entry of float section

163
Honeywell
Profit Toolkit Common Datapool Parameters
ToolkitName String 0 FALSE Toolkit Name

ToolkitDescription String 0 TRUE Toolkit Description
ConfigFileName String 0 FALSE Configuration File Name
CheckPointName String 0 TRUE Check Point File Name
LastCheckpointFileName String 0 FALSE Name of last Checkpoint file read in
LastCheckpointReadTime String 0 FALSE Time of last checkpoint file read
LastCheckpointWriteTime String 0 FALSE Time of last checkpoint file was written

Honeywell
'ACTIVE' - running toolkit calculations,

ApplicationStatus String 0 TRUE 'INACTIVE' not and default
Gain Extraction Dependent Datapool Parameters
Type Float 1 TRUE Dependent Variable Kind: CV=0, CC=1, BO=2

MapAppIndex Float 1 TRUE BO only: Index of RMPCT in DQP for BO DV
MapIndex Float 1 TRUE CV, BO: Index in RMPCT, CC: Index in DQP
Current Float 1 TRUE Current Read Value (for display)
Value calculated by model in response to
Step Float 1 TRUE perturbed INDEPs
Base FloatArray 5 TRUE Set of Step values for gain calculation
CVIndex Float 1 TRUE Index in RMPCT (for display)
CCIndex Float 1 TRUE Index in DQP (for display)
BOIndex Float 1 TRUE Index in DQP (for display)
DVIndex Float 1 TRUE Index of BO DV in RMPCT (for display)
DepVar Description String 0 TRUE Description (for display)
Gain Extraction Independent Datapool Parameters
Type Float 1 TRUE Independent Variable Kind: MV=0, DV=1,

CloneDV=2

165
Honeywell
MapAppIndex Float 1 TRUE Index of RMPCT in DQP

MapIndex Float 1 TRUE MVDV index in RMPCT
PassIndex Float 1 TRUE Perturb Group Number (INDEPs with same value
perturbed on same pass)
Step Float 1 TRUE Value passed to model
StepSize Float 1 TRUE Perturbation step size
DerivType Float 1 TRUE Derivative calculation type: 0=None, 1=Forward,
2=Backward, 3=Central
MVIndex Float 1 TRUE MV index in RMPCT, 0 for DVs. (for display)
DVIndex Float 1 TRUE DV index in RMPCT, 0 for MVs. (for display)
SourceIndep Float 1 TRUE Index of INDEP that is source for a CloneDV
IndepVarDescription String 0 TRUE Description (for display)
Gain Extraction Gains Datapool Parameters
Type Float 1 TRUE Kind: 0=CV Gain, 1=CC Gain, 2=BM Gain
DepVarIndex Float 1 TRUE Index of associated DEP variable
IndepVarIndex Float 1 TRUE Index of associated INDEP variable
Original Float 1 TRUE Original gain in engineering units (future use)
Previous Float 1 TRUE Value of previous validated gain
Current Float 1 TRUE Current calculated, unvalidated gain value
Validated Float 1 TRUE Most recently validated gain value
Validation params: [0]=max, [1]=min,
ValidCoef FloatArray 100 TRUE [2]=clamp/reject, [3]=filter, [4]=ROC
Calculation type: 0=not calculated, 1=calculated,
CalcType Float 1 TRUE 2=provided
ErrStatus Float 1 TRUE Error status: 0=good
MapAppIndex Float 1 TRUE Application index for mapping
MapIndex Float 1 TRUE Index into Gain Mapper custom variable arrays
GainVarDescription String 0 TRUE Description (for display)

Honeywell
Gain Extraction Common Datapool Parameters
NumRmpct Float 1 TRUE Number of RMPCTs in Profit Bridge application

MapAppIndex Float 1 TRUE Index of RMPCT in DQP
MapIndex Float 1 TRUE MVDV index in RMPCT
PassIndex Float 1 TRUE Perturb Group Number (INDEPs with same value
perturbed on same pass)
Step Float 1 TRUE Value passed to model
StepSize Float 1 TRUE Perturbation step size
DerivType Float 1 TRUE Derivative calculation type: 0=None, 1=Forward,
2=Backward, 3=Central
MVIndex Float 1 TRUE MV index in RMPCT, 0 for DVs. (for display)
DVIndex Float 1 TRUE DV index in RMPCT, 0 for MVs. (for display)
SourceIndep Float 1 TRUE Index of INDEP that is source for a CloneDV
IndepVarDescription String 0 TRUE Description (for display)

167
Honeywell
Gain Extraction Gains Datapool Parameters
Type Float 1 TRUE Kind: 0=CV Gain, 1=CC Gain, 2=BM Gain
DepVarIndex Float 1 TRUE Index of associated DEP variable
IndepVarIndex Float 1 TRUE Index of associated INDEP variable
Original Float 1 TRUE Original gain in engineering units (future use)
Previous Float 1 TRUE Value of previous validated gain
Current Float 1 TRUE Current calculated, unvalidated gain value
Validated Float 1 TRUE Most recently validated gain value
Validation params: [0]=max, [1]=min,
ValidCoef FloatArray 100 TRUE [2]=clamp/reject, [3]=filter, [4]=ROC
Calculation type: 0=not calculated, 1=calculated,
CalcType Float 1 TRUE 2=provided
ErrStatus Float 1 TRUE Error status: 0=good
MapAppIndex Float 1 TRUE Application index for mapping
MapIndex Float 1 TRUE Index into Gain Mapper custom variable arrays
GainVarDescription String 0 TRUE Description (for display)

Honeywell

NumCV Float 1 TRUE Number of DEPs that are CVs
NumCC Float 1 TRUE Number of DEPs that are CCs
NumBO Float 1 TRUE Number of DEPs that are BOs
NumMVDV Float 1 TRUE Number of INDEPs (MVs+DVs)
NumCVGain Float 1 TRUE Number of GAIN variables that are for CVs
NumCCGain Float 1 TRUE Number of GAIN variables that are for CCs
NumBOGain Float 1 TRUE Number of GAIN variables that are for BOs
NumPasses Float 1 TRUE The target Pass Index (Perturb Group Number)
Element [k] is the # of INDEPs associated with
NumMVDVPass FloatArray 1000 TRUE Perturb Group k+1 (future)
The # of perturb steps for the derivative type
NumStepsMax Float 1 TRUE requiring the most # of steps
The number of gain validation parameters (5 in
NumValidCoef Float 1 TRUE R200)
GMUpdate FloatArray 1000 TRUE The Gain Mapper Update (Execute) flags
GainExtVarDescription String 0 TRUE Description (for display)

169
Honeywell

NumCV Float 1 TRUE Number of DEPs that are CVs
NumCC Float 1 TRUE Number of DEPs that are CCs
NumBO Float 1 TRUE Number of DEPs that are BOs
NumMVDV Float 1 TRUE Number of INDEPs (MVs+DVs)
NumCVGain Float 1 TRUE Number of GAIN variables that are for CVs
NumCCGain Float 1 TRUE Number of GAIN variables that are for CCs
NumBOGain Float 1 TRUE Number of GAIN variables that are for BOs
NumPasses Float 1 TRUE The target Pass Index (Perturb Group Number)
Element [k] is the # of INDEPs associated with
NumMVDVPass FloatArray 1000 TRUE Perturb Group k+1 (future)
The # of perturb steps for the derivative type
NumStepsMax Float 1 TRUE requiring the most # of steps
The number of gain validation parameters (5 in
NumValidCoef Float 1 TRUE R200)
GMUpdate FloatArray 1000 TRUE The Gain Mapper Update (Execute) flags
GainExtVarDescription String 0 TRUE Description (for display)

Honeywell
Appendix B ProfitSuite Configuration Files
B.1 Configuration File Structure

Over This section describes the layout of the ProfitSuite configuration file.
What is it? The configuration file is a flat ASCII file that defines the connections between a
controller’s variables and their sources or destinations in the interface software for
the particular control system.
There is one configuration file per controller. The file must be available in the
c:\users\HiSpec\config directory when the controller is activated.
Part of the configuration file’s syntax is invariant over all DSSs (interface software
connecting the control system and the controller engine). Part is specific to each
type of DSS and is defined by the implementers of the DSS server. The invariant
part is sufficient to allow detection of errors in the overall file layout, and to verify
that there are no unknown parameters. The syntax is also sufficient to allow a DSS
server to obtain partially parsed information from the configuration file via the
controller’s API.
Syntax Each record in a configuration file is composed of a number of fields separated by
commas. ProfitSuite defines the first two fields and the implementer of the DSS
server defines the remaining fields. Within the first two fields information is treated
as case-insensitive and white space (including tabs) is ignored.
The appearance of // anywhere in a record is treated as the start of a comment and
the rest of the record is ignored during processing of the configuration file.
Header Record The first record in every ProfitSuite configuration file must be a Header record.
The Header record identifies the type of ProfitSuite application that the
configuration applies to:
Header, <application type>, Standard Configuration
Where <application type> is:
RMPCT for Profit Controller
DQP for Profit Optimizer
Or Toolkit for Profit Toolkit.

Honeywell
Appendix B- ProfitSuite Configuration Files
B.1- Configuration File Structure
Dimension Immediately following the header record, Profit Controller and Profit Optimizer
Records require dimension records indicating the number of variables of each applicable
variable type that apply to this configuration. The dimensions listed must match
the design of the application as developed in Profit Design Studio and expressed in
the associated design files: .xm, .xs for Profit Controller; and .ym, .ys for Profit
Optimizer. If the given dimensions do not match the matrix dimensions given in
the associated design files (.xm, .xs, .ym, .ys), the application will fail on startup
and an error message will be listed in the c:\users\hispec\apps\<application>.log
file.
These records look like:
Number of <variable type>s, n
where <variable type>s gives the name of the variable type and n gives the number
of variables of this type to include in this application’s datapool.
Profit Controller applications contain the following variable types:
1 or more CVs, 1 or more MVs, and 0 or more DVs. Profit Controller
configuration files must list three dimension records:
Number of CVs, l
Number of MVs, m
Number of DVs, n
Profit Optimzer applications contain the following variable types:
Number of controllers, l
Number of combined constraints, m
Number of DV bridge inputs, n
Number of MV bridge inputs, o
Number of bridge outputs, p
Profit Controller and Profit Optimizer datapools consist of the specified number of
records of each variable type. Each record of a given variable type contains a
number of parameters as specified in the c:\users\hispec\config\<application
type>.xml file. A formatted view of these record formats may be viewed by
running the \Program Files\Honeywell\HiSpec Solutions\HsMiniBrowser.exe
application and selecting the Help button. Page to the bottom of the page and
select the application type of interest.
Any application may also contain “custom” variables in its datapool. These
variables are defined in the configuration file and have a single parameter. Custom
variable definition is described below.
Profit Toolkit datapools typically consist entirely of custom variables. However,
certain toolkits, typically those associate with Profit Bridge, may contain dimension
records declaring variables of the following variable types:
Number of DEPs, l
Number of INDEPs, m

Honeywell
Number of CVGains, n
Number of GainExt, o
The parameters supported by these variable types may be viewed under the Profit
Toolkit section in the HsMiniBrowser Help display.
Server Record A server record looks like:
Server, server_name, order n[, schedules]
Where:
· server_name is the name of the DSS server that will be used for subsequent
parameter records, until another server record is encountered. A server record
must precede any parameter records.
· n is the order in which the executive will call the server members if there is
more than one server. The range of n is 0–32767. Different servers can be
assigned the same order number if it doesn’t matter in what order they are
called.
· The optional “schedules” field indicates that this server schedules the
controller. (The brackets indicate that the field is optional, and are not actually
entered in the file.) If no server record has the schedules option, the controller
executable will schedule it. It is an error if more than one server record
includes the schedule option.
Examples:
Server, HS_PHD_1_0, order 1, schedules
Server, HS_GANT_1_0, order 1, schedules
Server, DssOPCLink, order 1
A server name must be unique, which is essentially ensured by the scheme used in
the examples. The version number in the examples is the version of the DSS server,
not RMPCT or the DSS.
A server can be either a DSS server or a simulation server. Simulation servers must
be executed before DSS servers, and therefore must have a smaller order number.
Controller A record to configure a general controller parameter looks like:
Parameter
Controller, parameter, DSS Field 1, DSS Field 2...
Record
Example:
Server, AnyDssServerName, order 1
Controller, Optimiz Speed, DU1RMPCT, X(4) // opt_speed
The available controller parameter names and descriptions are listed in Appendix A.

173
Honeywell
CV, MV or DV A record to configure a CV, MV or DV parameter looks like:

Parameter
var_name, par_name, DSS Field 1, DSS Field 2...
Record
Where:
· var_name is the name (CVs, MVs or DVs name) as shown in Profit
Design Studio’s (APCDE) Description Info view.
· par_name is the Datapool name of a parameter that belongs to the variable
var_name. See Appendix A for a complete list.
· DSS Field i is DSS-specific information.
A variable’s name is the name that appears in the first column of the Descriptive
Info view in the RMPCT off-line design program. The variable’s name is set by
default to the source of the variable’s data that was used for model identification.
For LCN data, the default name is point.param, where point and param are the
point and parameter of the data’s source on the LCN. You can change the
variable’s name at any time in the off-line design program.
Examples using default variable names:
TC101.PV, Hard High Limit, TC101, X(2) // y_H
TC101.PV, Soft High Delta, TC101, X(19) // y_soft_H
TC101.PV, Perf Ratio, TC101, X(13) // h_fb
F104.OP, Output, F104, T(1) // u_0
Examples using user-entered variable names:
Top Col Temp, Hard High Limit, TC101, X(2) // y_H
Top Col Temp, Soft High Delta, TC101, X(19) // y_soft_H
Top Col Temp, Perf Ratio, TC101, X(13) // h_fb
Top Reflux, Output, F104, T(1) // u_0
The available parameter names and descriptions are listed in Appendix A.

Custom Variable A record to configure a scalar custom variable looks like:
Record cus_name, scalar, DSS Field 1, DSS Field 2 ...
or a custom variable that is an array with length n:
aux_name, array[n], DSS Field 1, DSS Field 2 ...
Example:
Server, AnyDssServerName, order1
TrayT, scalar, T101, PV
KeroEP, scalar, Q105, PV
The same custom variable may be used by more than one DSS server (i.e., it may
appear following more than one server record), but the scalar/array information
must be identical in all occurrences.

Honeywell
Options Record The options record is defined to allow information to be passed from the user to the
controller or the DSS server without the need for modifying the *.xm or *.xs files.
Information that is required only infrequently or for only one or a few types of
DSSs might be passed in the configuration file.
The format of an Options record is:
Options, Field 1, Field 2...
Field 1 is DSS-specific information.
Templates Templates can be used to avoid having to enter repetitive information. A template
record associates a parameter with a DSS item, as follows:
Template, par_name, DSS Field 1, DSS Field 2...
The field par_name is a controller parameter from Appendix A. It is added to the
template, associated with the DSS-specific fields that follow it.
The following record can be used to clear the template:
Template, Clear
Template records are cumulative, so the template consists of all template records
encountered from the beginning of the file or the most recent clear record to the
current point in the file. If a template record is encountered that has the same
par_name as a record already in the template, the information from the new record
replaces the existing information in the template.
To use information in the template, enter * in one or more fields in columns 2...n of
a parameter record. This causes the parameter record to be expanded into as many
records as are currently in the template. The template information is substituted for
*, with information from column 2 in each template record substituted for * in
column 2, information from column 3 in each template record substituted for * in
column 3, and so on.
Example:
Template, Hard High Limit, Spacer, X(2) // y_H
Template, Soft High Delta, Spacer, X(19) // y_soft_H
Template, Perf Ratio, Spacer, X(13) // h_fb
TC101.PV, *, TC101, *
Top Col Temp, *, TC101, *
This causes the last two records above to be expanded to the following:
TC101.PV, Hard High Limit, TC101, X(2)
TC101.PV, Soft High Delta, TC101, X(19)
TC101.PV, Perf Ratio, TC101, X(13)
Top Col Temp, Hard High Limit, TC101, X(2)
Top Col Temp, Soft High Delta, TC101, X(19)
Top Col Temp, Perf Ratio, TC101, X(13)

175
Honeywell
(“Spacer” in column 3 above is optional. Anything or nothing can be entered here

because this template column is not used in the expansions.)
Example:
Server , RMPCT APECS 1.0, order 1
Template , Hard High Limit, _SPHI
Template , Soft High Delta, _HISOFTD
Template , Perf Ratio, _PERFORMR
Top Col Temp , *, TC101*
This causes the last record above to be expanded to the following:
Top Col Temp , Hard High Limit , TC101_SPHI
Top Col Temp , Soft High Delta , TC101_HISOFTD
Top Col Temp , Perf Ratio, TC101_PERFORMR
Since there is only one template, the usual way of setting up a configuration file is
to enter the template records to define the parameters for one type of variable (such
as CV) followed by the parameter records for this type of variable. Then enter the
template records for the next type of variable followed by the parameter records for
this type of variable, and so on.

Honeywell
CV New Value For CVs that are asynchronous (i.e. slower) from the controller, a new value flag is
Flag Addition needed to signal the controller to read the value. The value is set to one by the DCS
and Profit Controller resets it to zero. This is the line in the configuration file used
for the TPS system:
Template, New Value Flag, Spacer, C, 1 //New_Value_Flag
For non-TPS systems, the above line needs to be commented out or deleted. Add
the following lines after the CV section and before the MV section for each
asynchronous CV (Template Clear is only needed once):
Template Clear
CV name, New Value Flag, new value tagname, parameter
Where:
CV name is the RMPCT name for the CV
new value tagname is the tagname of the point indicating a new value
parameter is the parameter (e.g. SP, PV, OP) holding the value one to indicate a
new value.
Example:
An oxygen analyzer samples the stack gas once every two minutes. The controller
is running every minute. The tagname for the analyzer is AI1234 and the tagname
of the point holding the new value indicator is AI1234_NV. The following lines
would be added to the configuration file:
Template Clear
Stack oxygen, New Value Flag, AI1234_NV, SP
MV Windup When a PID controller cannot cause its controlled variable to move, it can “wind
Status up”. It is very important that the Profit Controller knows when a MV is in a wind
up state. This is the line in the configuration file used for the TPS system for wind
up status:
Template, Windup Status, Spacer, ARWOP, // MV_Windup_Status
For non-TPS systems, the above line needs to be commented out or deleted. Add
the following lines after the MV section and before the DV section for all the MVs
(Template Clear is only needed once):
Template Clear
Template, Windup Status, _WU, parameter, // MV_Windup_Status
MV name, , tagname*, *
This modification requires that you create points on your control system that are
named after the MV point with a _WU suffix (any suffix will work). The name
parameter is replaced with the name of the actual parameter used to store the wind
up status. An easy method for creating the list of MVs is to copy the list in the
configuration file just above where these new lines will be inserted. The asterisk on
the end of the tagname is necessary.

177
Honeywell
The Profit Controller expects the following values in the wind up status:
1 = Normal
2 = High
3 = Low
4 = High/Low (control not possible)

Honeywell
B.2 OPC Servers / DssOPCLink
The OPC Protocol (OLE for Process Control) allows data transfers between
different programs. DssOPCLink is a Data Source / Sink (DSS) server allowing
data exchange between any ProfitSuite application and one or more OPC Servers.
Since all ProfitSuite applications are themselves OPC Servers, this Dss is used to
communicate between ProfitSuite applications. This Dss may also be used to
collect / control DCS data via an OPC Server. The following describes the
configuration file record format supported by DssOPCLink.
Server Record The new header for OPC clients is:

Server, DssOPCLink, order n
Records of the following format map a given ProfitSuite datapool Variable /
parameter to an OPC item – causing the ProfitSuite datapool parameter to be set to
the OPC item’s value at the beginning of each control interval and whenever the
parameter’s value changes during an interval, the value is written to the OPC item
at the end of the interval:
< Variable Name>, < Parameter Name>, < Start Array Index>, <OPC
ServerName>, <OPC Item ID>, <OPC Array Indices>, <OPC AccessPath>
where
< Variable Name> is the name of one of the application’s variables as listed at the
end of the .xm or .ym file. Custom variables are also supported
and their syntax is documented in ProfitToolkit manuals.
< Parameter Name> is one of the parameters supported by the type of variable
listed in the first column
< Start Array Index> defaults to 0. If <DP Parameter Name> is an array
parameter and <DP Start Array Index is specified (it is optional),
then the OPC Item values read in are copied starting at this array
index.
Note: the first three columns define a location in the ProfitSuite application’s
datapool
<OPC ServerName> is the Microsoft DCOM ProgId under which the OPC Server
to communicate with is registered. This ProgId is typically
registered when the OPC Server is installed if the server resides
on the local computer or when the client package for the OPC
Server is installed if the OPC Server resides elsewhere.
Typically, the vendor’s documentation indicates the ProgId by
which their server is identified.
If the OPC Server is another ProfitSuite application or a
TPN Server, then the applicaion name listed in the TPS
Status Display or the name under which you registered the
Honeywell
B.2 OPC Servers/DssOPCLink
application via ServerRegistar.exe should be used.
<OPC ItemID> is the ItemId string by which <OPC ServerName> refers to the
datum to be exchanged. Each OPC Server has different
conventions for Item ID syntax. See the Help provided by the
HSMiniBrowser.exe for information on ProfitSuite and TPN
Server item syntax. Refer to the accompanying documentation
for the item syntax supported for other OPC Servers.
<OPC Array Indices> allows opc arrays to be treated as a number of individual
elements. Internally, an OPC item is added to an OPC group for
each referenced element of the OPC array. This feature is useful
when sub arrays are needed, or for OPC Servers, such as the
TPN Server which prefer to treat arrays as collections of scalars.
This option should always be used to access LCN arrays via
TPN Server.
To specify an entire array, set < OPC Array Indices > to 0..N
or 1..N depending on whether arrays start at 1 or 0 in the
target OPC server. Otherwise set < OPC Array Indices > to
n .. m where n specifies the first element of the OPC array
you want to collect and m the last.
<OPC AccessPath> allows an OPC Access path to be specified. Neither
ProfitSuite nor the TPN Server use access paths. When a seventh field is
specified, it is passed along to the OPC Server when this OPC Item is accessed.
Options Records The following Options records are supported by DssOPCLink.

Honeywell
HOSTNAME Options, HOSTNAME, <OPC ServerName>, <Computer Name or IP Address>

The option indicates that <OPC ServerName> should be accessed on the computer
with the name or ip address indicated. This option is not needed to access remote
ProfitSuite applications, TPN Servers, or other registered Hci Components. Also,
OPC Servers that provide a remote DCOM registration don’t require this option. In
a Remote DCOM registration the HostName is listed under the AppID for the
component in the registry and is listed by Dcomcnfg.exe and oleview.exe. For
other OPC Servers, include this option record to access the remote server.
Otherwise, the server will be looked for on the local computer. The PDS runtime
configuration builder includes this option if you fill in the hostname when
configuring a parameter for collection via OPC.
FIRSTARRAYIND Options, FIRSTARRAYINDEX, <OPC ServerName>, <n>
EX
n indicates the index of the first element in arrays for the given OPC Server. The
default is 0. When this OPTION is not specified, DssOPCLink assumes the OPC
Server starts its arrays at index 0 The FIRSTARRAYINDEX only matters when
an array is output to the OPC Server. Normally a safearray with the LBOUND set
to 0 is created and the datapool array is copied starting at the index given by third
config file record field (default is 0). When FirstArrayIndex is present - the
LBOUND is set to the indicated array index (typically 1) instead.
LXS_ACCESS Options, LXS_ACCESS, <access level>

This option indicates the default access level to request from TPN Server(s),
where access level is one of:
View Only
Operator
Supervisor
Engineer
Program
Continuous Control
Point Builder
Intimate User
Blanks and case are ignored. Program is the default.

Honeywell
LXS_PRIORITY Options, LXS_PRIORITY, <priority level>

This option indicates the default priority level to request from TPN Server(s),
where priority level is one of:
LOW_RQST_PRIORITY
NON_CRITICAL_RQST_PRIORITY
MEDIUM_RQST_PRIORITY
CRITICAL_RQST_PRIORITY
HIGH_RQST_PRIORITY

Honeywell
TPN_LICENSE Options, TPN_LICENSE, <TPN ServerName>, <Password>

If the customer specifies their own password when installing the HiSpec version of
TPN Server, then this password must be given here. It is recommended that the
default password be accepted at install time and this record be omitted. This record
is never needed for the full price version of TPN Server.
STRICTNESS Options, STRICTNESS, ServerName, <numeric code>
Set <numeric code> to 0 to allow DQP <--> RMPCT communications to run
through disconnects. The default strictness code is 5. This is the highest level of
strictness. Currently, the only difference between levels of strictness is that when
a connection is lost, mapped datapool parameters that are Not Allowed Bad are
set to a Bad Value. This causes the application to turn off. This behavior is
incorrect for DQP <--> RMPCT communications so set the STRICTNESS code
to 0 for this useage. The default behavior is correct for process data connections.
This record is generated automatically by the PDS runtime configuration builder
for RMPCT and DQP connections.

Honeywell
Templates Templates can be used to define fields to be applied to subsequent definition

records:
Template, Perf Ratio, , , .X(10)
Template, CV Process Low Limit, , , .PVEULO
TopReflux,*,*, SomeTPNServer, AlkyCV01*

TopTemp,*,*, SomeTPNServer, AlkyCV02*
Profit Optimizer The following configuration excerpt illustrates a Profit Optimizer configured to
Example exchange model and optimization data with two Profit Controllers:
DssOPCLink, order 2
Options, STRICTness, t01a_ctl, 0
Options, Strictness, t01b_ctl, 0
// Data for each RMPCT
Template, Clear
// General parameters
// Note that you can have either , , OR ,*, to
propagate the controller name
//
Template, Odd Model Id, , ,
Controller.Odd DQP Model Id
Template, Even Model Id, , ,
Controller.Even DQP Model Id
Template, Controller Mode, , *,
Controller.Controller Mode
// Odd Model to DQP
Template, Odd DQP Model ID, , *,
Controller.Odd DQP Model ID
Template, Odd Scalar 1, , *,
Controller.Odd Scalar 1

Honeywell
Template, Odd Array 1, , *,

Controller.Odd Array 1
Template, Odd Model IF Version, , *,
Controller.Odd Model IF Version
Template, Even Scalar 5, , *,
Controller.Even Scalar 5
Template, Even Array 1, , *,
Controller.Even Array 1
Template, Even Model IF Version, , *,
Controller.Even Model IF Version
// Input to DQP
Template, In Scalar 1, , *,
Controller.In Scalar 1
Template, In Array 1, , *,
Controller.In Array 1
Template, In Array 3A, , *,
Controller.In Array 3A
Template, In Array 3B, , *,
Controller.In Array 3B

Honeywell
Template, In Scalar 2, , *,
Controller.In Scalar 2
Template, In Array 21, , *, Controller.In
Array 21
Array 22
Array 23
Array 24
Array 25
Template, Input From RMPCT Version,, *,
Controller.Input From RMPCT Version
Template, RMPCT Version, , *,
Controller.RMPCT Version to DQP
// List of RMPCT controllers for this DQP
t01a_ctl, *, *, t01a_ctl, *
t01b_ctl, *, *, t01b_ctl, *
// These entries are for Profit Simulator data from DV

bridge input.
Template, Clear
Template, Read Value, , , .Read
Value
Template, Start Sim Value, , , .Start DV
Honeywell
Sim Value
Template, Bias Sim Value, , , .Bias DV
Sim Value
DVBin:t01adv02, *, *, t01a_ctl, t01adv02*
// These entries are for Profit Simulator data from MV bridge input.
Template, Clear
Value
Template, Start Sim Value, , , .Start MV
Sim Value
Template, Bias Sim Value, , , .Bias MV
Sim Value
MVBin:t01amv01, *, *, t01a_ctl, t01amv01*

MVBin:t01bmv01, *, *, t01b_ctl, t01bmv02*
// These entries are for Profit Simulator data from DV

bridge output.
// These entries are to put Profit Simulator output in
DV "measurement" for RMPCT.
Template, Clear
Value
Template, Bias Sim Value, , , .Bias DV
Sim Value
Bout:t01adv01, *, *, t01a_ctl, t01adv01*

Bout:t01bdv01, *, *, t01b_ctl, t01bdv01*
TPN Server The following configuration file shows a Profit Controller configured to exchange
Example process data with LCN points via TPN Server:
Header, RMPCT, Standard Configuration

Number of CVs, 5

Honeywell
Number of MVs, 2
Number of DVs, 1
Server, DssOPCLink, order 1
Controller,Number of CVs, , APP04_TPNsvr, 44NS_CTL.C1
//num_cv
Controller,Number of MVs, , APP04_TPNsvr, 44NS_CTL.C2
//num_mv
Controller,Number of DVs, , APP04_TPNsvr, 44NS_CTL.C3,
//num_dv
Controller,Initialization Pass Counter, ,
APP04_TPNsvr, 44NS_CTL.X(1) // initpass
//
// CV template definitions
Template, Clear
Template, CV Process Low Limit, , , .PVEULO
//Process SP Low Limit
Template, CV Process High Limit, , , .PVEUHI
//Process SP High Limit
Template, Read Value, , , .PV
//y_read
//
04FY245A.PV, *,*, APP04_TPNsvr,
44NSCV01*
04TC033.PV, *,*, APP04_TPNsvr,
44NSCV02*
04FC245O.OP, *,*, APP04_TPNsvr,
44NSCV03*
04FC242.SP, *,*, APP04_TPNsvr,
44NSCV04*
44NSCV05*
// MV template definitions
Template, Clear
Template, Process Low Limit, , , .CVEULO
// Process_CVEULO (CV = calc. value)
Template, Process High Limit, , , .CVEUHI
// Process_CVEUHI (CV = calc. value)
Template, Windup Status, , ,
Honeywell
.ARWOP.internal // MV_Windup_Status
Template, Use This MV, , ,
.MODE.internal // use_this_mv
Template, Read Value, , , .P1
// u_read
Template, Read Process Value, , ,
.PVCALC // u_pv_read
Template, Sent Value if ON, , , .T(1)
// u_0
Template, MV Critical, , , .C1
04AC640R.SP, *,*, APP04_TPNsvr,

44NSMV01*
44NSMV02*
//
// DV template definitions
Template, Clear
Template, Read Value, , , .PV
// u_read
//
44NSDV01*

Honeywell
Appendix C – Instructions for Collecting Data through
Oracle-based PHD Only
C.1 Interfacing Profit Controller/Optimizer/Toolkit to PHD

Overview PHD includes RDIs to collect data from several third party DCSs. This
functionality allows the PHD database to interface between Profit Controller,
Profit Optimizer and Profit Toolkit and these DCSs.
Oracle based A version of the PHD Server known as Embedded PHD was distributed with
PHD versus Release 200 onwards, of the Profit products. Embedded PHD uses a Microsoft
Embedded PHD Access database to store point definitions, and has no interface to the Oracle
Server used by the Oracle-based version of PHD. The intended purpose of
Embedded PHD is solely to historize controller datapool parameters. The PHD
points required for this are built automatically, and there is no support in
Embedded PHD for third party DCS systems, and no user interface to manually
build points.
Data Required The data that Profit Controller requires from a DCS may be categorized as
from DCS follows:
· Data that is essential in order to support control and optimization

functionality.
· Data required to optionally support any schematics or other functionality that
may be available on the DCS. For example, if the DCS is a TPS system, then
the controller can be configured to fully support the standard RMPCT
schematics available on any Universal Station or GUS node.
Typically the data required to support DCS schematics constitutes about 90 % of
the data input/output load for a controller. If you are only using Profit Viewer on
NT to display your controller, the data I/O load can be dramatically reduced by
excluding non-essential DCS points from your .cfg file.
Data points can also be divided into fast scan points and slow scan points. For
example, a CV process value should be scanned at least four times as fast as the
controller execution cycle, to ensure the controller gets the latest data at the start
of each processing cycle. CV process high and low limits however need only be
scanned at a slower rate, say twice the controller execution cycle.
DCS-entered In general, all user visible Datapool parameters can be accessed through Profit
data Viewer. However, a particular application may require some controller data items
to be entered manually by an operator at the DCS level. You can send these values
to the controller by adding the appropriate record to the .cfg file and then building
the corresponding PHD points.

Honeywell
Appendix C – Instructions for collecting data through Oracle-based PHD Only
C.1 Intefacing Profit Controller/Optimizer/Toolkit to PHD
Planning the The number of PHD RDIs you decide to use to collect data for a controller
number of RDIs depends on two main factors:
· The data I/O load

· Synchronization requirements
For example, a medium size controller supporting schematics on a TPS system
will require about 7000 PHD database points. In this case, it might be desirable to
split the data collection load across two RDIs, one for fast points and a second for
slow points. Smaller controllers that do not support DCS graphics may only need
one RDI. In practice one RDI may in fact be used for more than one controller,
providing the controllers have the same execution frequency.
In PHD, the RDIs can be offset from the top of the minute and this feature should
be used to synchronize the RDI scan cycle with the controller execution cycle.
Ideally, the RDI should complete a scan cycle a few seconds before the controller
executes. You can use the PHD utility PHDMAN to monitor this.
As a general design principle, the RDI scan frequency and offset parameters
should be specified so as to ensure that the controller receives the most up to date
values for each calculation cycle.
Scheduling a Controllers can be scheduled either from the NT operating system or from the
Controller DCS, providing the DCS supports some sort of triggering mechanism. The Server
record in the .cfg file specifies the type of scheduling to be used.
The RC_Bldr RC_Bldr is a utility included with Profit Controller that enables you to build the
Utility PHD database for a controller or optimizer. RC_Bldr will compose a PHD Tag
Load file based on the records in the .cfg file, so that there is a one-to-one
correspondence between the .cfg file records and the database points needed by
the controller. The types of PHD points required to support a controller depend on
the type of DCS being used to gather data. RC_Bldr currently supports two types
of DCS, TPS system and Yokogawa. Also included with Profit Controller are two
.SQL files for each supported DCS that can be used to directly load the Tag Load
Source System table and the Source Attributes table in the PHD relational
database. These tables are normally completed manually using TotalPlant
Information. For Yokogawa, RC_Bldr also builds an .SQL file that can be used to
directly load the virtual PHD tags required to map parameters into the PHD
relational database.
If you are using an unsupported type of DCS, then executing RC_Bldr for either
one of the two supported DCS (whichever is most like your DCS), will provide
files that can be easily edited manually for a specific DCS.

191
Honeywell
Appendix C-Instructions for Collecting Data through Oracle- based PHD only
Assigning For every DCS parameter required for your controller, a corresponding PHD
Points to RDIs database point must be built. The PHD point definitions are defined by the
parameters written to your configuration file by the Profit Design Studio Run
Time Configuration utility. The corresponding PHD points are built using the
PHD Tag Loader utility, which requires a CSV formatted ASCII file as input. The
RC_Bldr utility builds this ASCII file for you by parsing the controller’s
configuration file and automatically composing a PHD Tag Loader file in the
correct CSV format.
PHD may have up to 256 PHD Real-time Data Interfaces (RDIs) configured per
node, and you must define each RDI individually, using TotalPlant Information,
as explained in Section C.2. (Note, however, that a TPS node currently can have
only 20 RDIs.)
RC_Bldr distributes the PHD points across 4 RDIs, to read and write data from/to
the DCS. Each PHD point is assigned to one of the RDIs in the Tag Load file as
follows:
RDI_1 - handles fast read/write points
RDI_2 - handles fast write only points
RDI_3 - handles slow read/write points
RDI_4 - handles slow write only points
Distributing the points initially across 4 RDIs gives you the flexibility to reassign
the points to fewer RDIs by manually editing the Tag Load File with simple
global “Replace” commands. In practice, you will probably assign all the points to
one or two RDIs, depending on the controller size.
Using a PHD The PHD Profit Controller can execute on an NT node that has only the PHD
Across a Client software installed. Refer to the “Installing the Uniformance Desktop”
Network
section of the Uniformance Client Installation Guide for instructions to install the
PHD Client. In this case the controller will access the database on the PHD Server
node using the network API. To set up your controller for this configuration you
must add the following line to your controller .cfg file:
Options, Server Name, NODE_NAME/nnnn, ,
where NODE_NAME is the name of the PHD server node
and nnnn is the port that was used when your PHD client was installed. 3000
is the usual default port number.
To run Profit Toolkits, the only needed PHD component is the PHD Client. Other
components may be “unchecked” when the “Uniformance Desktop!” installation
screen asks you which components to install.
The PHD The PHD controller automatically resets the value of a PHD Watchdog timer point
Watchdog to zero at the end of every successful execution cycle. It is the responsibility of the
Timer control engineer to write an independent Watchdog program that checks the
Watchdog timer point every cycle and, if it is zero, set it a value of one. If, at the
Honeywell
next cycle, the value is still one, then the Watchdog program can assume that the
controller failed, and can take appropriate action. The Watchdog program is
usually implemented on the DCS, and not on the NT node, so that any NT
hardware failure can be detected.
To configure a Watchdog timer point, add the following line to your controller
.cfg file.
Options, Reset Watchdog, your_ctl, WD, // Reset watchdog timer
where your_ctl.WD is the name of the PHD Watchdog point.

193
Honeywell
Mapping data The Profit Controller Datapool expects standard values for all parameters,
values from a
regardless of the DCS type. For example, the MV mode status must be MAN or
third party DCS
to the Datapool AUTO or CAS, represented as an 8-character string. Third party DCSs may use
different values or data types to represent the same mode status. In this case, you
must use PHD virtual tags to map the DCS value to the standard value expected
by the Datapool. The following two tables specify the mapping required for Profit
Controller and Profit Optimizer, respectively.
RMPCT Process Connected Data Points and Mapping

Datapool Description Required / Valid PHD Dss Server Description
(from .cfg file) Optional Data Type Values
(Control Point)
(CV Points)
Read Value Required Real Input Any real value CV Process Value
New Value Flag Optional Real Input Any real value Analyzer update ready
CV Process Low Limit Optional Real Input Any real value CV Process Low Limit
CV Process High Limit Optional Real Input Any real value CV Process High Limit
(MV Points)
Sent Value Required Real Output Any real value Controller output from MV to control element.
Cascade Status Optional Real Output 0: OFF, 1: INIT, 2: Output to the DCS for possible mode
ON. switching.
Read Value Required Real Input Any real value Read back of Sent Value
Read Process Value Required Real Input Any real value MV Process Value (same as Read Value
unless predict-back or CV compensation
options are used in which case use the PID’s
PV)
Use This MV Optional String Input / MAN or AUTO or MV control status – CAS means MV is
Output CAS connected to controller, MAN or AUTO means
MV is not connected to controller
Windup Status Required String Input HI or LO or HILO MV Windup status – HILO indicates break in
or NORMAL output path, HI or LO indicates windup in
output path
Process Low Limit Optional Real Input Any real value MV Process Low Limit
Process High Limit Optional Real Input Any real value MV Process High Limit
(DV Points)
Windup Status Optional (needed String Input HI or LO or HILO DV Windup status– HILO indicates break in
for predict-back or or NORMAL output path, HI or LO indicate windup in output
CV compensation path
options)
Read Value Required Real Input Any real value SP of DV control loop for predict-back or
Honeywell
RMPCT Process Connected Data Points and Mapping

Valid PHD Dss Server
CV compensation options, otherwise DV
Process Value
Read Process Value Required Real Input Any real value DV Process Value (same as Read Value
unless predict-back or CV compensation
options are used)
Use This DV Optional Real Input Any real value DV control status
Profit Optimizer (DQP) Process Connected Data Points and Mapping

Datapool Description Required / Datapool Valid Datapool Values Description
(from .cfg file) Optional Type
(MV Bridge Inputs)
Read Value Required Real Any real value MV Bridged Input Value from
DCS
Alive Flag Required Real Any real value MV Keep Alive Flag
(DV Bridge Input)
Read Value Required Real Any real value DV Bridged Input Value from
DCS
Alive Flag Required Real Any real value DV Keep Alive Flag
(Bridge Output)
Read Value Required Real Any real value Used by DQP to correct bias

195
Honeywell
Building the PHD Tag Load File

Step Action
1 The steps in this procedure must be carried out for each controller you implement.
Before you start, decide on the names of the RDIs that you will use for your controller. A PHD
RDI name may be up to 10 alpha numeric characters long, of which you may specify the first 8
characters or less. This is referred to as the base RDI name. For clarity, the RDI names should
reflect the controller name. For example, for a controller named as PHD1_CTL, a suitable base
RDI name would be PHD1_CTL.
Note: You will need the RDI names from this section when performing Section C.2.
2 From a DOS prompt, enter the following commands to execute the Tag Load File Builder:
>CD \Programs Files\Honeywell\HiSpec Solutions\Profit Controller
>RC_Bldr
3 In answer to the question
-I- Please select the target DCS for this Tag Loader file:
Choices are 1) for TDC 3000
2) for Yokogawa
Enter your selection:
Enter either 1 or 2, depending on the DCS you are using. Note that TDC 3000 is the same as
TPS system. For other third party DCSs that are not yet supported by RC_Bldr, you may use
one of the above DCSs as a starting point and then edit the file to build PHD points to support
your DCS. Note that selecting 2 will also produce an SQL batch file for the virtual tags and their
function definitions required to map MV point antiwindup statuses and modes to the
enumerations expected by RMPCT. These files can be used as a starting point for other DCSs.
4 In answer to the prompt:
-Q- Enter a valid Controller Name:
Enter the name of the controller for which you want to build a database, for example PHD1_CTL.
If the controller configuration file is not found in the \USERS\HISPEC\CONFIG directory the
program will abort at this point.
5 If a valid configuration file is found, the Builder prompts you for the Base RDI name:
-I- The PHD RDI names for “controller” will be
composed from a base RDI name of 8 characters or less
which you will be prompted for.
-Q- Please enter the Base RDI Name:
Enter the Base RDI Name you have chosen, for example PHD1RDI. The Builder will compose 4
RMPCT RDI names by appending the suffixes “_1”, “_2”, “_3” and “_4” to the Base RDI Name.
The Tag Load File will then be built in the \USERS\HISPEC\APPS directory, with the name:
controller_name.DB
A report file named: controller_name.RPT
and a batch SQL file named: controller_name.SQL
are written in the same directory. The report file contains information and statistics about your
PHD database. You should print out this file for future reference.
6 Continue with Section C.2.

Honeywell
C.2 Building the Oracle-based PHD Database for Profit
Controller
Reality Check The steps in this procedure must be carried out for each controller you implement.
This section describes how to build the components of the PHD relational database
needed to support Profit Controller. The steps are as follows:
· Define the RDIs used in the Tag Load File
· Define the Tag Load Interface Configuration
· Define the RMPCT Parent tag
· Load the Tag Source attributes
· Load the Source System field names
· Load the RMPCT Tag Load file
To do this you use the ‘TotalPlant Information’ utility on the PHD Server node.
Procedure Follow this procedure to build the PHD database points for your controller.
Defining the RDIs
Step Action
1 Start TotalPlant Information on the PHD Server node.
On the “Select Application” sub-form select “Process History”.
On the “Select Form” sub-form select “RDI Specification”.
2 Complete the RDI Specification form as shown below, for PHD1RDI_1.
3 Repeat Step 2 for PHD1RDI_2, PHD1RDI_3 and PHD1RDI_4.

Honeywell
C.2 implementing the client software for integration with the TMN Services
Defining the
RDIs

Honeywell
C.2 implementing the client software for integration with the TMN Services.
Defining the Defining the Tag Load Interface

Tag Load
Interface Step Action
1 The steps in this procedure need only be carried out once for each PHD Server.
Start TotalPlant Information on your PC.
On the “Select Form” sub-form select “Tag Load Interface Configuration”.
2 Complete the Interface Configuration form as shown below.

199
Honeywell
Building the
Building the RMPCT Parent Tag
RMPCT Parent
Tag Step Action
Start TotalPlant Information on your PC.
On the “Select Form” sub-form select “Tag Configuration”.
2 Complete the “Tag Config” form as shown below.

Honeywell
C.2 implementing the client software for integration with the TMN Services.
Loading the Loading the Tag Source Attributes

Tag Source
Attributes Step Action
Profit Controller provides a set of two SQL batch files for each supported DCS, to:
· Load the Profit Controller specific CDS parameter names into the PHD Relational
Database.
· Map the column headings used in the Tagload file to the corresponding standard
PHD Tag Load attributes.
2 To Load the TPS system-specific attributes, start a DOS command window on your PC.
· > CD \Program Files\Honeywell\HiSpec Solutions\ProfitController
· > PLUS33 login/password@totalplant lxstagld.sql
· > PLUS33 login/password@totalplant lsxtagsc.sql
where login/password is usually set to TOTALPLANT/TOTALPLANT.
3 Repeat Step 2 for the Yokogawa specific attributes. The corresponding file names are
yktagld.sql and yktagsc.sql.
4 You can check the results of these batch procedures using the TotalPlant Information
“Tag Source Configuration” form and the “Tagload Source System Configuration”
form.

201
Honeywell
Loading the Loading the PHD Tags

PHD Tags
Step Action
1 The steps in this procedure must be carried out once for each controller you implement.
Start theTotalPlant Information utility on the PHD Server node.
On the “Select Form” sub-form select “Tagload”.
2 Complete the Tagload form as shown in Figure below, ensuring that you use the same
parent tag name used in the previous steps.
3 · Click [Tagload].
· Enter the full pathname of the Tagload File.
· Select the [Update existing tags] radio button.
· Click [OK].
The tag load may take several minutes, depending on the size and activity of your Oracle
Server.
4 When the Tagload operation has successfully completed a message box will appear.
Select ‘YES’ to send the changes to your PHD Server.
The results of the Tagload operation are logged in the file: \temp\Tag Load.log
Building the
PHD Tags
Using Tag
Loader

Honeywell
C.3 Configuring Oracle-based PHD for Profit Controller
Reality Check Each Profit Controller requires 4 PHD RDIs. Each RDI must be separately defined
in the PHD relational database.
This section covers the following activities:
· Configuring the PHD RDIs that you used for your controller.
· Editing the PHD system wide parameter files needed for Profit Controller
(RMPCT).
Procedure Follow this procedure to configure PHD for your controller. In the descriptions
“PHD1RDI_1” is used as the RDI name, but you should use your controller
specific RDI names.
Tuning Tuning PHD for Your Controller

Step Action
1 To automatically configure the start/stop files for the RDIs that you have defined, go to a DOS
prompt and enter the following command:
>RDI_SERVICES totalplant/totalplant@totalplant
This will build the command file to start and stop the RDIs defined for this PHD Server.
2 Edit the \PHDServer\NtSite\PHDPARAMS.CMD file and add the following parameters for your
RDIs:
SET PHD1RDI_1:REMCLOCK 0
SET PHD1RDI_1:REMSYNCH 1
SET PHD1RDI_1:OFFSET -3
SET PHD1RDI_1:STATISTICS 1
SET PHD1RDI_2:OFFSET 3
Each RDI is synchronized to the DCS time so that the offsets are relative to the top of a DCS
minute. On a TPS system, the main controller point is usually built to execute 5 cycles (2.5
seconds) after the top of the minute. As you add more controllers you should adjust the offset
of each RDI so as to smooth the PHD data access load as much as possible.

Honeywell
C.3 Configuring Oracle-based PHD for Profit Controller
Tuning PHD for Your Controller

Step Action
3 Edit the \PHDServer\NtSite\PHDPARAMS.CMD file and add the following system parameters
for RMPCT:
SET PUT_MEMPROTECT 0
Important Note: If you are using PHD tags which provide manual inputs to virtual tag
calculations, then make sure the DBM_TAGFILTER parameter is set to 0. If this parameter is
set to 1 then manual input tags are not loaded into memory and the virtual tags will not
function.
4 Check the PHD_TAGS and the MAX_TAGS parameters in PHDPARAMS.CMD and verify that
the PHD system can support the number of tags needed for your controller(s).
Important Note: Your PHD site license may determine the number of PHD database points
you can build. If you need more PHD points for your controller you MUST upgrade your PHD
license. Do NOT violate your site license for PHD.

Honeywell
C.4 Synchronizing RDI Execution with Controller MV Interface
Points
Overview IMPORTANT:
For Profit Controller to function correctly, the DCS process values must be collected
by the PHD RDIs from the interface points on the DCS after the process values have
been updated and just before the control execution cycle. Since the PHD RDIs run
asynchronously with the DCS, this in general may not happen. The procedure for
correcting this on a TPS system is described below, but for any third party DCS you
must address this problem based on the DCS characteristics.
TPS System- For a TPS system-based Profit Controller to function correctly, the MV DV, and CV
Specific Case values must be collected from their interface points on the DCS before the control
execution cycle. The process values are stored into the interface point parameters
from the process-connected points whenever the interface point executes.
Profit Controller Point Builder builds the first MV, DV, and CV interface points
with CYCLE parameter values 1 or 2 cycles less than that of the main controller
point, and specifies that the remaining interface points run after each other, starting
with the corresponding first interface point (e.g., MV01, CV01 and DV01).
This means that the interface points execute just prior to the main control point.
Since the PHD RDIs run asynchronously with the points on the LCN, the fast RDI
probably will not execute after the interface points have executed and before the
main control point executes. This means that the control calculations will be
performed using the values from the previous control cycle, leading to undesirable
results.
If you are running your controller against the LCN based simulator instead of the
process, the same problem will occur. This is true because in this case, the
simulation calculations (which store the simulated values into the MV point
parameters) will run just prior to the main control point, and before the fast RDI can
collect the latest simulated values.

Honeywell
C.4 Synchronizing RDI Execution with Profit Controller MV Interface Points
Synchronize your RDIs with Your Controller Execution
Step Action
1 For controllers connected to the process, reconstitute the controller. GETD point and change the
value of the NORMCYCL parameter to:
NORMCYCL(original) + (Controller Interval(secs) * 2) / 3
Since the units of CYCLE are half seconds, this will make the interface points execute half a
control interval before the next controller execution cycle, and will allow the fast RDI to run at
least once before the control calculations. Adjust your RDI offsets accordingly.
2 For controllers connected to the LCN based simulation points, reconstitute the controller. GETD
point and change the value of the NORMCYCL parameter to:
(Controller Interval * 2) / 2
Since the units of CYCLE are half seconds, this will make the simulation CL blocks execute half a
control interval before the next controller execution cycle, and will allow the fast RDI to run at
least once before the control calculations.

Honeywell
C.5 PHD Security Groups
If you are planning to use the PHD based version of Profit Controller or Profit
Optimizer you must add the ProfitUser account or the account your controller is
registered under, to the following PHD Security Groups. In a Honeywell TPS
domain, controllers are registered under the ‘TPSComSvr’ account, and all
Profit Suite installations automatically add the account to the PHD Groups.
PHD_MANAGER
PHD_EDITDATA
PHD_PUTDATA
PHD_SECURITY

207
Honeywell
Appendix D – Server Registrar/Registering an Application
D.1 Using the Server Registrar

Overview The Server Registrar can be used to register applications on the local computer or
on any networked computer that has the proper registration software installed.
Registering updates the NT or WIN2K registry so that local and remote clients can
connect to applications.
Server Registrar To start the Server Registrar application from MS Windows, click [Start] and
Programs>Honeywell HiSpec Solutions>Server Registrar.
Non-Registered The left side of the display displays the name and type of the applications that
Applications have not been registered on either the local computer or a network computer.
Local Select Local to view the non-registered applications on the local computer.
Network Select Network to view the non-registered applications on any network-connected

computer. The user may select a specific computer on the network from a drop-
down list of computers on the same domain as the local computer, or alternately
the user may manually enter the name of the computer in the computer text box.
Registered The Applications Status list shown in the middle, right of the window displays the
Applications name, location, type, status, and number of clients for each registered application.
Applications that run on the local computer are shown with an “X” in the Local
column and the location column shows the name of the local computer. Remote
applications have a blank Local column, and the name of the computer on which
they execute is shown in the Location column.
Determining the The list of registered applications is determined by examining the Windows
Registered registry on the local computer. Both local and remote applications may be listed.
Applications When TPS domain replication is taken advantage of, the identical list of registered
applications is replicated to each computer that is a member of the TPS domain.
In non-TPS configurations, two manual techniques may be used to copy remote
Honeywell
D.1 Using the Server Registrar
application registrations to the local Windows registry:

1. Using ServerRegistrar:
a. select the computer where the remote application(s) reside in the
Computer field in the upper left. The list of available
applications that are not currently listed in the Application
Status area in the middle right is displayed.
b. Select the remote application you wish to access locally.
c. Drag the application over the Application Status list or press the
Register button.
d. Select OK on the dialog showing the application configuration.
e. The remote application registration is now copied and the
Application Status list updates to include the new remote
application.
2. Using ProfitViewer
a. Select the AppMenu button to display the Applications Menu.
b. Pull down the list for the Program Applications field.
c. Select “Add ProfitViewer Remote Application”
d. Press the GO button
e. Enter the name of the remote computer or pull down the list and
select the computer in the “Select/Type The Name of the
Computer Where the Application Runs” field.
f. Press the “Get Apps” button. There will be a pause while the
software accesses the registry on the named remote computer.
There may be an error if you do not have permission to access
ths computer’s registry. Otherwise, the pull down list for the
“Select an Application” field is displayed, filled in with the list
of the applications registered on that computer.
g. Select the remote application you wish to access locally.
h. Press the Add button. There will be a pause while the remote
registration is copied to the local registry. The Applications
Status list updates with the new remote application displayed.
Application The application status refresh method controls how often the Applications status
Status Refresh information on the right side of the display is updated. The default is for an
Method automatic refresh every 5 seconds. If manual is selected then the status
information is only updated when the [Refresh] button is clicked.

209
Honeywell
D.2 Registering an Application
Overview The Server Registrar allows registering a Controller, Optimizer or Toolkit
application.
There are three ways to register an application:
1. Click on a non-registered application and then click the [Register->] button.
2. Double click on the non-registered application.
3. Click and drag a file from the non-registered application list to the
Applications Status list.
After using any of the three methods listed, the register dialog appears. The
dialog allows naming of the application and the selection of the associated files.
The configuration file cannot be changed. To use a different configuration file,
click the [Cancel] button and select a different configuration file from the list.
After the application name and files are selected, click the [Register] button. The
[Register] button is not enabled until all required files are selected and the
application name is not blank.
As shown below there are no associated file for a toolkit registration.
When registration is completed a dialog shown below will be displayed and the
newly registered application will appear in the registered applications list.
IMPORTANT: For LCN based controllers; the controller name must match the
8/02
Honeywell
D.2 Registering an Application
controller point name on the LCN.
Registering If a new application is renamed with an existing application’s name, a warning

Using an message is displayed indicating that this new application registration information
will replace the existing application information.
Existing
Application The warning dialog is shown below:
Name
A new local application cannot be registered using the same name as a remotely
registered application. A warning is displayed to allow a different application
name to be entered.
Application
Already
Registered as
Remote
Application
Warning
For TPS Domain- After registration is complete, it is necessary to commit and replicate the
Resident configuration across the TPS Domain using the TPS Configuration Utility. You
must be logged in as a TPS_Administrator for this procedure. You may access
Controllers Only
the replication facility by either selecting the [Replicate] button on the Server
Registrar window, or through the TPS Configuration Utility which can be
accessed as follows:
Start>Programs>Honeywell TPS>Configuration Utility.
See the TPS System Configuration Utility User’s Guide (TP20xxx - Where xxx
= current revision) for more information on this utility.

211
Honeywell
D.3 Modifying an Existing Application
Modify Controller Select an application in the Registered Applications list. A window appears with
the current files associated with the application. Modify does not allow the
application name cannot be changed. However the user may change any of the
associated files.
The main purpose of modification is to change the model or specification file
associated with a controller.
The [Modify] button is not enabled until a change in a file name is detected. In
the example shown below the model file has changed from st01 to st01a.
Config File Changing the configuration file is not recommended, but is allowed as long as the
Change Warning new configuration file is for the same type of application. The application will
only run correctly if the new configuration file is designed to work with the model
and spec files indicated.
Only configuration files that match the application type are allowed. For example,
a controller CFG file can only be modified with another controller CFG file (i.e.
not an Optimizer CFG file).
Config File Type
Mismatch

8/02
Honeywell
Applications that are configured to support simulation via ProfitSimulator on the

NT/W2K platform require that a simulation file be specified. Applications
configured for ProfitSimulator will not run without a simulation file generated by
PDS for the specific application. Applications not configured for ProfitSimulator
ignore the simulation file.
When do Profit Suite applications completely reinitialize when their application status
Modifications transitions from INACTIVE to ACTIVE. However, the model, spec, and
Take Effect? simulation file names stored to the checkpoint file take precedence over the
settings specified via ServerRegistrar. To get these new settings to become
effective, the application must be Terminated, either via the ServerRegistrar
Terminate button, via the TPS Status Display Stop or Terminate command, or via
PrivTaskmgr.exe. After, the process has been terminated, delete the checkpoint
file and the backup checkpoint file
(c:\users\hispec\config\<ApplicationName>.cpt and <ApplicationName>.cpt.bu –
for instance st01.cpt and st01.cpt.bu if the application is named st01). The next
time the application is executed, the new filenames will be used. Alternately, the
filenames used can be updated on the fly via the ProfitViewer <application type>
status display (Controller Status for ProfitController or Optimizer Status for
ProfitOptimizer).
Applications may be brought into execution by:
1. View the application with ProfitViewer or ProfitAssistant.
2. Select the application in ServerRegistrar and press the “Activate” button
3. If Embedded History collection has been configured, and the associated
RDI has not been shutdown and PHD Server is in execution, the RDI will
start the application back up. Note: the RDI is automatically shutdown
when the application is stopped via the TPS Status Display Stop function
or via the ServerRegistrar “Terminate” button. The RDI is NOT
shutdown via the TPS Status Display Terminate function or via
privtaskmgr.exe.
4. Applications configured to be synchronized with a TPS APP node are
automatically restarted via a CL program through CL Server when the
main control point on the LCN is has a PTEXECST of ACTIVE.

213
Honeywell
For TPS Domain After registration is complete, it is necessary to commit and replicate the
Resident configuration across the TPS Domain using the TPS Configuration Utility. You
Controllers Only
must be logged in as a TPS_Administrator for this procedure. You may access the
replication facility by either selecting the [Replicate] button on the Server
Registrar window, or access through
Start\Programs\Honeywell TPS\Configuration Utility.
See the TPS System Configuration Utility User’s Guide (TP20xxx - Where xxx =
current revision) for more information on this utility.

8/02
Honeywell
D.4 Profit Assistant Configuration
Overview Users who purchase Profit Assistant and register a controller will be able to
configure the parameters that are changeable by Operators in Profit Assistant by
selecting the [Configure ProfitAssistant] button on the Modify Application dialog.
Users may configure the operator changeable flag for a wide range of CV, MV
and DV parameters.
The user only needs to make changes to these settings if the defaults are not
sufficient.
To change the configuration, select the row associated with the parameter you
wish to change, and this will toggle the “Changeable” setting. The change takes
effect immediately.

215
Honeywell
D.5 Application Security Settings
How To Set The Security Settings dialog box is called up by selecting a registered
Application application from Applications Status list of the Server Registrar display and
Security then selecting the [Security] button at the top of the display.
What Does The applications security settings determine whether a particular group/user
Security Really operating on a particular computer has access to an application. If the
Impact? security settings do not allow access then typically this means that the
group/user will be able to view but not control the application.
NT/WIN2K Groups The User and Group based security is based on the NT or WIN2K security
and Users model. It is possible to allow or deny access based on the NT Users or
Groups that have been setup.
Computer and In order for a particular NT/WIN2K user/group to have access to an

Group/User application, both the computer the user/group is accessing the application
Security from, and the user/group must have access to the application.
Access rights are determined as follows:
1. Does this computer have access to the application? If the answer to this
question is no, then none of users/groups operating from this computer
will have access to the application.
NOTE: when the “Computers with Access to Application” list is empty,
ALL computers are granted access. When 1 or more computers are
listed, only those computers listed are granted update access to the
application.
2. If the answer to the question is yes, then only the users/groups that are
in the “Users/Groups With Access to Application” list have access to
the application.
Security Roles Application security is only one aspect of security. Another aspect is the
Security Role configuration – ProfitSuite user interfaces (ProfitViewer,
ProfitAssistant, and ServerRegistrar) allow or deny certain functions
depending on what security role the logged in user is assigned to. Typical
security roles are operator, supervisor, engineer, and administrator. This
topic is described in detail in Section 13.

8/02
Honeywell
D.5 Application Security Status
Setting Computer The default is for an application to be accessible from all computers.
Security
Important Note:
When the
“Computers With
Access to
Application” list is
empty, then all
computers have
access to the
application.
The above diagram shows an empty list. Contrary to what you might think,
when the list is empty, all of the computers have access to the application.
Restricting If the user desires to restrict access from certain computers, then simply add
Computers the computers that require access to the application. By doing so all other
Access to computers will not have access to the application.
Applications
The above diagram shows an application that allows access from only
COMPUTER1 (I.e. all other computers do not have access to the
application).
Adding Users may add computers by either selecting from the drop-down list or by
217
Honeywell
Computers manually entering in the computer name. Once the computer has been added
then select “Add”.
NT/WIN2K By default, the following users/groups to have access to the application:

User/Group o EveryOne, and
Security o ProfitUser (when not on a TPS domain)
o TPSComServer (when on a TPS domain)
The above diagram shows an application that allows access to the following
users: ProfitUser and EveryOne.
Restricting Simply remove EveryOne if the user desires to restrict access from certain
Users/Groups groups/users, and then add any users/groups that require access to the
Access to application.
Applications
The above diagram shows an application that allows access by the “Tech
Support” group (I.e. EveryOne has been removed, and because of this all
other users/groups do not have access to the application).

Honeywell
Adding a User or By selecting [Add], the Add User or Group dialog is called up, whereupon
Group the user may select from groups and users in any selected domain.
To see the users in the domain, the Show Users check box must be selected.
Multiple groups/users may be selected. To complete the configuration the

user simply selects Add.
More that 2500 The Groups (and Users) list shows a maximum of 2500 groups/users. Thus,
Users if the group/user you require is not in the list, then you must manually enter
the group/user.
Manually Adding a A group or user may be added by typing in the group or user name manually
Group or User via the Security Settings dialog and the selecting Add. The correct format is
Domain\Groupname or Domain\Username. Some special groups like
Everyone do not require a Domain name prefix.
Removing To remove groups or users, select the group(s) and user(s) and then select
Group(s) or Remove.
User(s)

219
Honeywell
Special Users - It is a requirement that ProfitUser (when not running on a TPS domain) and
ProfitUser and TPSComServer (when running on a TPS domain) always must have access
TPSComServer to the application. As such it is impossible to remove these users from the
list of Users/Groups With Access to Application.
The following message is displayed if an attempt is made to remove the

user:
Application It may be helpful to note that Server Registrar Security settings actually
Security File – manipulate a file called Application.sec (where Application is the name of
Application.Sec the application being configured for security).

Honeywell
D.6 Viewing a Registered Application
Viewing an Click on an application in the registered application list and then on the
Application [View] button.
This will launch a new instance of Profit Viewer for the selected application.
It may take several seconds Profit Viewer to launch, if it is the first
connection to the application.

221
Honeywell
D.7 Activating/Inactivating a Registered Application
Activating an Click on an application in the registered application list and then on the
Application [Activate] button.
If the application is not currently running, it is started. The
“ApplicationStatus” of the application is set to ACTIVE.
Inactivating an Click on an application in the registered application list and then on the
Application [Inactivate] button.
This will inactivate the selected application.

8/02
Honeywell
D.8 Terminating a Registered Application
Activating an Click on an application in the registered application list and then on the
Application [Terminate] button.
This will terminate the selected application. WARNING: any client
applications, such as ProfitViewer, Profit Assistant, other Profit Suite
Applications, will lose their connection to this application when it is
terminated. The Num Clients field will be 1 or more in this case.
If Embedded History collection has been configured and the PHD Server is
running, then the associated RDI is shutdown. This step prevents the
application from coming back to life at the next collection interval.
Applications may also be terminated via the TPS Status Display Stop
function. Conversely, the associated RDI is always restarted when an
application is started while PHD Server is running.
Note that if the PHD Server is stopped and restarted either manually or due a
system shutdown / restart, all the RDIs again become active. Therefore,
previously Terminated applications for which Embedded History collection
is configured are activated. See the section “Removing or Renaming an
Application” in Appendix H to permanently stop history collection for a
Profit Suite application.
Additionally, the Profitxxxx.exe process associated with a given application

may be forcibly ended either via privtaskmgr.exe or the Terminate function
of the TPS Status Display. In this case, the PHD RDI is not shutdown.

223
Honeywell
D.9 Removing a Registered Application
Removing a Click on an application in the registered application list and then on the
Controller [Remove] button.
If the application is running then it will not be possible to remove the
application. A message box appears informing the user to Terminate the
application before retrying.
After the application is removed it will appear in the non-registered

applications list.
A replicate is required for the removal to take effect on TPS domains.

8/02
Honeywell
D.10 Sorting the Non-Registered or Registered
Applications
How To Sort on Click on any column header to sort the applications.
Apps or
For example by clicking on the column header Name the application will be
Hostname
sorted alphabetically according to application names (this is the default
sorting). Clicking on the same header again forces a reverse sort.

225
Honeywell
Appendix E — Using the Special Task Manager
E.1 Privtaskmgr.exe (Formerly TaskMgr_ed.exe)

Overview The Special Task Manager (privtaskmgr.exe) is a special version of the Task
Manager that allows you to end processes to which the normal version of Task
Manager does not allow normal user access. Be very careful using this utility.
Program When a Profit product is installed, privtaskmgr.exe is automatically installed
Location under Program Files\Honeywell\ HiSpec Solutions. In Profit Suite R205 and
higher use of this application is only required under special circumstances. Please
use the Terminate button in ServerRegistrar or the Stop or Terminate functions of
the TPS Status Display instead of this dangerous application. However, proper
usage of this application is described below.
When Would Typically you would only terminate a Profit application process because you want
You Terminate a to:
Process? · Install a new version (upgrade) of the Profit application.
· Re-register the Profit application. A Profit application program must be
terminated before attempting to re-register that program.
· Clear a Profit application program that has stopped operating correctly. This
should rarely, if ever, be required.

8/02
Honeywell
Appendix E – Using the Special Task Manager
Terminating a If preparing to upgrade, re-register, or clear your Profit application software,

Process follow the steps below to first terminate the affected Profit Application process
(Profit Controller, Profit Optimizer, or Profit Toolkit).
Step Action
1 Set the Profit Application process to be terminated to OFF.
2 From the Detail screen of that application, set the active state to
INACTIVE.
3 If you are not historizing Datapool parameters using the Embedded
History function, skip to Step 5.
If historizing Datapool parameters using the Embedded History function,
click Start on your desktop, then select Settings>Control
Panel>Services.
In the Services window, select the Honeywell PHD service, and click
Stop.
4 Still in the Services window, click Startup… and under Startup Type,
Select the Disabled radio button. Click OK.
IMPORTANT: Make yourself a note to change the Startup Type back to
Automatic when you are ready to start the application back up again.
5 Locate the Process ID (PID) of the Profit application you want to
terminate as follows:
· Go to (Drive):\users\HiSpec\Apps
· Double-click the log file for the application you want to terminate.
For example: If I wanted to terminate the cdu1_ctl Profit Controller, I
would double-click cdu1_ctl.log, as highlighted below.
6 Determine the PID for the affect Profit application by locating the Proc
ID number. In the example log file below, the Proc ID is 222.
12Apr01 12:52:04 Begin RMPCT controller start-up
12Apr01 12:52:04 Cmd Line: cdu1_ctl cdu1_ctl.cfg cdu1_ctl.xm cdu1_ctl.xs cdu1_ctl.xp
12Apr01 12:52:04 Reg File: CDU1_CTL 222 cdu1_ctl.cfg cdu1_ctl.xs cdu1_ctl.xm

227
Honeywell
Step Action
cdu1_ctl.xp
12Apr01 12:52:04 RMPCT cdu1_ctl EXEC M1: Proc ID 222: control thread started
12Apr01 12:52:05 RMPCT cdu1_ctl CON M228: RMPCT kernel ver. 200.0000 running
7 Using Windows Explorer, locate the Private Task Manager program

under: (Drive:)\Program Files\Honeywell\HiSpec Solutions\privtaskmgr.exe.
Double-click privtaskmgr.exe to start the program.
8 Select the Processes tab.
9 Use CAUTION when performing this step, and make sure you are
selecting the correct application.
First ensuring you have found the correct Profit application under Image
Name and the correct PID under PID, select the Profit application
process you want to terminate, then click [End Process].

Honeywell
10 The following warning message will appear.
Click [Yes] to end the process.

11 If the following message box then appears, ensure you are running the
privtaskmgr.exe and not the normal NT Task Manager.
Perform this procedure again using the privtaskmgr.exe program.

NOTE: If Embedded PHD is configured to get history for this Profit application
process, PHD Service will automatically start the Profit application process for
you.
Termination If you are unable to terminate the process, it may be because you do not have
Attempt Didn’t “debug programs” rights.
Work? Follow these steps to check your user rights:
Step Action
1 Select Start>Programs>Administrative Tools>User Manager
2 Select Policies>User Rights
3 Select the “Show Advanced Users Rights” check box.
4 Drop down the Right list and select “Debug Programs.”
The “Grant To” box will list all the groups that have this right. If you are not
in one of the listed groups (you can check membership in each one by
double-clicking on them), then your system administrator will need to give
your group that right.

229
Honeywell
Appendix F — Using DSS RDI, RDI Server to Communicate
with 3rd Party Systems
F.1 Overview of DSS RDI and RDI Server

Overview As a user of the Profit Suite (Profit Controller, Optimizer and Toolkit), you have
the ability to communicate with 3rd party systems using the DSS RDI supplied
with all Profit Suite applications. The DSS RDI uses a Uniformance product
called RDI Server – which has similarities to the Uniformance PHD product - to
perform the communication. Simply put, you have the ability to get/put numeric
and string values from/to foreign systems.
The following diagram provides an overview of how you would configure a Profit
Application to communicate with foreign systems using DSS RDI and RDI
Server.

8/02
Honeywell
rd
Appendix F- Using DSS RDI, RDI Server to Communicate with 3 Party Systems
F.1 Overview of DSS RDI and RDI Server
The following list summarizes how RDI Server is configured to get/put data
from/to 3rd party systems:
· In Profit Design Studio, you configure the RDI type and the parameter
connection for the RDI. This information is stored in the CFG file.
· The Profit Application’s DSS RDI reads the information in the CFG file, and
based on the information, writes information to the NT Registry and XML
Tag File(s) to configure RDI Server.
· RDI Server reads the information in the NT Registry in conjunction with the
data in the XML Tag File(s) and is able to get/put data from/to 3rd Party
Systems.
The RDI Server can communicate with many different 3rd Party systems as long as
the appropriate RDI is available.
Terminology RDI (Remote Data Interface) – Software used to get/put data from/to a 3rd party
system. Examples of RDIs are ones to communicate with OPC-compliant
applications, and ones to communicate with various DCS vendors such as
Honeywell, Yokogawa, etc.
RDI Type - Type of RDI, for example – OPC, Honeywell, Yokogawa, etc.
RDIServer DSS – Part of Profit application that communicates with RDI Server
in order to get/put data from/to 3rd Party systems.
RDI Server - Uniformance product that runs as an NT Service which is capable
of dealing with many different RDI types.
RDI Server Tag – Each parameter to get/put is represented as a tag and tag
number in RDI Server.
Tag XML file - Each parameter to get/put is configured in this XML formatted
file.

231
Honeywell
F.2 Installation Considerations
Installing RDI RDI Server is not included on the Profit application disk. A simple installation is
Server available on a separate installation disk.
RDI Server must be installed before starting a Profit application that uses DSS
RDI for its data connections. Note that DSS RDI is installed as part of the Profit
Suite application (similar to all other DSSs).
RDI Server Runs RDI Server runs as an NT Service. Once the RDI Server installation is complete
an NT Service the service is automatically started up. To verify that the service is running, select
Control Panel>Services and then search for the Uniformance 200 RDI Server as
shown in the diagram below. The “Status” should be Started and the “Startup”
should be Automatic. This setting of automatic startup ensures that the RDI Server
service will automatically startup every time the computer is rebooted.
Additional Certain RDI Types require additional installation steps. Typically the additional
Installation steps involve installing client-side software specific to the RDI type. For example,
Instructions for the At-a-Glance RDI requires client-side software to be installed for RDI Server to
Some RDI Types work. Please refer to Uniformance RDI Server Documentation for detailed
instructions on the additional installation steps for some RDI types.

8/02
Honeywell
F.3 How RDI Server is configured to Get/Put Parameters
Overview This section details how RDI Server is configured to be able to get/put parameters
on 3rd party systems.
Generally speaking the way this is accomplished is that DSS RDI reads the
connection information in the Profit application configuration file (.CFG file) to
determine what 3rd party system parameters to connect to.
DSS RDI then adds registration information relating to the RDIs into the NT
registry. DSS RDI also generates a XML formatted file called the Tag XML File
containing parameter connection information so that RDI Server knows which
parameters to get/put.
Information DSS RDI automatically creates a key for each required RDI in the following
Stored in the NT location in the NT registry:
Registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RDIServer\Parameters\RDIList
A brief description of each key is provided:
· Executable – the full path and file name of the RDI DLL.
· OutputFile – the full path and file name of the log file where RDI Server logs
status information.
· Parameters – Contains values specific to the RDI type, in this example OPC.
Tag XML File RDI Server refers to parameters it collects as tags (similar to Uniformance PHD)
thus the configuration file which contains the 3rd party system configuration
information is called the Tag XML File. Obviously the file is in XML format.
DSS RDI automatically creates an XML file for each RDI.
The files are named RdiName.xml, where RdiName is the same as the registry
key under RdiList. In the example above the filename would be OPC1.XML.

233
Honeywell
What Data is As can be seen from the sample Tag XML file below, there are many parameters
Required in the that need to be configured to get a single value from a 3rd party system. The most
Tag XML File?
important parameters are:
· The shorttag.xml file should reside in the same directory as the XML file.
· Tag tagname and tagno - this is the name by which RDI Server refers to the
parameter to be collected. These should be unique.
· All parameters starting with “src_” – This is information required by the RDI
Server to identify parameters on the 3rd party system. Important Note: the data
configured here is exactly the same when configuring a PHD tag for an RDI.
· The root node, shown in the example as OPCRDIOPC1, must be named the
same as the XML file.
· A Tag XML File may contain many tags.
Note: This example shows a tag configured for an OPC RDI. The OPC parameter
is named “:CV00.ReadValue” and is a floating point value 4 bytes long. Since this
is not an array value the src_index parameters are set to zero.

Honeywell
F.4 How to View the Detailed Status of RDI Server
RDI Server – RDI Server has some diagnostic screens that can be viewed by running TELNET.
Detailed Status
Using TELNET to 1. Start a TELNET session. Select Start>Run, then type in TELNET as shown:
View RDI Server
Status
procedure:
2. Select Connect>Remote System, enter the Host Name and Port as shown,
then select the [Connect] button (note that LOCALHOST means that RDI
Server is running on the local machine):
3. Enter a valid UserName and Password.

235
Honeywell
rd
Appendix F – Using DSS RDI, RDI Server to Communicate with 3 Party Systems
F.4 How to View the Detail Status of RDI Server
4. At the RDIServer prompt you can do the following commands:
· MON RDI – to view the states of the RDI(s) (See sample below).
· START RDInnn – start the RDI
· SHUT RDInnn – stop the RDI
The following screen shows sample output from MON RDI:
Note that users familiar with Uniformance PHD will be familiar with the output of
MON RDI.

8/02
Honeywell
Appendix G — Profit Suite Integration with Alert Manager
G.1 Overview of DSS2SFF and Alert Manager

Overview The Profit Suite products (Controller, Optimizer and Toolkit) can be integrated
with @sset.MAX Alert Manager. The goal of this integration is to send messages
in the Profit applications log file to Alert Manager (i.e. the .log file that resides in
the Users\Hispec\Apps directory).
To accomplish this integration, a DSS called DSS2SFF is provided for all Profit
Suite Applications. This DSS converts Profit application alarms and messages into
Scout File Format (SFF) that the Alert Manager Server then processes.
Communication The Alert Manager server is typically installed on a different computer than the
with Alter Profit application. As such several communications utilities are required to shuttle
Manager the Scout File to the Alert Manager server. These utilities are not provided on the
Profit Suite installation CD, but are available with the Alert Manager product.
Important Note: that DSS2SFF will not function properly unless these utilities
are installed.
Profit Profit Design Studio allows all Profit applications to interface with Alert Manager.
Applications It does so by putting the following record for the DSS2SFF into all Profit
Interfacing with applications’ configuration files (.CFG).
Alert Manager
Server, HS_DSS2SFF_1_0, order 4
DSS2SFF_Run, scalar(Value=0.0;Chkpnt=0)
This record shows that an associated custom variable called DSS2SFF_Run can
be used to turn DSS2SFF off (set to 0) or on (set to 1). This variable defaults to
off, but can be turned on via the HSMiniBrowser utility.

237
Honeywell
Appendix H — Profit Suite Embedded History
H.1 Overview
How It Works Profit Suite Embedded History allows the historization of all desired application
parameters into a local embedded Uniformance Process Historian. A Uniformance
PHD Server is installed as part of the Profit Suite application installation.
Unlike the Oracle-based version of Uniformance PHD, Oracle is not installed.
PHD tag and RDI configuration are performed programmatically by the Profit
Suite software and stored in a Microsoft Access database. Only historization of
Profit Suite data is supported by Embedded History. Oracle-based PHD must be
separately purchased to support all other functionality. However, all data stored
into embedded history is accessible from the Uniformance desktop applications.
Data stored in an embedded historian may be imported to Oracle-based PHD via
the PHD to PHD interface.
History collection for Profit Suite applications is configured in the following
manner:
1. After building the application’s standard configuration in the Profit
Design Studio (R220 or higher) runtime configuration feature, select the
History Builder tab. The resultant point and click user interface allows
any and all parameters of the given application to be configured for
history collection. After selecting the desired parameters, press the
[Build] button. A file named <appname>.csv is created or updated.
2. Copy the .csv file along with the normal application files (.cfg, .xm, .xs
for Profit Controller; .cfg, .ym, .ys for Profit Optimizer; .cfg for Profit
Toolkits) to the c:\users\hispec\config directory of the online system on
which you have previously installed R200 or higher of each Profit Suite
application type.
3. Register the application via ServerRegistrar, if it is not already registered.
4. Call up the application in Profit Viewer.
5. Go to the application detail display (Controller Detail for Profit
Controller, Optimizer Detail for Profit Optimizer, Toolkit Detail for
Profit Toolkits).
6. Press the [Update AutoHistory] button. The button will stay highlighted
until the Profit Suite application has processed the request. This may take
a control interval or 2. If something goes wrong, a new window is
mounted and the log of messages indicating the error reason is displayed.
Otherwise, the button’s appearance returns back to normal.
From this point on, an OPC RDI collects the configured parameters into
the PHD Server once per control interval.

Honeywell
Appendix H – Profit Suite Embedded History
H.1 Overview
7. TotalPlant Information desktop utilities may be used to access the PHD

archives.
8. To modify, add, or remove parameters from history collection:
a. Make sure that the exact .csv file currently in effect on the online
system is in the same directory as the controller builder (.ebb) file
you will import in the next step.
WARNING: It is critical to keep the .csv file to ensure that the file
stays in sync with the Embedded History database. Keep a backup copy
in a secure place.
b. Import <appname>.ebb into Profit Design Studio (R220 or higher)

Runtime Configuration feature.
c. Select the History Builder tab.
You cannot remove tags from PHD because this would invalidate
the archives. However, if you no longer want a parameter to be
historized, select the parameter(s) and press the [Deactivate] button.
You can restart historization for previously deactivated tags by
pressing the [Activate] button after selecting the desired
parameter(s). You may also add new parameters to the list.
d. Press the [Build] button to update the .csv file.
e. Copy the updated .csv file to c:\users\hispec\config on the online
system.
Open the application in Profit Viewer, go to the application’s detail display, and
press the [Update AutoHistory] button.

239
Honeywell
H.2 Troubleshooting
Overview Every effort has been made to trap and report all errors in either
C:\users\hispec\Apps\<APPNAME>.log or
C:\users\hispec\Apps\<APPNAME>_phd.log. However, in some rare cases, PHD
may NOT in fact start collecting history for the configured tags after an apparently
successful invocation of the Update AutoHistory procedure. The following section
will help troubleshoot these situations.
Useful PHD The following commands can be entered from the PHD Management console
Commands window:
1. PHDCTL STOP – stop the PHD Server
2. PHDCTL START – start the PHD Server
NOTE: Any command starting PHDMAN SHO can also be given as PHDMAN
MON. In this case the same information as the SHO command would produce is
repeatedly refreshed until you press Ctrl-C.
3. PHDMAN SHO SYS – this command lists the state of the PHD system
including the state of each configured RDI.
· If the status is completely blank, except for the dashed outlines, then the
PHD Server is not running or is in the process of starting up.
· If the System State is INIT, stop PHD and restart it. If PHD is still in
INIT, reboot. If this doesn’t solve the problem contact TAC as expert
help is required to resolve this situation.
· If the RDI state is *ABORT*, the RDI process failed for some reason.
PHD logging information may be found in
<drive\PHDServer\NtSite\Phdserver.log and
<drive\PHDServer\NtSite\PHD_EVENT.log.
4. PHDMAN SHO INT <APPNAME> – shows the detailed status of the RDI
for the given application.
5. PHDMAN SHO TAG <number or tagname> - shows everything known
about this tag. If you have Access on your system you can look at
c:\users\hispec\config\AutoHistory\phddb.mdb. If you do this BE
EXTREMELY CAREFUL NOT TO CHANGE ANYTHING. The ip_tag
table contains an entry for each configured PHD tag. The tags with no
PARENT_TAG entry describe tags and the others describe RDIs. The
TAGNO column indicates the number for each tag.
Other Every command executed by a Profit Suite application to configure embedded
Troubleshooting history has its output redirected to the file:
Information c:\users\hispec\Apps\<APPNAME>_tmpphd.log. Occasionally this information is
useful in troubleshooting.

8/02
Honeywell
H.3 “Interesting” Features
Overview The following are features of Profit Suite Embedded History that may be of
interest to you, depending on how you use this function.
Automatic After an UpdateHistory request has successfully completed for a given
Application application, an OPC RDI has been configured to collect the specified data from
that application once every control interval. If, for any reason, this application is
Restart
not in execution when the RDI attempts to collect data, the application will be
brought into execution.
Typically, the PHD Server service (Honeywell PHD) is set to execute when the
node boots. When PHD starts up, it starts up all the configured RDIs. Therefore,
the OPC RDIs for configured Profit Suite applications will execute. Consequently,
all the Profit Suite applications for which history collection is configured will
always start up when the node boots.

241
Honeywell
H.3 Interesting Features
Removing or If you remove or rename a Profit Suite application, PHD configuration

Renaming an information referring to the now missing application remains. An OPC RDI will
still attempt to collect tags from the now missing application. The simplest way to
Application
get PHD to forget about the old application is to remove the RDI for that
application. At this point Profit Suite Embedded History has no automated method
for achieving this. Follow these steps to remove an RDI configuration:
· Stop PHD (PHDCTL STOP) or just the RDI: PHDMAN STOP INT <appname>
· Delete the line “START INTERFACE <APPNAME>” where <APPNAME>
indicates the name of the now missing Profit Suite application from the file
<drive>\PHDServer\NtSite\Start_Interfaces.dat.
· Delete the line “EXEC C:\PHDServer\ntsite\<APPNAME>.DAT” where
<APPNAME> indicates the name of the now missing Profit Suite application
from the file <drive>\PHDServer\NtSite\Interfaces.dat.
· Delete the file <drive>\PHDServer\NtSite\<APPNAME>.dat
· Delete the file <drive>\PHDServer\NtSite\Kill_<APPNAME>.cmd
· Delete the file <drive>\PHDServer\NtSite\Go_<APPNAME>.cmd
· Delete the file <drive>\PHDServer\NtExec\rdi_<APPNAME>.exe
· Delete <drive>\PHDServer\GblSect\*.gbl (all.gbl files in this directory)
This step is required to get PHD to re-generate its configuration. If you do not
do this, things should work but if you were to run PHDMAN sho sys, you would
see that the rdi you are trying to get rid of is listed with a status of *ABORT*.
The rdi cannot run because you deleted its .exe file.
At this point, the rdi for the removed Profit Suite application has been removed.
The tags for this RDI are still in the PHD configuration database and in the
archive. These cannot be removed without invalidating the archive. See the next
section if you would like to reinitialize PHD and its archives.
If you stopped PHD, restart it via PHDCTL START command

8/02
Honeywell
Reinitializing The only way to remove tags from the PHD configuration database is to delete
PHD to an Empty everything and start over.
Archive
This step results in the loss of all archived PHD data for this node. DO NOT
DO THIS IF THERE IS ANYTHING YOU NEED IN THE PHD
ARCHIVES. Even if you create backups of the archive files, they will not be
accessible since the configuration information to match the archives will be gone.
You could generate reports containing the important archived information using
the various PHD Desktop utilities – like the Excel Companion.
· Stop the PHD Server (PHDCTL STOP)

· Copy c:\users\hispec\config\AutoHistory\phddb_empty.mdb to
c:\users\hispec\config\AutoHistory\phddb.mdb. This empties your PHD
configuration database.
· Copy c:\users\hispec\config\AutoHistory\Interfaces_empty.dat to
<drive>\PHDServer\NtSite\Interfaces.dat.
· Copy c:\users\hispec\config\AutoHistory\Start_Interfaces_empty.dat to
<drive>\PHDServer\NtSite\Start_Interfaces.dat.
· Delete <drive>\PHDServer\GblSect\*.gbl. This wipes out the Global Memory
Segment images of your PHD configuration.
· Delete all the files in <drive>\PHDServer\Archive. This wipes out your PHD
Archives.
· Create a new, empty PHD Archive via the following command:
PHDMAN CREATE ARCHIVE SCAN0001
· Start the PHD Server (PHDCTL START)
· It takes a few minutes for PHD to start up. PHDMAN MON SYS repeatedly
lists the PHD status. If everything has worked, after a few minutes the System
state should be “ACTIVE” and the RDI list should be blank. Press Ctrl-C to
end the monitor.
· Connect the new archive to the PHD Server and activate scanning to archive:
PHDMAN CONNECT SCAN0001 SCAN ACTIVE
Now a call to PHDMAN SHO ARCHIVE should show SCAN0001
· If you had previously configured history collection for parameters that you no
longer wish to historize – you must modify the .csv files for those applications
before re-configuring the history collection for those apps. The easiest way to
do this would be to (CAREFULLY!) edit the appropriate .csv files
(c:\users\hispec\config\<APPNAME>.csv), deleting the lines for the tags you
no longer want to historize. If you do this – be sure to copy this file to
wherever you are archiving your .xm, .xs, .mdl, .ebb files for this application.
243
Honeywell
You want to make sure that if you ever go back to update your history
configuration in PDS that you use this modified version of the .csv file.
The other way to re-configure history collection is to delete the .csv file, open
the .ebb file in PDS and re-enter the history collection configuration in the
History Builder. Then copy the newly re-created .csv file to
c:\users\hispec\config\<APPNAME>.csv on the online control system.
Now you can re-configure history collection for desired applications by pressing
the Profit Viewer [Update AutoHistory] button for the appropriate applications.

Honeywell
Security Issues To automate the steps required to configure PHD collection of Profit Suite data,
Profit Suite applications execute PHD command line commands and scripts.
These commands would normally end up executing as the user under which the
Profit Suite application is executing. This user is the domain user TPSComServer
on TPS domain systems or the local user ProfitUser otherwise.
Due to Microsoft DCOM functionality, the user name and its password must be
stored in the required DCOM registration for each Profit Suite application in the
NT registry. To avoid security holes, ProfitUser and TPSComServer are set up
such that one cannot log into the system as these users (because their passwords
are too “knowable”). Therefore, these users cannot be added to the various
security groups required to allow them to attain the necessary permission to run
PHD commands
To solve these problems, Profit Suite applications do not directly execute the
necessary commands. A new service, HsCmdSvc.exe has been introduced. The
commands end up being executed by this service. So, the commands “RunAs” the
user that this service is configured to “RunAs.” The Profit Suite installation
software creates a local user (PSEmbeddedHistory) which is assigned a “secret”
password and sets up the HsCmdSvc to “RunAs” this user.
NOTE: If you decide to change the password for the PSEmbeddedHistory user,
you must also change the password entry in the Control Panel / Services /
HsCmdSvc / Startup screen.
The PSEmbeddedHistory user is added to the appropriate PHD security groups
and thus the PHD commands can now execute.

245
Honeywell
TotalPlant The full featured TagExplorer that comes with the TotalPlant desktop WILL NOT
Information WORK with Profit Suite embedded history, but it does work with any and all
Oracle-based Enterprise PHD servers available on your network.
TagExplorer
To enter Profit Suite Embedded History tagnames into desktop applications, use
the Profit Suite TagExplorer available at:
<drive>\Program Files\Honeywell\HiSpec Solutions\PSTagExplorer.exe
and the Profit Suite TagExplorer shortcut under the HiSpec Solutions program
group.
Tagnames may be copy/pasted or drag/dropped from PSTagExplorer to desktop
applications.
File To speed startup, the PHD Server reads its configuration from the “global memory
Synchronization sections” stored in the .gbl files located at <drive>\PHDServer\GblSect. If these
files are present, the PHD configuration information contained in files elsewhere
is ignored. Therefore, if any of these files is modified while the PHD Server is
inactive, the changes will not take effect unless the .gbl files are deleted before
PHD is next started.
However, keep in mind that when a tag is configured, it is assigned a unique tag
number. PHD assumes that these numbers never change and are never reused.
Therefore, it is imperative that the configuration database (phddb.mdb) NEVER
be manually modified.

Honeywell
H.4 Detailed Description of “Update History” Function
Update History This section describes the steps occurring after the Profit Viewer application detail
Function display [Update AutoHistory] button is pressed:
Explained Profit Viewer writes the value 1.0 to the Common.UpdateHistory parameter of the
application. Profit Viewer then leaves the button highlighted until it “sees” the
UpdateHistory parameter’s change to a value other than 1.0. A new value of 0
indicates success, >1.0 indicates an error. The error reason is logged into
c:\users\hispec\apps\<appname>_phd.log. Profit Viewer opens a new window and
displays this file in reverse order (similar to the Status Messages screen) when
UpdateHistory goes to >1.0.
Profit Suite applications are typically suspended waiting for it to be time to run the
next interval. When the time for the next interval arrives, the application wakes
up. When the UpdateHistory parameter is equal to 1.0, if UpdateHistory logic is
not already in progress, UpdateHistory logic is executed.
Update History logic (same for all Profit Suite applications):
1. Verify that the file c:\users\hispec\config\<appname>.csv exists:
if not put out a message, set UpdateHistory to 2.0 and return.
2. Try to dynamically load the PHD client library: netapishr.lib and find all
routines we will need. If this doesn’t work, put out a message, set
UpdateHistory to 2.0 and return.
3. Verify that PHD is installed
if not - put out a message, set UpdateHistory to 2.0 and return.
4. Verify that PHD is started:
if not – try to start it with the PHDCTL START command. If this does not
work, put out a message, set UpdateHistory to 2.0 and return.
NOTE: This generally will fail unless you add the user PSEmbeddedHistory
to the local Administrator’s group. However the PHD Server should always
be running anyway since it starts at boot time.
5. See if an RDI for this app is defined and active:
if not - run the CreateOPCRDI.cmd script to do so. If this does not work, put
out a message, set UpdateHistory to 2.0 and return.
6. Run the ConfigOPCRDI.cmd script to make sure the appropriate RDI parent
tag is configured. If this does not work, put out a message, set UpdateHistory
to 2.0 and return.
7. Run the UpdatePHDTags.cmd script to update the tag configuration and start
collecting history for the tags indicated in <appname>.csv. If this does not
work, put out a message, set UpdateHistory to 2.0 and return.
8. If we get here, everything worked! Set UpdateHistory to 0.

8/02
Honeywell
H.5 Profit Suite Embedded PHD Data Retrieval Configuration
Example
Introduction The following is an example of configuring Oracle-based PHD to retrieve data
from Profit Suite PHD. Note the following instructions are general guidelines
only. Refer to the TotalPlant Information Application User Guide for detailed
instructions.
Example 1. Node A is running Oracle PHD 150.2. For illustration purposes, the computer
Configuration name for Node A is TBAPP07.
2. Node B is running Profit Embedded PHD. For illustration purposes, the
computer name for Node B is TBAPP01.
3. For illustration purposes, APP01CTL and PC3ST01 are used. APP01CTL and
PC3ST01 are Profit Controllers running on Node B (Profit Embedded PHD
Node). Their parameters are historized by the Profit Embedded PHD running
on Node B.
Configure a PHDtoPHD RDI on Node A (Oracle PHD Node) to collect PHD data
from Node B (Profit Embedded PHD Node).
1. Logon to the oracle-based PHD Server node.
2. Select Programs/Total Plant Information/Total Plant Information. Enter the
appropriate password.
3. In the ‘Select Application’ frame, select Process History.
4. In the ‘Select Form’ frame, scroll down and select RDI Specification.
The following display illustrates the Source System PHD RDI configuration on
Node A (Oracle PHD Node) to collect PHD data from Node B (Profit Embedded
PHD Node).
Please note the Port Number 3010. This port number must match the port number
configured during the Embedded History installation under Select Remote PHD
Port.

8/02
Honeywell
RDI Build Oracle-based PHD tags.

Specification
1. Select Window/Menu to return to the TotalPlant Information Menu page.
Page
2. In the ‘Select Form’ frame, scroll down and select Tag Configuration.
3. Configure a Tag on Node A (Oracle PHD Node) whose source tag is a tag on
Node B (Profit Embedded PHD Node).
The Collector Name for this Tag should be the RDI created in the previous
step.

8/02
Honeywell
Example 1 Float The following displays illustrate the Tag configuration.

Honeywell
AppendixH – Profit Suite Embedded History
Data Collection Display

Please note in this display:
· System Type = LOCAL
· Tag Type = F

251
Honeywell
Data Processing Display

Honeywell
General Display

253
Honeywell
Example 2 Char Enable Flags Display

Honeywell
Data Collection Display

On this screen, notice the:
System Type = LOCAL
Tag Type = C

255
Honeywell
Data Processing Display

Honeywell
General Display

257
Honeywell

APC-4500VE SECCION 7. PROFIT CONTROLLER. Instalacion

Uploaded by

Document Information

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

APC-4500VE SECCION 7. PROFIT CONTROLLER. Instalacion

Uploaded by

Copyright:

Available Formats

Profit® Viewer - Profit Controller - Profit Optimizer - Profit Toolkit –

Profit Bridge – Profit SensorPro – Profit Design Studio – Profit Assistant

Printed in U.S.A. – © Copyright 2001 by Honeywell International Inc.

Other product names are trademarks of their respective owners.

ii Profit Suite Installation Guide 8/02

SECTION 1 — BEFORE YOU BEGIN................................................................................. 1

8/02 Profit Suite Installation Guide iii

8.3 Initializing Profit Controller’s Messages ......................................................... 50

iv Profit Suite Installation Guide 8/02

SECTION 17 — BRINGING PROFIT TOOLKIT ONLINE ............................................. 111

D.10 Sorting the Non-Registered or Registered Applications .............................. 226

vi Profit Suite Installation Guide 8/02

8/02 Profit Suite Installation Guide vii

viii Profit Suite Installation Guide 8/02

8/02 Profit Suite Installation Guide ix

Documentation The following documents comprise the Profit Suite library.

x Profit Suite Installation Guide 8/02

8/02 Profit Suite Installation Guide xi

xii Profit Suite Installation Guide 8/02

08/02 Profit Suite Installation Guide 1

2 Profit Suite Installation Guide 8/02

8/02 Profit Suite Installation Guide 3

4 Profit Suite Installation Guide 8/02

08/02 Profit Suite Installation Guide 5

6 Profit Suite Installation Guide 8/02

08/02 Profit Suite Installation Guide 7

8 Profit Suite Installation Guide 8/02

Three distinct environments and three different users are possible:

8/02 Profit Suite Installation Guide 9

10 Profit Suite Installation Guide 8/02

08/02 Profit Suite Installation Guide 11

12 Profit Suite Installation Guide 8/02

8/02 Profit Suite Installation Guide 13

Uninstall earlier 1. Go to Start>Settings>Control Panel >Add/Remove Programs.

4. Click the Yes button to verify.

a. Go to Start>Settings>Control Panel >Add/Remove Programs.

b. Select the program to be removed: TPS – HCI Runtime

c. Click the Add/Remove button.

d. Click the Yes button to verify.

14 Profit Suite Installation Guide 8/02

Note: If there happen to be several TPS Domains configured on the same

08/02 Profit Suite Installation Guide 15

16 Profit Suite Installation Guide 8/02

9. Click [Next] on the Welcome window.

10. Click on [Yes] to accept the license agreement.

8/02 Profit Suite Installation Guide 17

18 Profit Suite Installation Guide 8/02

9. Click [Accept] to accept the License Agreement.

08/02 Profit Suite Installation Guide 19

20 Profit Suite Installation Guide 8/02

13. Click [Next] to accept the Archive Directory.

8/02 Profit Suite Installation Guide 21

17. Click [Next] on the Ready to Install window

22 Profit Suite Installation Guide 8/02

18. Select [Finish] on the Installation Completed window

20. On NT systems; click on Start->Settings->Control Panel/Services.

8/02 Profit Suite Installation Guide 23

9. Click [Finish] when the installation is complete.

24 Profit Suite Installation Guide 8/02

8/02 Profit Suite Installation Guide 25

10. After accepting the License Agreement, click [Next].

26 Profit Suite Installation Guide 8/02

8/02 Profit Suite Installation Guide

28 Profit Suite Installation Guide 8/02