Sei sulla pagina 1di 408

Experion PKS

Integrated Experion-TPS User's Guide

EPDOC-XX66-en-430A
December 2013

Release 430
Document Release Issue Date
EPDOC-XX66-en-430A 430 0 December 2013

Disclaimer
This document contains Honeywell proprietary information. Information contained herein is to be used solely
for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or
disclosed to a third party without the express permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied
warranties of merchantability and fitness for a 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 direct, special, or consequential damages. The information
and specifications in this document are subject to change without notice.
Copyright 2013 - Honeywell International Sàrl

2 www.honeywell.com
Contents

1 About This Document .......................................................................................................................... 13


2 References ............................................................................................................................................ 15
3 Overview of Experion and TPS Nodes ............................................................................................... 17
3.1 Introduction to Experion and TPS Integration .................................................................................................. 18
3.1.1 Intended audience .............................................................................................................................. 18
3.1.2 Assumptions ...................................................................................................................................... 18
3.1.3 System Topology ............................................................................................................................... 18
3.1.4 Enhanced Universal Control Network (EUCN) ................................................................................ 19
3.1.5 Experion Station-TPS (ES-T) ............................................................................................................ 20
3.1.6 Experion Server-TPS (ESVT) ........................................................................................................... 21
3.1.7 Experion Stations ............................................................................................................................... 21
3.1.8 Experion Servers ................................................................................................................................ 21
3.1.9 Console functionality ......................................................................................................................... 21
3.1.10 Application Control Environment (ACE-T) .................................................................................... 22
3.1.11 Experion Application Processing Platform (Experion APP) ........................................................... 22
3.1.12 Control Integration ........................................................................................................................... 22
3.1.13 System data flow .............................................................................................................................. 23
3.2 Multiple Experion clusters on one TPS (LCN) ................................................................................................ 25
3.3 Architectural Overview .................................................................................................................................... 26
3.3.1 ES-T Architecture .............................................................................................................................. 26
3.3.2 ESVT Architecture ............................................................................................................................ 26
3.4 Enterprise Model and TPN ............................................................................................................................... 28
3.4.1 Enterprise Model Builder in Configuration Studio ........................................................................... 28
3.5 Implementation Overview ................................................................................................................................ 30
3.5.1 Implementation flowchart .................................................................................................................. 30
3.6 Implementation Environment ........................................................................................................................... 31
3.6.1 Experion engineering tools ................................................................................................................ 31
3.6.2 TPS/LCN engineering tools ............................................................................................................... 31
3.6.3 TPS engineering tools ........................................................................................................................ 32
3.6.4 Network tree ...................................................................................................................................... 32
3.6.5 System Management Display ............................................................................................................ 33
3.6.6 Operating System ............................................................................................................................... 33
3.6.7 System security .................................................................................................................................. 33
3.6.8 PC station furniture ............................................................................................................................ 33
3.7 Viewing the Process .......................................................................................................................................... 35
3.7.1 HMIWeb displays .............................................................................................................................. 35
3.7.2 SafeView application ......................................................................................................................... 35
3.7.3 Experion standard displays ................................................................................................................ 36
3.7.4 Native Window Displays ................................................................................................................... 37
3.7.5 HMIWeb Faceplates for TPN points ................................................................................................. 37
3.7.6 HMIWeb Detail displays for TPN points .......................................................................................... 38
3.8 Analyzing the Process ....................................................................................................................................... 40
3.8.1 Reports ............................................................................................................................................... 40
3.8.2 Historization ...................................................................................................................................... 40
3.9 Desktop Familiarization .................................................................................................................................... 41

3
CONTENTS

3.9.1 Program groups .................................................................................................................................. 41


3.9.2 Console Station program group ......................................................................................................... 41
3.9.3 System Management program group ................................................................................................. 42
3.9.4 TPS Applications program group ...................................................................................................... 43
3.9.5 SafeView program group ................................................................................................................... 45
3.10 Monitoring Experion-TPS Nodes ................................................................................................................... 46
3.10.1 Monitoring system alarms ............................................................................................................... 46
3.10.2 Monitoring Experion Stations .......................................................................................................... 48
3.10.3 Monitoring System Interfaces .......................................................................................................... 49
3.10.4 Monitoring LCNP Status ................................................................................................................. 49
3.10.5 Analysis Tools .................................................................................................................................. 49
3.11 Documentation Reference Listing .................................................................................................................. 51
3.11.1 References for common user tasks .................................................................................................. 51
4 Supplementary Installation Tasks ...................................................................................................... 55
4.1 Installation checklists ........................................................................................................................................ 56
4.2 Prepare TPS/LCN for Integrated Experion-TPS Nodes ................................................................................... 57
4.2.1 Before you begin ................................................................................................................................ 57
4.2.2 Tasks .................................................................................................................................................. 57
4.3 Post Installation Tasks for ES-T ESVT ACE-T ............................................................................................... 58
4.3.1 Additional tasks ................................................................................................................................. 60
5 Common Platform Tasks ..................................................................................................................... 63
5.1 Copy Load Modules to HM .............................................................................................................................. 64
5.2 Update an Existing NCF for Experion Nodes .................................................................................................. 67
5.2.1 Overview of NCF node configuration procedure .............................................................................. 67
5.2.2 Procedure for configuring the NCF Node ......................................................................................... 70
5.2.3 Building AM Points ........................................................................................................................... 72
5.3 Create Checkpoints for ESVT and ACE-T ....................................................................................................... 73
5.3.1 Procedure for creating check points .................................................................................................. 73
5.4 Additional NCF Considerations ....................................................................................................................... 74
5.4.1 LCN Nodes ........................................................................................................................................ 74
5.4.2 System Wide Values - Console Data ................................................................................................. 74
5.4.3 System Wide Values - Clock Source ................................................................................................. 75
5.5 Time Synchronization Considerations .............................................................................................................. 76
5.6 Add Experion nodes to System Management Display ..................................................................................... 77
5.6.1 Multicast consideration ...................................................................................................................... 77
5.6.2 Procedure for adding a node as managed item .................................................................................. 77
5.7 Verify TPN Server Configuration ..................................................................................................................... 81
5.8 Connect the Transceiver and TPS/LCN Cables ................................................................................................ 83
5.9 Configure LCNP (Board0) Settings .................................................................................................................. 84
5.9.1 Edit LCNP Settings ............................................................................................................................ 84
5.9.2 Edit ES-T Native Window settings .................................................................................................... 86
5.9.3 Edit ES-T Keyboard settings ............................................................................................................. 87
5.9.4 Configure TPS/LCN Printer Settings ................................................................................................ 88
5.10 Load Personality into ES-T ............................................................................................................................ 91
5.11 Load Personality and HM Checkpoint into ESVT ......................................................................................... 92
5.12 Load Personality and HM Checkpoint into ACE-T ....................................................................................... 93
5.13 Establishing Access Permissions for Signon Manager ................................................................................... 94
5.13.1 Purpose of establishing access permissions ..................................................................................... 94
5.13.2 Default access permissions .............................................................................................................. 94
5.13.3 Experion operator security requirements ......................................................................................... 95
6 Configure Experion Database ............................................................................................................. 97
6.1 Procedures included in this section ................................................................................................................... 98
6.2 Procedures in other publications ....................................................................................................................... 99

4 www.honeywell.com
CONTENTS

6.3 Procedure to integrate TPN Units into the Enterprise Model ......................................................................... 100
6.4 Procedure to configure TPS System Interface ................................................................................................ 103
6.4.1 TPS Connection - Tuning properties ............................................................................................... 106
6.5 Procedure to add and configure Operators ..................................................................................................... 108
6.6 Map TPS Units to Experion Assets ................................................................................................................ 109
6.6.1 Multiple Experion clusters on one TPN .......................................................................................... 109
6.6.2 Configuration example ..................................................................................................................... 113
6.6.3 SY Unit mapping to Assets .............................................................................................................. 113
6.7 Procedure to add Experion Console ................................................................................................................ 116
6.8 Procedure to add Console Station ................................................................................................................... 118
6.9 Support Remote GUS with Console Extensions ............................................................................................. 119
6.10 Specify Station Toolbar Definition (.stb) File .............................................................................................. 120
6.10.1 Experion Station Toolbar Definition Files ..................................................................................... 120
6.10.2 Customizing the file ....................................................................................................................... 120
6.10.3 Specifying the .stb file ................................................................................................................... 120
6.11 Configure Audible Annunciation .................................................................................................................. 122
6.11.1 Procedure to be followed when the IKB is present ........................................................................ 122
6.11.2 Procedure to be followed when IKB is not present ....................................................................... 125
6.12 Support TPS on Console Station Extension ................................................................................................. 128
6.12.1 Native Window Displays ............................................................................................................... 128
6.12.2 TPN Faceplates and Group Displays ............................................................................................. 128
6.12.3 GUS Displays ................................................................................................................................ 128
6.12.4 IKB ................................................................................................................................................ 128
7 Multiple Experion Clusters on one LCN ........................................................................................... 131
7.1 Procedures included in this section ................................................................................................................. 132
7.2 Plan the partitioning of TPN units .................................................................................................................. 133
7.2.1 Planning the partitioning of TPN units for multiple Experion clusters ........................................... 133
7.2.2 Rules for mapping TPN unit to an asset on one Experion cluster ................................................... 134
7.3 Publication of the TPN System Alarm ........................................................................................................... 135
7.3.1 Configuring publication of the TPN System Alarm ........................................................................ 135
7.4 Add Experion servers to EMDB ..................................................................................................................... 137
7.4.1 Define Experion clusters in your Enterprise Model ........................................................................ 137
7.5 Configure DSA ............................................................................................................................................... 138
7.5.1 Configuring DSA and data subscriptions between the Experion clusters ....................................... 138
7.6 Verify the unit mapping and the history collection configuration .................................................................. 139
7.6.1 Commands for verification .............................................................................................................. 139
7.7 Save TPS points configuration ....................................................................................................................... 140
7.8 Restore TPS points configuration ................................................................................................................... 142
7.8.1 Configuring the history collection and the point scripts for the TPS points ................................... 142
7.8.2 Apply configuration information to the TPS points ........................................................................ 142
7.8.3 Other options ................................................................................................................................... 143
7.9 Remove mappings .......................................................................................................................................... 144
7.9.1 Removing mappings that are no longer needed on the existing Experion cluster ........................... 144
8 Integrate Experion Control ................................................................................................................ 145
8.1 Integrating ACE-T with TPS .......................................................................................................................... 146
8.1.1 Platform ........................................................................................................................................... 146
8.1.2 Functionality of ACE-T ................................................................................................................... 146
8.2 Integrating Experion Controllers .................................................................................................................... 147
8.2.1 FTE Network Implications .............................................................................................................. 147
8.3 Experion EUCN control integration ............................................................................................................... 148
8.3.1 EHPM configuration block .............................................................................................................. 148
8.3.2 ACE/C300 to EHPM peer-to-peer communication ......................................................................... 148
8.3.3 EHPM point import into ERDB ...................................................................................................... 148

5
CONTENTS

8.3.4 EHPM and ENIM firmware upgrade ............................................................................................... 149


9 Authoring Custom Displays .............................................................................................................. 151
9.1 Display Authoring Approach .......................................................................................................................... 152
9.1.1 Dynamic objects .............................................................................................................................. 152
9.1.2 TPS/LCN data access authorization ................................................................................................ 152
9.1.3 Entering object script ....................................................................................................................... 153
9.1.4 Invoke TPS/LCN displays ............................................................................................................... 154
9.1.5 Shape gallery ................................................................................................................................... 154
9.1.6 Faceplates ........................................................................................................................................ 154
9.1.7 EHPM faceplate ............................................................................................................................... 156
9.1.8 Invoke HMIWeb display from Station command zone ................................................................... 157
9.1.9 Invoke GUS Display from Station Command Zone ........................................................................ 157
9.2 Accessing HMIWeb TPN detail displays ....................................................................................................... 159
9.2.1 Example display with TPN operational parameters ........................................................................ 159
9.2.2 HMIWeb TPN detail displays for Logic tabs .................................................................................. 159
9.2.3 HMIWeb TPN detail displays for Device Control tabs ................................................................... 167
9.2.4 HMIWeb TPN detail displays for Regulatory Control tabs ............................................................. 174
9.2.5 HMIWeb TPN detail displays for Sequence Parameters ................................................................. 181
9.2.6 HMIWeb TPN detail display for CDS Parameters .......................................................................... 197
9.2.7 HMIWeb TPN detail displays for Smart Transmitter Data Configuration Parameters ................... 198
9.2.8 HMIWeb TPN detail displays for Array Points ............................................................................... 199
9.2.9 HMIWeb TPN detail displays for EHPM Node .............................................................................. 205
9.2.10 Native Window Detail invocation ................................................................................................. 208
9.2.11 Display invocation ......................................................................................................................... 210
9.2.12 Enabling HMIWeb TPN detail displays ........................................................................................ 211
9.2.13 HMIWeb TPN detail display integration with SafeView ............................................................... 211
9.2.14 Script invocation of HMIWeb TPN detail ..................................................................................... 211
9.2.15 Example script invocation of HMIWeb TPN detail ....................................................................... 212
9.2.16 Identifying the DISPTYPE parameter ........................................................................................... 212
9.2.17 Examples of other script invocations ............................................................................................. 212
9.3 Deploying HMIWeb Faceplates for TPN ....................................................................................................... 214
9.3.1 Supported TPN point types .............................................................................................................. 214
9.3.2 Configuration overview ................................................................................................................... 215
9.3.3 GUS display invocation of HMIWeb faceplate ............................................................................... 215
9.3.4 Station invocation script invocation example .................................................................................. 216
9.3.5 Identifying the DISPTYPE parameter for a faceplate ..................................................................... 216
9.4 Supporting Display Operations in TPS/LCN ................................................................................................. 217
9.4.1 TPS/LCN and Experion Display support ........................................................................................ 217
9.4.2 Replacing TPS/LCN schematics ...................................................................................................... 217
9.4.3 Pathname search behavior ............................................................................................................... 217
9.4.4 Pathnames for HMIWeb displays .................................................................................................... 217
9.4.5 Pathnames for Universal Station schematics ................................................................................... 218
9.4.6 Pathnames for GUS displays ........................................................................................................... 218
9.5 Implementing the TPS Faceplate Control ....................................................................................................... 219
9.5.1 Inserting TPS Faceplate Control as an ActiveX control .................................................................. 219
9.5.2 TPS Faceplate Property page in HMIWeb Display Builder ............................................................ 219
9.5.3 TPS Faceplate usage consideration ................................................................................................. 220
9.5.4 Script access to TPS Faceplate properties and method ................................................................... 220
9.5.5 Faceplate sysDtlTPS_fp.htm ........................................................................................................... 221
9.5.6 Invoking the faceplate - popup display ............................................................................................ 221
9.5.7 Invoking the TPS faceplate through scripting ................................................................................. 222
9.6 Accessing Actors ............................................................................................................................................ 223
9.6.1 About Actors .................................................................................................................................... 223
9.6.2 Purpose of Actors in TPS/LCN ....................................................................................................... 223

6 www.honeywell.com
CONTENTS

9.6.3 SCHEM actor for display invocation .............................................................................................. 223


9.6.4 KEYLEVEL actors .......................................................................................................................... 223
9.6.5 Experion Standard displays - no access through Actors .................................................................. 223
9.7 Accessing Actors from HMIWeb script using TPS Commands ..................................................................... 224
9.7.1 About TPS Commands .................................................................................................................... 224
9.7.2 Installation of TPS Commands ........................................................................................................ 224
9.7.3 InvokeDisplay method ..................................................................................................................... 224
9.7.4 TPS Command Properties ................................................................................................................ 225
9.7.5 TPS Command Error messages ....................................................................................................... 225
9.7.6 TPS/LCN standard display invocation using display name ............................................................ 225
9.8 Script Examples for Invoking Displays .......................................................................................................... 227
9.8.1 Invoking TPS Schematic from HMIWeb Display ........................................................................... 227
9.8.2 Invoking TPS/LCN Point Detail from HMIWeb Display ............................................................... 227
9.8.3 Invoking TPS/LCN System Status Display from HMIWeb Display ............................................... 227
9.8.4 Obtaining PSDP data in HMIWeb Display ...................................................................................... 227
9.9 Automatic priming of TPS points on Experion .............................................................................................. 228
9.9.1 What is autopriming? ....................................................................................................................... 228
9.9.2 Off-line development LCN used with simulator nodes to build and test displays .......................... 228
9.9.3 Features of autopriming ................................................................................................................... 228
9.9.4 Need for local priming ..................................................................................................................... 229
9.9.5 Parameter Conversion Timeout ....................................................................................................... 230
9.9.6 ESVT node is down ......................................................................................................................... 230
10 GUS Functionality on ES-T .............................................................................................................. 231
10.1 GUS Functionality Summary ....................................................................................................................... 232
10.1.1 Operating System Support ............................................................................................................. 232
10.1.2 GUS Display Builder ..................................................................................................................... 232
10.1.3 GUS Display Runtime ................................................................................................................... 232
10.1.4 GUS Remote Displays ................................................................................................................... 233
10.1.5 Cross-Environment Display Invocation ........................................................................................ 233
10.1.6 GUS HCI Client ............................................................................................................................. 233
10.1.7 Local TPN Server .......................................................................................................................... 233
10.2 Handling F1-F17 keys when GUS application is in focus ........................................................................... 234
10.2.1 Function key behavior ................................................................................................................... 234
11 Managing Operations, Alarms, and Events ................................................................................... 237
11.1 Managing Scope of Responsibility ............................................................................................................... 238
11.1.1 About Enterprise Model ................................................................................................................. 238
11.1.2 Use Enterprise Model Builder to create Assets ............................................................................. 238
11.1.3 Unit to Experion Asset relationship ............................................................................................... 239
11.1.4 Assignment of assets ...................................................................................................................... 241
11.1.5 Mapping of TPS/LCN Units to Experion Assets ........................................................................... 242
11.1.6 Mapping when more than one LCN is connected to Experion using DSA ................................... 242
11.1.7 Enabling alarming for Experion Assets with mapped TPS Units .................................................. 243
11.1.8 TPS/LCN Area Change ................................................................................................................. 244
11.1.9 Super area ....................................................................................................................................... 245
11.1.10 KEYLEVEL.KL File Access Overview ...................................................................................... 245
11.1.11 HMIWeb display stores ................................................................................................................ 245
11.1.12 TPN Server Auxiliary Display indicator ...................................................................................... 246
11.1.13 Refresh the KEYLEVEL.KL file from the TPN Server Auxiliary Display ................................ 247
11.2 Managing Process Alarms ............................................................................................................................ 248
11.2.1 Experion Alarm Summary Displays .............................................................................................. 248
11.2.2 Enable/Disable/Inhibit ................................................................................................................... 248
11.2.3 Enable/Disable audible alarm suppression .................................................................................... 249
11.2.4 Correctly manage disabled alarms on ESVT ................................................................................. 249

7
CONTENTS

11.2.5 Alarm presentation ......................................................................................................................... 250


11.2.6 Changing Alarm Priority to NOACTION or PRINTER ............................................................... 251
11.2.7 Changing the values of ALMFMT and DIGALFMT parameters ................................................. 252
11.2.8 Deleting points that are in alarm .................................................................................................... 252
11.2.9 Stuck alarms on ESVT ................................................................................................................... 252
11.2.10 Managing sequence program (PROCMOD) alarms .................................................................... 252
11.2.11 Disabling PROCMOD (sequence) point alarms .......................................................................... 253
11.2.12 Using SOE points ......................................................................................................................... 254
11.2.13 Alarm Shelving ............................................................................................................................ 254
11.3 Managing Operator Messages ...................................................................................................................... 255
11.3.1 Clear messages ............................................................................................................................... 255
11.3.2 Informational (non-confirmable) messages ................................................................................... 255
11.3.3 Confirmable message behavior ...................................................................................................... 259
11.3.4 Clear message before acknowledging ............................................................................................ 262
11.3.5 Recovery of TPS Messages that are not cleared yet ...................................................................... 262
11.3.6 Message list overflow .................................................................................................................... 262
11.4 Managing System Alarms ............................................................................................................................. 264
11.4.1 TPS System and Console Status Indicators ................................................................................... 264
11.4.2 TPN system Alarm Functionality .................................................................................................. 266
11.4.3 Alarm annunciation on node status change ................................................................................... 266
11.4.4 System Status LED behavior of TPN versus Experion ................................................................. 266
11.4.5 No ACK Integration between TPN and Experion ......................................................................... 267
11.4.6 System Status LED behavior of TPN versus Experion ................................................................. 267
11.4.7 Combined Experion/TPN System Alarm LED Behavior .............................................................. 268
11.4.8 No ACK Integration between TPN and Experion ......................................................................... 268
11.5 TPN Console Acknowledgement .................................................................................................................. 269
11.5.1 Experion Configuration ................................................................................................................. 269
11.5.2 LCN Configuration ........................................................................................................................ 269
11.6 Process History and Event Storage ............................................................................................................... 270
11.6.1 Event database ............................................................................................................................... 270
11.6.2 Operator events .............................................................................................................................. 270
11.6.3 Viewing process history ................................................................................................................. 270
11.7 Importing TPN History Configuration ......................................................................................................... 271
11.7.1 Example of imported history display ............................................................................................. 271
11.7.2 Changing history rates before export ............................................................................................. 271
11.7.3 History import requirements and recommendations ...................................................................... 271
11.7.4 Import History configuration ......................................................................................................... 272
11.7.5 Using comma separated files (.csv) with history data ................................................................... 275
11.7.6 Example file results ........................................................................................................................ 276
11.7.7 Export History configuration ......................................................................................................... 276
11.8 ES-T Keyboard Behavior .............................................................................................................................. 279
11.8.1 IKB and OEP hot keys ................................................................................................................... 279
11.8.2 LED annunciation .......................................................................................................................... 280
11.8.3 Focus-dependent (context specific) keys ....................................................................................... 281
11.8.4 IKB Keyswitch .............................................................................................................................. 281
11.9 Implementing Remote Native Window ........................................................................................................ 283
11.9.1 Operations ...................................................................................................................................... 283
11.10 Remote TPN Operations using Flex and DSA-connected Stations ............................................................ 284
11.10.1 Flex Station and remote operation functionality using DSA ....................................................... 284
12 Administering Experion-TPS Nodes ............................................................................................... 285
12.1 Managing Experion-TPS Security ................................................................................................................ 286
12.1.1 High Security Policy model ........................................................................................................... 286
12.1.2 Signon Manager ............................................................................................................................. 287
12.1.3 Station/Operator ............................................................................................................................. 288

8 www.honeywell.com
CONTENTS

12.1.4 About Station time-outs ................................................................................................................. 288


12.1.5 Station time-outs and Signon Manager .......................................................................................... 288
12.1.6 Signon Manager Settings in Configuration Utility ........................................................................ 289
12.1.7 Invoking the Signon Manager ....................................................................................................... 289
12.2 Password Security and Synchronization ....................................................................................................... 290
12.2.1 Secure passwords ........................................................................................................................... 290
12.2.2 Windows Services & DCOM Servers Log-on tool ........................................................................ 290
12.3 Supporting System and Network Availability .............................................................................................. 292
12.3.1 About Redundant Servers .............................................................................................................. 292
12.3.2 About Fault Tolerant Ethernet ....................................................................................................... 292
12.3.3 About Redirection Manager .......................................................................................................... 292
12.3.4 About System Event Server ........................................................................................................... 292
12.3.5 About System Performance Server ................................................................................................ 293
12.4 Distributed System Architecture ................................................................................................................... 294
12.5 Configuring an ES-T Station for Native-Window-Only Operation .............................................................. 295
12.5.1 Configuring for Native-Window-Only Operation ......................................................................... 295
12.5.2 Returning a Native-Window-Only Station to the Experion Environment ..................................... 296
13 Integrating TPS using only Server .................................................................................................. 297
13.1 Managing an integrated system .................................................................................................................... 298
13.1.1 Managing TPS points in an integrated system .............................................................................. 298
13.2 Managing TPS alarms and events ................................................................................................................. 299
13.2.1 Mapping TPS units ........................................................................................................................ 300
13.2.2 Change of alarm priorities ............................................................................................................. 300
14 Managing TPS points ....................................................................................................................... 303
14.1 Integrating TPS points into Experion ........................................................................................................... 304
14.2 Configuring history collection for TPS points .............................................................................................. 305
14.3 Configuring history offsets ........................................................................................................................... 308
14.4 Adding a TPS point to a trend ...................................................................................................................... 310
14.5 Adding a TPS point to a group ..................................................................................................................... 311
14.6 Including TPS point data in custom displays ............................................................................................... 312
14.7 Writing scripts for TPS points ...................................................................................................................... 313
14.8 Security level changes in HMIWeb graphics ................................................................................................ 314
14.8.1 Scenarios ........................................................................................................................................ 315
14.9 Referencing LCN Boolean parameters as enumerations .............................................................................. 316
14.10 HMIWeb Display Script Device Read ........................................................................................................ 317
14.11 Attaching algorithms toTPS points ............................................................................................................. 318
14.12 Deleting, Moving or Cutting over TPS points to CDA .............................................................................. 319
14.12.1 Backing up the TPS point configuration in Experion .................................................................. 319
14.12.2 Restoring TPS point configurations in Experion ......................................................................... 321
14.12.3 Permanently deleting TPS points ................................................................................................. 322
14.12.4 Removing deleted TPS point references in Experion .................................................................. 324
14.12.5 Finding and removing deleted TPS points from Experion .......................................................... 324
14.12.6 Moving TPS points within the LCN ............................................................................................ 325
14.12.7 Moving a TPS unit to a different Experion cluster ...................................................................... 328
14.13 Peer to Peer Communication between CEE and TPS Points ...................................................................... 329
15 Troubleshooting Experion-TPS nodes ........................................................................................... 331
15.1 Troubleshooting Approach ........................................................................................................................... 332
15.1.1 Troubleshooting displays ............................................................................................................... 332
15.2 Station and Server do not provide TPN data to Experion displays .............................................................. 337
15.3 TPS faceplate cannot get data, Native Window schematic access from Experion fails ............................... 339
15.4 Cannot change TPN data from Experion or TPN Server will not write to TPN .......................................... 340
15.5 HMIWeb display shows TPS/LCN data as "-----" ........................................................................................ 341
15.6 HMIWeb display shows TPS/LCN data as "?????" ...................................................................................... 342

9
CONTENTS

15.7 Slow display or faceplate call up with TPS data .......................................................................................... 343
15.8 TPN Server will not start .............................................................................................................................. 344
15.9 TPN Server in Warning state ........................................................................................................................ 345
15.10 Experion-TPS Node has Native Window WARNING Status .................................................................... 347
15.11 TPS System Alarm indication out of synch ................................................................................................ 349
15.12 ES-T appears as GUS in Native Window ................................................................................................... 350
15.13 ES-T appears as UNVL in Native Window ................................................................................................ 351
15.14 ESVT appears as APP in Native Window .................................................................................................. 352
15.15 ESVT appears as AM in Native Window ................................................................................................... 353
15.16 ES-T or ESVT node will not load its personality ....................................................................................... 354
15.17 ES-T or ESVT TDC Emulators Service has been shutdown ...................................................................... 356
15.18 Verifying TPS/LCN Installation and Version ............................................................................................. 357
15.18.1 Verification of Load Module installation: CBREV Schematic .................................................... 357
15.18.2 Verification of TPS/LCN release ................................................................................................. 357
15.18.3 Verification of TPS/LCN personality files on local drive ........................................................... 358
15.19 Verifying Configuration of Board 0 Data Access Configuration and TPN Server Channels ..................... 359
15.20 Getting duplicate TPS alarms ..................................................................................................................... 362
15.21 Getting an “Error Synching Tags from [RemoteServer]” alarm ................................................................ 363
15.22 System event journaling and silence synchronization not working ............................................................ 364
15.23 Multiple TPN System Alarms .................................................................................................................... 365
15.24 Cannot access data or receive alarms from a TPS point ............................................................................. 366
15.25 Data from a TPS point owned by another Experion cluster is still accessible from the local cluster
even though the remote cluster is unavailable ................................................................................................. 367
15.26 Cannot call up the TPS points that are moved after adding an ESVT to the same TPN ............................ 368
15.27 Unable to write to TPS points using an OPC client connected to the ESVT OPC server .......................... 369
15.28 Cannot access data or alarms from TPS points over DSA ......................................................................... 370
15.29 Annunciator is activated for a few seconds when a TPS alarm that has been shelved goes back into
alarm ................................................................................................................................................................ 371
15.30 Annunciator is silenced without operator interaction ................................................................................. 372
15.31 'S' and 'C' indicators don't appear in the Station status bar on an ES-T ...................................................... 373
15.32 There are blank boxes where the 'S' and 'C' indicators should be on the Station status bar ....................... 374
15.33 'S' and 'C' indicators in Experion Station don't match the 'S' and 'C' indicators in Native Window ........... 375
15.34 CEE-TPS peer-to-peer points are not getting historized after adding them in server history table in
Control Builder ................................................................................................................................................ 376
15.35 CDA display call up is slow on a flex station ............................................................................................. 377
15.36 Standard history not collected for an EHPM .............................................................................................. 378
15.37 Cannot build C200/C300 CDA points even though the TPS point with the same name is deleted from
the LCN ........................................................................................................................................................... 379
16 TPS PRIMMOD and Experion Aggregate Alarming ....................................................................... 381
16.1 About aggregate alarming ............................................................................................................................. 382
16.2 Importing TPS PRIMMOD groups .............................................................................................................. 383
16.2.1 Prerequisite for importing .............................................................................................................. 383
17 Appendix ........................................................................................................................................... 385
17.1 Processing custom defined IKB OEP keys on an ES-T ............................................................................... 386
17.1.1 System Registry key assignments .................................................................................................. 386
17.2 ACE-T Guidelines ........................................................................................................................................ 388
17.2.1 ACE-T capacity and performance ................................................................................................. 388
17.2.2 ACE-T configuration options ........................................................................................................ 388
17.2.3 ACE-T control processing ............................................................................................................. 389
17.2.4 ACE-T TPN server group writes ................................................................................................... 390
17.2.5 Detailed ACE-T Control Strategy Phasing Guidelines ................................................................. 391
17.2.6 TPN server data access transactions .............................................................................................. 394
17.3 Dspprime description and syntax .................................................................................................................. 396
17.3.1 Syntax ............................................................................................................................................ 396

10 www.honeywell.com
CONTENTS

17.3.2 Dspprime argument description ..................................................................................................... 396


17.4 TPN interface channels ................................................................................................................................. 399
18 Notices .............................................................................................................................................. 401
18.1 Documentation feedback .............................................................................................................................. 402
18.2 How to report a security vulnerability .......................................................................................................... 403
18.3 Support and other contacts ............................................................................................................................ 404
18.4 Training classes ............................................................................................................................................. 407

11
CONTENTS

12 www.honeywell.com
1 About This Document

This guide describes supplementary installation tasks that must be done before you use T-Nodes on an Experion
system. It also describes configuration tasks necessary for T-Nodes.

Revision history

Revision Date Description


A December 2013 Starting with Experion R430, this document’s title has been
changed from Integrated Experion TPS Nodes (ES-T, ESVT,
ACE-T) User's Guide to Integrated Experion-TPS User’s
Guide since the Enhanced Universal Control Network (EUCN)
nodes, Enhanced High-Performance Process Manager (EHPM)
and Enhanced Network Interface Module (ENIM) can now be
integrated with the Experion network.
Peer-to-peer communication between the ACE/C300
Controller and the EHPM Controller is supported from this
release onwards. As part of the EUCN nodes integration with
Experion, some sections have been updated like, “Overview of
Experion and TPS Nodes”, “Integrate Experion Control” and
so on.

13
1 ABOUT THIS DOCUMENT

14 www.honeywell.com
2 References

The following list identifies all documents that may be sources of reference for material discussed in this
publication.

Document Title Doc ID


Software Installation User's Guide EPDOC-X136-en-4301A
System Administration Guide EPDOC-X139-en-430A
HMIWeb Display Building Guide EPDOC-XX54-en-430A
Server and Client Configuration Guide EPDOC-X127-en-430A
Operator's Guide EPDOC-XX80-en-430A
Application Control Environment User Guide EPDOC-XXX4-en-430A
System Management Operations Guide EPDOC-X142-en-430A
System Management Configuration Guide EPDOC-X141-en-430A
Fault Tolerant Ethernet Status Server and Auxiliary Display User's EPDOC-XX38-en-430A
Guide
Fault Tolerant Ethernet Installation and Service Guide EPDOC-XX36-en-430A
Native Window User's Guide EPDOC-XX74-en-430A
SafeView User's Guide EPDOC-X120-en-430A
TPN Server User's Guide EPDOC-X143-en-430A
Configuration Utility User's Guide EPDOC-XX14-en-430A

15
2 REFERENCES

16 www.honeywell.com
3 Overview of Experion and TPS Nodes

17
3 OVERVIEW OF EXPERION AND TPS NODES

3.1 Introduction to Experion and TPS Integration


The Experion Process Knowledge System (PKS) platform offers a replacement for Global User Station (GUS)
and Universal Station (US) functionality through the use of the Experion Station-TPN and Experion Server-
TPS. Because the nodes connect directly to the Local Control Network (LCN), also known as the TotalPlant
Solution (TPS), virtually all data, events, and operator messages previously presented on the GUS or US are
incorporated into the Experion Station-TPS.
Starting with Experion R430, the Enhanced High-Performance Process Manager (EHPM) and the Enhanced
Network Interface Module (ENIM) nodes are integrated in the Experion network. EHPM and ENIM are the
existing HPM and NIM nodes which have been enhanced to communicate over FTE. Peer-to-peer
communication between the EHPM Controller and the ACE/C300 controllers is supported from this release
onwards, the ACE/C300 initiates peer-to-peer communication and the EHPM acts as the responder.
For detailed description of TPN/TPS nodes, refer to applicable TPN/TPS documents.

3.1.1 Intended audience


This guide is intended for the following users:
System engineers, those who have to configure the integrated Experion and TPS nodes.
Operations personnel, those who need an introduction to the integrated Experion and TPS nodes.

3.1.2 Assumptions
This guide assumes that your support team is familiar with the following:
Configuring and operating a TPS/LCN system
Navigating and operating Windows applications
Interpreting basic network concepts, terms, and components
Throughout this document there are procedures that require special attention or else the system may not perform
as intended. Procedures indicated with the following icon are most likely to be missed and need to be verified.

Attention
For detailed descriptions of Experion nodes, refer to applicable Experion documentation, and Online Help available on
each Experion node.

3.1.3 System Topology


The following figure illustrates a simple architecture using integrated Experion-TPS (ES-T and ESVT) nodes.
The Plant Information Network can be implemented as a Fault Tolerant Ethernet network. Starting with
Experion R430, the EHPM controller can communicate with both ACE and C300 Controller.

18 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.1.4 Enhanced Universal Control Network (EUCN)


The EUCN is an FTE-based, dual communications network based on the ISO open system communication
standards. It introduces the ENIM and the EHPM, wherein the traditional co-axial cable system is replaced by
the FTE.
For detailed description of EUCN nodes, refer to applicable TPN/TPS documents.

Related topics
“EHPM” on page 19
“ENIM” on page 20

3.1.4.1 EHPM
The EHPM is an FTE-based controller that contains a set of algorithms and tools for implementing integrated
control strategies. The EHPM is the HPM node that has been enhanced to support connectivity to the Experion
ACE/C300 through FTE.

19
3 OVERVIEW OF EXPERION AND TPS NODES

3.1.4.2 ENIM
The ENIM is an FTE-based node that provides the interface between the LCN and the EUCN. The ENIM is the
NIM node that has been enhanced to support connectivity to the EHPM.

3.1.5 Experion Station-TPS (ES-T)


The Experion Station-TPS (ES-T) node provides the same operations environment as other types of Experion
Stations. Experion Stations have the ability to use Honeywell's HMIWeb technology for custom graphics and
presentation of alarms, events, and messages. HMIWeb technology uses HTML as the native display format,
allowing process, application, and business data to be integrated.
In addition, the ES-T provides the Native Window application that emulates a Universal Station and optionally
supports GUS displays. The Native Window and GUS runtime connect to a locally installed LCNP (LCN
processor) board, providing a user interface with access to all TPS/LCN operations, engineering, and
maintenance functions. Additionally, the GUS display environment is also available for an ES-T.

20 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.1.6 Experion Server-TPS (ESVT)


An Experion-TPS Server (ESVT) node supports the same real-time database and subsystems as the Experion
Server. The ESVT has a locally-installed LCNP board for accessing the TPS/LCN. The ESVT provides support
for initial Experion configuration and also supports functions such as history collection, archiving, and
reporting.

3.1.7 Experion Stations


Several types of Experion Stations are available to satisfy a range of needs; they include Experion Station-Flex,
Experion Station-Console and Experion Station-Console Extension, and Experion Station - TPS (ES-T).
Experion Station-Console (ES-C) communicates directly to a control execution environment supporting devices
such as the Experion controller. An Experion Station-TPS requires an FTE connection to Experion controllers.
Experion Station-TPS supports both Experion control execution environments and TPS/LCN control
environments.
For each ES-T, you can connect up to three Experion-TPS Console Stations Extensions. Console Station
Extensions connect to an ES-T in the same way that a Flex Station connects to an Experion server. Extension
stations then provide support for Remote GUS Displays and Remote Native Window options.
Experion Station-Flex (ES-F) can use a client-server relationship with an ESVT to present process data to the
user. An ES-F can be applied anywhere (including internet, wireless, and dial-up connections), as long as it has
a connection to the Experion Server. The ES-F could be used on the plant floor, in satellite control rooms, and in
the engineering and maintenance offices.
All Experion Station types provide the Station application as an operator interface and share the available
feature set for consistent operation. Custom displays, trends, and other operations displays are configured once
and available across the various types of Experion Stations. The ES-T also provides the Native Window as a
familiar interface for previous users of the GUS or US.

3.1.8 Experion Servers


Multiple Experion Servers can reside in an Experion system and provide the following:
Servers can be either Experion Servers (that is, connected to an Experion system) or ESVTs (that is, connected
to an Experion system and LCN system).
Cluster Server is the term used for both Experion Server and ESVT, since both of these servers manage an
Experion cluster of nodes and contain configuration information as well as the Real-time Database for their
local Experion cluster of nodes.
Experion Servers have an optional redundancy subsystem designed to fail over to a backup server in the event
of a failure of the primary or controlling server.

3.1.9 Console functionality


Experion supports console functionality through deployment of Experion Console Stations and Experion-TPS
Console Stations Extensions. ES-T is a member of a LCN console. The ES-T members of an LCN console can
optionally be configured as members of an Experion console. ES-Ts are members of both Experion and LCN
consoles. Experion Stations with Console Extensions (ES-CE) that are clients of a host ES-T become members
of the same Experion console as the host ES-T. The following figure illustrates the console concepts.

21
3 OVERVIEW OF EXPERION AND TPS NODES

Attention
Each ES-T node must belong to one Experion Console and that Experion Console and TPN Console must have a one-
to-one relationship. In other words, a TPN Console must not span across multiple Experion Consoles or across
multiple Experion clusters.

3.1.10 Application Control Environment (ACE-T)


The Application Control Environment (ACE-T) node provides the same Experion integrated application
environment as the ACE including control modules, function blocks, RCMs, SCMs and CABs. In addition, the
ACE-T provides an interface to TPN via the TPNServer. This can either be local with an on node LCNP4 or
remote with a connection to a TPNServer in an APP node. The TPN interface includes secondary controller
cascade connections to using the UCNOUT and HIWAYOUT function blocks.

3.1.11 Experion Application Processing Platform (Experion APP)


The Experion Application Processing Platform is the Experion system's advanced applications platform. The
APP combines the security and integrity needed for advanced process control and optimization. The APP can
run complex applications developed by Honeywell, by users, and by third-party suppliers. Integrating process
and business data, the APP uses industry-standard technologies, such as the Microsoft Windows Server 2008 R2
Standard operating system, and communication interfaces, such as DCOM, OLE, and OPC.

Attention
Experion APP does not require the presence of the Experion Server (ESVT).

3.1.12 Control Integration


Both ES-T and ESVT can directly connect to Experion controllers as well as support the ACE-T. The Experion
controllers require FTE connections.
Starting with Experion R430, connection between ACE/C300 Controllers and EUCN nodes is supported.

22 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.1.13 System data flow


In a plant-wide system, data is typically shared between servers over a high-bandwidth network, such as a 100
Mbps or higher Ethernet. In this case, each server is assumed to be responsible for controlling a different part of
the plant. Typically, there are multiple control rooms, or multiple stations in the same control room, each
associated with a specific server. The following diagram illustrates the data flow for ES-T and ESVT. LCN
(TPS) alarms and events are published to the ES-T and ESVT nodes. The ES-T and ESVT nodes have a
TPS/LCN alarm list that collects the TPS/LCN alarms and events. They receive the TPS/LCN data directly from
their local TPS (LCNP) connection.

23
3 OVERVIEW OF EXPERION AND TPS NODES

The Distributed System Architecture (DSA) option enables multiple Experion servers to share data, alarms,
messages, and history without the need for duplicate configuration on any server. Specific configuration
procedures are required to set up DSA. Point information brought into the Experion servers by way of DSA is
then shared with the Experion stations. An ES-T accesses DSA and SCADA information through its Cluster
Server (including information through DSA communications between two ESVTs. For more information about
using Flex Stations and DSA, refer to the Remote TPN Operations using Flex Stations.
Starting with Experion R430, EHPM and ENIM are part of the Experion network. ACE node and C300
Controller, that belong to the same ESVT cluster, can communicate with the EHPM through the Control Data
Access (CDA). The CDA is the Experion system communication infrastructure and data access interface
schema that provides application integration with Experion system objects.
Starting with Experion R430, the EHPM points that are imported into ERDB can be optionally downloaded to
Experion Server so that the standard history can be collected through CDA.

24 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.2 Multiple Experion clusters on one TPS (LCN)


With Experion R400 and later, you can configure multiple Experion clusters on one TPS (LCN).
The following figure illustrates a typical topology for multiple Experion clusters on one TPS.

There can be a maximum of 5 Experion clusters connected to on TPS.

25
3 OVERVIEW OF EXPERION AND TPS NODES

3.3 Architectural Overview


This section provides a functional overview of the ES-T and ESVT. Having an understanding of the node
architecture assists in the performance of implementation and operation tasks.

3.3.1 ES-T Architecture


In addition to Console Station functions, the ES-T includes:
Console Station Services: This software supports standard summaries, trends, reports, and HMIWeb displays.
It directly connects to the TPN Server to access TPS/LCN data. Note: Reports are a function of the ES-T and
can be generated and viewed on an ES-T only when it is connected and synched with its ESVT.
TPN Server: This private OPC server obtains TPS/LCN data, alarms, and events directly through the local
LCNP, and builds a data cache to serve data to its clients. The TPN Server is automatically linked to the
Experion platform layer on the ES-T, where the node maintains the Experion data cache and alarm list.
LCNP: This hardware board provides a connection to the TPS/LCN. When the board is loaded with the
TPS/LCN personality, it provides the full functionality of a Universal Station, viewable through the Native
Window. The LCNP board provides TPS/LCN data, process alarms, events, and support for the Native Window,
TPN Server, and TPS Faceplates and GUS displays that service TPS/LCN data points.

3.3.2 ESVT Architecture


In addition to the Experion Server functionality (archiving, journaling, reporting, server redundancy, and
SCADA facilities to communicate with controllers and remote terminal units), the primary components of an
ESVT include the following:
TPN Server: This private OPC server obtains TPS/LCN data, alarms, and events directly through the local
LCNP, and builds a data cache to serve data to its clients. The TPN Server on the ESVT node is automatically
linked to the Experion Server layer, where the node maintains the Experion data cache and alarm list.
LCNP: This hardware and software component provides a connection to the TPS/LCN. When an ESVT is
loaded with the LCNP personality, it acts as a specialized Application Processing Platform (APP).

26 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

Attention
Honeywell has not qualified nor recommends that the user build Application Module (AM) points on the ESVT. The
ESVT is dedicated to other Experion PKS platform functions such as event journaling of the TPS/LCN.

27
3 OVERVIEW OF EXPERION AND TPS NODES

3.4 Enterprise Model and TPN


The Enterprise Model Builder is the application used to build, edit and download an Enterprise Model in
Experion. The enterprise model provides a means of organizing the core operational environment around a
hierarchical asset model; typically configured to represent the physical assets of the plant or mill. The Enterprise
Model is fully integrated with the TPN. TPN Units and the points that they contain are associated with
Enterprise Model's Assets in a similar way that they were previously associated with Experion Areas.

Tip
In the Enterprise Model example, A1, A2, B1, and C1 are TPN Units while Mixer, Reactor A, Tank B, and Tank C
are levels added by the Enterprise Model Builder to organize the TPN Units into logical groupings.

3.4.1 Enterprise Model Builder in Configuration Studio


Enterprise Model Builder is a standard tool in the Configuration Studio. The Enterprise Model Builder stores
your user-configured assets in the Enterprise Model Database (EMDB). The EMDB resides on an Experion
Server node. For TPS systems this can be the ESVT.

28 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

Tip
For more information about the Enterprise Model, refer to the “Enterprise Model Builder” section in the Enterprise
Model Builder User's Guide.

29
3 OVERVIEW OF EXPERION AND TPS NODES

3.5 Implementation Overview


This section provides an overview of the implementation approach and the resources you can refer to during
configuration.

3.5.1 Implementation flowchart


Using checklists from this document that identify the resources you need, in general your implementation
begins with the following tasks:
Install and configure the Experion Server, Console Station, and TPS/LCN. Refer to the Software Installation
and Upgrade Guide for the necessary steps.
Configure the TPS/LCN. Refer to this guide for the necessary steps.
Perform the site-specific tasks, as needed to fully implement the Experion nodes in support of plant operations.
Refer to this guide for an overview of several key tasks. For detailed information, refer to applicable Experion
documentation and the Help available on each Experion node.

30 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.6 Implementation Environment


This section provides an overview of your implementation environment when deploying Integrated Experion-
TPS nodes. The environment includes the following:
Experion and TPS engineering tools
System management
Operating system
Security management
Hardware and furniture

3.6.1 Experion engineering tools


Experion engineering tools are available from Configuration Studio.

3.6.2 TPS/LCN engineering tools


TPS/LCN engineering tools are available from the Native Window of an ES-T.

31
3 OVERVIEW OF EXPERION AND TPS NODES

3.6.3 TPS engineering tools


TPS engineering tools are available from the TPS program group under
Programs > Honeywell Experion PKS > TPS Applications as shown below.

3.6.4 Network tree


You can configure a Network tree so that you can view a network item's status and health from the System
Status Display. From the network tree in the System Status display, you can then access performance and
configuration detail displays for the network tree items that display performance and configuration data. For
more information about how to configure the Network tree to appear in the Experion displays, refer to the
Server and Client Configuration Guide.

32 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.6.5 System Management Display


The System Management Display provides a hierarchical view of the Windows domains, the computers in TPS
domain organizational units, and the status of HCI (Honeywell Communication Interface) components residing
in those computers. The display appears within a Microsoft Management Console (MMC).

3.6.6 Operating System


The ES-T runs on the Microsoft Windows 7 Professional operating system. The ESVT and ACE-T run on
Microsoft Windows Server 2008.

3.6.7 System security


The ES-T and ESVT support operator-based security. Station-based security is not supported on an ES-T. ES-T
starts with the credentials of the current Windows account. The equivalent operator definition must exist in
Experion. Windows authenticates the user logging on to the computer against the Windows user account. The
Experion server then controls authorization by using security levels and assets. Operators use an application
called “Signon Manager” to sign on and off without having to log off of the computer, which would cause loss
of view of the process.

Attention
The operator-based security account must be linked to a Windows account or group.

3.6.8 PC station furniture


The furniture styles shown may be used to support the ES-T.

33
3 OVERVIEW OF EXPERION AND TPS NODES

34 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.7 Viewing the Process


With an ES-T, you have the following facilities for viewing the process:
• HMIWeb displays
• SafeView window management
• Experion Station application displays
• Native Window (TPS/LCN) displays
• HMIWeb Detail Displays and Faceplates for TPN
• Standard GUS Runtime Displays

3.7.1 HMIWeb displays


The HMIWeb Display Builder is a tool for building custom graphical displays using web-based features in
HTML. Additionally, Experion supports TPN with its HMIWeb Detail displays for TPN points and HMIWeb
Faceplates for TPN point.

3.7.2 SafeView application


The SafeView application enables you to create well-organized groupings of multiple windows. It also
coordinates the placement of windows across applications. SafeView helps ensure that the placement of critical
operating displays is predictable and that they are never obstructed by other displays or applications. SafeView's
multi-window support provides the capability to view and manage multiple Station windows, a Native Window,
and other Honeywell or third-party displays. The following figure illustrates a sample SafeView application
window.

35
3 OVERVIEW OF EXPERION AND TPS NODES

With Experion R400, a Fast button is available in the title bar of the managed windows. The Fast mode button
allows you to request a window and/or a display to be in fast mode. This directs the window/display to update
the data at a preconfigured fast rate. The Fast mode button is applicable for the following displays.
GUS displays
Native Window
Station displays
At a given point in time, only one display can be in fast mode.
For more information about the Fast button, refer to the SafeView Users Guide.
Operators can also use the standard IKB/OEP Fast key or any Station-configured key to request the data to be
updated at a pre-configured fast rate for a single display. The IKB/OEP Fast key has an LED indicating if the
display is updating at a fast rate.

3.7.3 Experion standard displays


The Station application is the user interface to the Experion platform and includes setup and configuration
displays, as well as displays that operators can use for monitoring and controlling plant processes. The
following types of Experion displays, and others, are viewable through the Station application: Message
Summary, Trend displays, Alarm Summary, Group, and Detail.
Experion Group displays support TPS/LCN points. The same Group and Detail displays that were available on
the Universal Station for TPS/LCN points are available through the Native Window. Native Window displays
(such as Groups 1-450) can be invoked from HMIWeb displays or directly accessed through the Native
Window. Additionally, TPN points can be added to Experion Group displays. The following figure shows
examples of several Experion displays that are viewable through the Station application.

36 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.7.4 Native Window Displays


Native Window displays can be invoked only on the Station that currently has possession of the Native Window.
Attempts to invoke Native Window displays will fail on other stations. This also applies to TPN Detail Displays
and Native Window Group Displays. Unlike the ES-T, it is not possible for GUS or HMIWeb displays to invoke
Native Window displays, and vice versa. (This behavior is the same as Remote GUS.)

3.7.5 HMIWeb Faceplates for TPN points


The HMIWeb-based faceplate displays support the TPN's AM, NIM, HG point types. The HMIWeb-based
faceplate provides a replacement for the classic TPN faceplate which is also supported in Experion.

37
3 OVERVIEW OF EXPERION AND TPS NODES

3.7.6 HMIWeb Detail displays for TPN points


Experion provides a set of native HMIWeb displays that access an extended set of standard operational
parameters associated with a given TPN point. The displays provide access to TPN operational parameters.
With Experion R410, you can view and control all the parameters, using Experion TPN point detail displays as
you can with the Native Window point detail displays. While the Native Window display provides the data in a
series of separate pages, Experion station display provides the same data as a set of tabbed displays. The tabbed
displays framework of Experion Station window incorporates all the components that are supported in the
Native Window. The following figure is an example of Experion station display:

38 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

39
3 OVERVIEW OF EXPERION AND TPS NODES

3.8 Analyzing the Process

3.8.1 Reports
Experion reports provide a flexible way to get information from the Server database. The reports available as
part of Experion are pre-formatted reports such as Alarm and Event, Alarm Duration, and Batch. You can also
configure custom reports using Microsoft Excel and/or Free-format. After you have configured reports for your
site, operators and other users can request these reports. Reports can be printed or viewed on Experion Server
and Station displays, or saved in a file.

3.8.2 Historization
Trend displays are standard Station displays that provide a way of viewing historical data for points. Trend
displays complement other types of displays that can be used to view historical data such as point detail trends,
group trends, and custom display trends.

40 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.9 Desktop Familiarization


This section identifies the desktop applications available at an ES-T or ESVT by program grouping.

3.9.1 Program groups


After selecting the Honeywell Experion PKS program group from the Start menu, users can access the
following program groups.
For ESVT:

For ES-T:

3.9.2 Console Station program group


The following figure shows these Console Station applications:
HMIWeb Display Builder is used to build displays that support your process. Typically, displays are built and
saved on the Server and then replicated to Stations. You can build displays on the Station, but then you need to
save the displays to the Server to ensure that they are made available to each Station.
Station provides the primary interface for interacting with the system.
References for using Console Station applications include:
• HMIWeb Display Building Guide
• Server and Client Configuration Guide

41
3 OVERVIEW OF EXPERION AND TPS NODES

• Operator's Guide

3.9.3 System Management program group


The following figure shows several System Management applications:
Configuration Utility is used to perform initial configuration
FTE Status Display is used to monitor Fault Tolerant Ethernet health
System Management Display is used to monitor node and HCI component status

42 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

References for using the System Management applications include:


• FTE Status Display and User Guide
• System Management Configuration Guide
• System Management Operations Guide
• Configuration Utility
• Node Definition Guide

3.9.4 TPS Applications program group


The following figure shows the Native Window, which you can use to access TPS/LCN functionality as if you
were at a Universal Station.

43
3 OVERVIEW OF EXPERION AND TPS NODES

You can also use the TPS Application Program group to launch GUS Display Builder.

44 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.9.5 SafeView program group


The following SafeView applications are available from the SafeView group.
SafeView Graphical Workspace Editor is used to configure workspaces
SafeView Text Editor is used to configure workspaces
SafeView is used to launch a configured workspace

References for using SafeView applications include:


• SafeView User's Guide
• HMIWeb Display Building Guide

45
3 OVERVIEW OF EXPERION AND TPS NODES

3.10 Monitoring Experion-TPS Nodes

3.10.1 Monitoring system alarms


Several system displays provide the Experion-TPS node status. Experion and TPS/LCN system alarms share the
SYST STATS key's LED. If a TPS/LCN system alarm is active then pressing the SYST STATS key will invoke
the TPS/LCN System Status display. If an Experion system alarm is active, then it invokes the Experion System
Alarm Summary display. If both the TPS/LCN system alarm and theExperion system alarm are active, then both
the TPS/LCN System Status display and the Experion System Alarm Summary display is invoked.
The Experion System Status Display is also accessed by clicking the System item on the Status bar.

Tip
The TPS System Alarms requires the SES component to be running on ESVT.

With Experion R410, the TPS/LCN system and console status indicators on the Native Window are also shown
in the Experion Station status bar when using an ES-T.

Attention
The TPN system alarm has been replaced with the TPS System Status and TPS Console Status indicators in the
Experion Station status bar. It is recommended to disable the TPN system alarm.

If you want to continue to use the TPN System alarm, then it is presented as an Experion system alarm when
using an ES-T. The following screen capture is only applicable if you are using the TPN System Alarms.

46 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

TPS/LCN system alarms are also indicated on the TPS/LCN Console Status and System Status displays, viewed
through the Native Window. You can invoke the Native Window status displays using the following methods:
Console Status display: Click the C button on the Native Window status bar (as illustrated in the following
figure), click the C button on the Experion Status status bar, or press the CONS STATS key when the LED has
been activated by a TPS/LCN system alarm.
System Status display: Click the S button on the Native Window status bar (as illustrated in the following
figure), click the S button on the Experion Status status bar, or press the SYST STATS key when the LED has
been activated by a TPS/LCN system alarm.

47
3 OVERVIEW OF EXPERION AND TPS NODES

If Experion is unable to read the S and C value, the ES-T will show blank boxes in the Station status bar where
the S and C would normally be.
Link from Experion System Status: Click the TPS System Status link as shown in the following figure. Note
that this is only applicable if you are using the TPN system alarm.

Attention
With Experion R410, the TPS System Status link is removed from the Experion System Status.

Attention
A consolidated TPS system alarm is provided to alert operators of a problem with a TPS system component. This
alarm is a consolidation of all outstanding TPS system alarms.
In certain cases when there is an outstanding TPS System alarm, it may re-alarm although there is no new fault. This
includes the reloading of an LCN node and when the LCN system alarm is being caused by multiple faults, and one of
the faults is acknowledged by a GUS or by a US.

3.10.2 Monitoring Experion Stations


Experion Station status can be viewed when you click the item from the status bar.

48 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.10.3 Monitoring System Interfaces


The ES-T and ESVT nodes require a TPS System Interface. The status of system interfaces deployed in your
system can be viewed thru the appropriate Station displays.
Clicking the link for a System Interface of interest invokes more detailed information about its status. In normal
operating conditions, the indicators should appear green with an OK or Running status.

3.10.4 Monitoring LCNP Status


The LCNP Status display provides status about the health of the local LCNP board. It provides information
previously available in physical TPS/LCN node LEDs and other alphanumeric board indicators.

For more information about the LCNP Status display, refer to the LCNP Status User's Guide.

3.10.5 Analysis Tools


Initial analysis can be performed on nodes using Experion's Analysis Tools. The Network Tree's Analysis Tools
are integrated into Configuration Studio and are available on any Experion node. For details, refer to the
Diagnostic Studio Users Guide.

49
3 OVERVIEW OF EXPERION AND TPS NODES

50 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

3.11 Documentation Reference Listing


This section provides a quick reference listing to Experion and TPN/TPS documents.

Attention
When referencing Experion user documentation, note the following:
• “Console Station” applies to both the ES-C and the ES-T.
• “Server” applies to all Experion Servers, including the ESVT.

3.11.1 References for common user tasks


Table 1: Experion documents

User Task Reference Comment


Understanding the Overview Provides Experion overview.
system
Experion TPS Integration Product Information Note
Getting started Getting Started with Experion Software Provides checklists to get started
with system functions.
“Prepare TPS/LCN for Integrated Experion-TPS Nodes” (this
guide)
Planning the Server and Client Planning Guide
system
Enterprise Model Builder User Guide
Installing Platform specific Planning, Installation and Service documents Provides platform installation
hardware procedures.
Installing software Getting Started with Experion Software, Use these manuals to first install
Experion software.
Software Installation User's Guide,
Supplementary Installation Tasks Guide
Configuring the Server and Client Configuration Guide, Use these manuals to configure
system Experion first using Configuration
System Management Configuration Guide,
Studio, then add TPS
TPN Server User's Guide configuration.
Configuring LCN book set Refer to LCN book set for control
control strategies configuration.
Experion book set Refer to Experion Control Builder
books for Experion controller
configuration.
Operating the Operator's Guide Refer to Operator's Guide for
control system Experion Station operations of the
alarm and message summaries.
Native Window User's Guide Refer to the Native Window User
Guide and TPS/LCN book set for
TPS/LCN operations.
(this guide) Refer to this guide for ES-T
keyboard behavior.
Historizing and Server and Client Configuration Guide Refer to the sections on trend
reporting displays and reports.
Managing the FTE Status Display and User Guide Supports Fault Tolerant Ethernet.
network
FTE Installation and Service Guide

51
3 OVERVIEW OF EXPERION AND TPS NODES

User Task Reference Comment


Authoring displays HMIWeb Display Building Guide Refer to the HMIWeb Display
Building Guide for building
custom displays.
SafeView User's Guide Refer to the SafeView User's
Guide for managing displays.
(this guide) Refer to this guide for interfacing
HMIWeb displays to the TPS/
LCN.
Note: Refer to GUS documentation such as the GUS Display Building Guide and GUS Display
Scripting User's Guide, to support GUS Displays.
Managing the Server and Client Configuration Guide, Refer to the guides for managing
system the Experion system and its
System Management Configuration Guide,
performance from the Network
System Management Operations Guide tree and/or System Management
Display.
Administering the System Administration Guide, Refer to these guides for TPS and
system Experion administration
Server and Client Configuration Guide
approaches, particularly when
establishing security.
Troubleshooting Server and Client Configuration Guide
the system
(this guide)
Starting and Server and Client Configuration Guide Refer to the appropriate sections
stopping the in these guides for system startup/
system shutdown procedures.

Table 2: TPN/TPS documents

User Task Reference Comment


Planning the UCN Planning (UN02501) Provides the necessary
system information required to plan a
UCN Guidelines (UN12610)
UCN or an EUCN.
Provides guidance to the user to
ensure the best performance of the
UCN through system
configuration rules and
installation guidelines.
Installing NIM to ENIM Upgrade Kit Instructions (51195195-383) Refer to the appropriate sections
hardware in these upgrade kit documents.
HPM to EHPM Upgrade Kit Instructions (51195766-035)
Installing software HPM Installation (HP20600) Refer to the appropriate sections
in these documents.
TPN System Installation (SW20600)
Configuring the Engineer’s Reference Manual (SW09605) Provides a general guide to the
system process engineer's configuration,
HPM Control Theory (HP09–684))
startup, and reconfiguration
PM Family Parameter Reference Dictionary (xPM09–684) efforts for TPN-based TPS
systems.
Describes how to use the HPM/
EHPM.
Defines the user-visible
parameters that exist in the HPM/
EHPM.

52 www.honeywell.com
3 OVERVIEW OF EXPERION AND TPS NODES

User Task Reference Comment


Troubleshooting HPM Service (HP13610) Refer to appropriate sections in
the system this document.

53
3 OVERVIEW OF EXPERION AND TPS NODES

54 www.honeywell.com
4 Supplementary Installation Tasks

55
4 SUPPLEMENTARY INSTALLATION TASKS

4.1 Installation checklists


The following table lists the supplementary installation tasks (in sequential order) that should be performed after
you have completed installing your T-Nodes with the Experion Application DVD.

Task Go To this checklist


Prepare LCN “Prepare TPS/LCN for Integrated Experion-TPS Nodes” on page 57
Post Installation “Post Installation Tasks for ES-T ESVT ACE-T” on page 58
Optional Tasks Perform the optional tasks in “Additional tasks” on page 60.

56 www.honeywell.com
4 SUPPLEMENTARY INSTALLATION TASKS

4.2 Prepare TPS/LCN for Integrated Experion-TPS Nodes


Use the checklist for preparing the TPS/LCN NCF and History Module to support ES-T, ESVT, and ACE-T
nodes.

Prerequisites
Your TPS/LCN version has been upgraded to appropriate version. Refer to the related Customer Release Guide
for steps to upgrade your TPS/LCN.

Note
For information on EUCN integration with Experion network, refer to the Customer Release Guide in the TPN/TPS
bookset.

4.2.1 Before you begin


To perform the preparation tasks, you will need the following software media:
• Use the Utilities and load module media version that is appropriate for respective Experion releases
(recommended).
• For a Universal Station-only site (no existing ES-T nodes): Zip disk media containing load modules (&Z1,
&Z12, &Z14).
• For a site with no existing US or GUS nodes: GUS-TPN Software CD (&Z1).
• For a site with no existing Experion APP or AM nodes: TPN Application Module Software or later CD
(&Z3).

Attention
Refer to the Experion PKS General Release Software Change Notice (SCN) for the media version that is appropriate
for respective Experion releases (recommended).

4.2.2 Tasks

Step Task Go to Done? Notes


1 Copy Experion Nodes with TPS “Copy Load Modules to Use the Utilities and Load Modules
option backplane Load Modules to HM” Software CD or Zip disk.
the History Module.
2 Update NCF with ES-T, ESVT, and “Update an Existing NCF LCN node numbers and types (AM
ACE-T node configurations. for Experion Nodes” for Integrated Experion Server-
TPS, US for Integrated Experion
Note: An ACE - T requires the same
Station - TPS, AM for Integrated
NCF configuration as a Experion App
Experion - TPS ACE-T node) are
node.
specified at this step.
3 Verify or create a checkpoint volume “Create Checkpoints for Note: The procedure to implement
on the History Module for an ESVT ESVT and ACE-T” the ESVT or ACE-T checkpoint
or ACE-T node. volume depends on site factors.
Note: An ACE-T node requires the
same actions as a Experion APP
node.
4 Configure the NCF as necessary. “Additional NCF LCN Nodes
Considerations”
System Wide Values - Console Data
“Time Synchronization
System Wide Values - Clock Source
Considerations”

57
4 SUPPLEMENTARY INSTALLATION TASKS

4.3 Post Installation Tasks for ES-T ESVT ACE-T

Tip
Ensure you have installed the LCNP4 personality. See “Install LCNP Personality Software on local drive” in the
Software Installation User's Guide (SIUG).

Step Task Go to Done? Notes


Configure TPS Components
1 Configure the LCNP “Configure LCNP (Board0) Use the Configuration Utility to
(Board0). Settings” configure LCNP (Board0) settings.
Honeywell recommends that LCNP
Auto Restart be enabled.
2 (Optional) Examine TPN “Verify TPN Server (Optional) Installation creates a
Server Configuration. Configuration” default configuration for the TPN
server. Examine the default settings.
Connect LCN
3 Shut down the computer.
4 Connect the TPS/LCN “Connect the Transceiver and
cables. TPS/LCN Cables”
5 Restart the computer.
5 Verify the LCNP status. “ES-T or ESVT node will not To verify LCNP status, invoke the
load its personality” LCNP Status application (Start >
Programs > Honeywell Experion
PKS > TPS Applications).
Following shutdown/restart and after
the board's software has loaded,
LCNP status should go to OK.
If the LCNP status is not OK, see
“Troubleshooting Approach”.
7 Verify the TPN Server “Troubleshooting Approach” After LCNP status goes to “OK”,
status. use System Management display to
verify the TPN Server status changes
to “Idle.”
If not IDLE, find the symptom in
“Troubleshooting Approach”.
Note: TPN Server status will not
change to “Running” until after you
define the TPS Interface (next task).
Note: A yellow triangle on a
component indicates that events
exist. Right-click to display the
events for that component.
Configure Experion Database
8 Plan the partitioning of “TPS Connection - Tuning Perform this task only if multiple
TPN units properties” on page 106 ESVTs are used on a single LCN.
9 Configure publication of “Publication of the TPN System Perform this task only if multiple
the TPN System Alarm Alarm” on page 135 ESVTs are used on a single LCN.

58 www.honeywell.com
4 SUPPLEMENTARY INSTALLATION TASKS

Step Task Go to Done? Notes


10 Add Experion servers to “Add Experion servers to One Experion Server for each
EMDB EMDB” on page 137 configured system must have the
EMDB installed.
Build Experion Assets so that you
can later map TPS Units to Assets.
For multiple ESVTs on a Single
LCN, all Experion clusters on the
same TPN must be configured to
belong to the same Enterprise Model
system.

Note
If EUCN is integrated with
Experion network, ensure
that all TPN units in which
EHPM points reside, must
have assets defined in the
Experion EMDB, and units
mapped to Experion assets
in the same ESVT cluster.

11 Add/configure TPS “Procedure to configure TPS Station access level must be MNGR.
System Interface System Interface” on page 103
If “Oper” is indicated in lower right
status pane, then select “Oper” and
enter “mngr” in the dialog.
12 Save TPS point “Save TPS points configuration” Perform this task only if multiple
configuration on page 140 ESVTs are used on a single LCN and
if the existing ESVT is split.
13 Map TPS Units to “Map TPS Units to Experion Ensure that the “Notifications
Experion Assets. Assets” on page 109 Enabled” check box is enabled on
status tab after mapping TPS Units.
14 Restore TPS point “Restore TPS points Perform this task only if multiple
configuration for history configuration” on page 142, only ESVTs are used on a single LCN and
and point scripts follow the “Configuring the if the existing ESVT is split.
history collection and the point
scripts for the TPS points” steps.
15 Remove mappings that are “Remove mappings” on page 144 Perform this task only if multiple
no longer needed on the ESVTs are used on a single LCN and
existing Experion cluster if the existing ESVT is split.
16 Configure DSA “Configuring DSA and data
subscriptions between the
Experion clusters” on page 138
17 Restore remaining TPS “Restore TPS points Perform this task only if multiple
point configuration configuration” on page 142 ESVTs are used on a single LCN and
if the existing ESVT is split.
18 Add/configure operators “Procedure to add and configure Verify Station is in MNGR security
Operators” on page 108 level (lower right status pane shows
“Mngr”).
19 Configure Experion For initial steps, see “Procedure Refer to the Server and Client
Console to add Experion Console” on Configuration Guide for Console
page 116 configuration details.
20 If this is an ES-T, add For initial steps, see “Procedure Refer to the Server and Client
Console Station to an to add Console Station” on Configuration Guide for Console
Experion Console (if not page 118 Station configuration details.
already done)

59
4 SUPPLEMENTARY INSTALLATION TASKS

Step Task Go to Done? Notes


21 Configure other Experion Supplementary Installation Tasks Refer to the Software Installation
items Guide, User's Guide or Server and Client
Configuration Guide for
Software Installation User's
configuration details.
Guide,
Server and Client Configuration
Guide
22 If this is an ES-T, verify At the ES-T, do the following
operation of the ES-T verification steps:
applications.
1. Invoke Native Window
(Honeywell Experion PKS >
TPS Applications > Native
Window). The Native Window
should launch with a view to the
TPS/LCN.
2. Invoke Station application
(Honeywell Experion PKS >
Console Station > Station).
3. View Alarm Summary, System
Alarm Summary, and other
standard displays.
At the ESVT, do the following steps:
1. Invoke Station (Honeywell
Experion PKS > Console
Station > Station).
2. Select View > System Status >
Stations > Console Station, and
then select node of interest.
3. The Console Station status
should be OK.
23 Verify the unit mapping “Verify the unit mapping and the Perform this task only if multiple
and the history collection history collection configuration” ESVTs are used on a single LCN.
configuration on page 139

Related topics
“Additional tasks” on page 60

4.3.1 Additional tasks

Step Task Go to Done? Notes


1 Install optional Supplementary Installation Tasks
applications. Guide and this guide
2 Configure the Station This guide
keyboard.
3 Configure ES-T audible “Configure Audible
annunciation. Annunciation” on page 122

60 www.honeywell.com
4 SUPPLEMENTARY INSTALLATION TASKS

Step Task Go to Done? Notes


4 Configure ES-T startup. Experion documentation Configure ES-T startup to ensure
the desired results for operations
personnel (logon script and
SafeView workspace
configuration). The startup
scenario and SafeView
workspaces is modified to support
the TPS Faceplate and Native
Window.
5 If this is an ACE Application Control Environment
installation, configure User Guide
ACE control execution
environment.
6 Add Integrated Experion- “Add Experion nodes to System
TPS nodes to System Management Display”
Management Display.
7 Verify the TPN Server “Verify TPN Server
Configuration. Configuration”
8 Connect the TPS/LCN and “Connect the Transceiver and
Transceiver cables. TPS/LCN Cables”
9 Configure the LCNP “Configure LCNP (Board0)
(Board0). Settings”
10 Loading Personality and “Load Personality and HM
Checkpoint into Server. Checkpoint into ESVT”
11 Loading Personality and “Load Personality and HM
Checkpoint into ACE-T. Checkpoint into ACE-T”

61
4 SUPPLEMENTARY INSTALLATION TASKS

62 www.honeywell.com
5 Common Platform Tasks

Attention
These procedures are to be used in conjunction with an installation checklist.

63
5 COMMON PLATFORM TASKS

5.1 Copy Load Modules to HM


For the Experion nodes to operate properly on the LCN, system files called external load modules are required
in the &CUS and &CLX directories on the TPS/LCN system History Module. Use the following procedure to
copy the system files to the TPS/LCN system History Module.

Attention
This procedure needs to be performed only once per TPS/LCN, not per node.
If Experion nodes are added to a system that already has Experion nodes running, then this procedure is not required,
as the files already exist on the system History Module.

Attention
If no mechanism exists for copying from CD to the History Module (for example, there is no Native Window to
provide emulated disk functionality), then the load modules must be copied using a Universal Station and Honeywell-
provided Zip disk media.
The following procedure uses CDs and emulated disks.

Attention
If you have VIEW ONLY access to the Native Window (that is, you are logged on as Product Administrator and the
administrator does not have permission to change the key level of the Native Window), then you will have to do the
following to have permission to copy files to the TPS/LCN History Module:
Sign on to Signon Manager as an engineering user, that is, a member of the High Security Policy's Local Engineer
group.

Attention
Use the ES-T load module version that is required for the TPS System Status Indicator (S) and TPS Console status
indicator (C) on the Experion Station status bar to function correctly.
Refer to the Experion PKS General Release Software Change Notice (SCN) for the media version that is appropriate
for respective Experion releases (recommended).

1 Click Start > Programs > Honeywell Experion PKS > TPS Applications > Native Window to open the
Native Window.
2 Invoke the Console Status display.
3 Locate this station (will be marked by an asterisk *).
4 Determine and record the Drive Numbers for this station:
$F___ and $F___
• Insert the Utilities and Load Modules CD.
• Click Exit to close the Welcome dialog box.
• When the Are You Sure? dialog box appears, click Yes.
5 Create the Emulated Drives and mount Disk_&z14.lcn and Disk_&z12.lcn:
• Select Access from the Native Window upper menu bar.
• Select Mount/Dismount Emulated Disks menu item.
• Click Create.
• Navigate to the appropriate CD path for your LCN/TPS system (such as, TPN_R620_R650).
• Select system file Disk_&z14.lcn, and then click Open.
• Accept the default information on the Emulated Disk Information screen and click OK.
• Select the file Disk_&z14.lcn in the Available (Dismounted) Emulated Disks port.
• Click Mount, select either the Left Drive or the Right Drive, and then click OK.
• Repeat steps a) through h) for system file Disk_&z12.lcn.

64 www.honeywell.com
5 COMMON PLATFORM TASKS

6 Go to the Native Window Command Processor:


• In the Native Window, select Engineering > Menu from the top menu.
• From the Engineering Main Menu, select the Command Processor target.
7 Type the LSV NET command to verify that the &CUSand &CLX directories exist. If they do not exist, use
the Create Directory command to create them.
8 To support ES-T nodes, copy the files from the Utilities and Load Modules CD to the History Module using
the following individual commands, where:
“$Fn” represents the drive number with Disk_&z14.lcn mounted, and;
“$Fx” represents the drive number with Disk_&z12.lcn mounted.
UNPT NET>&CUS>*.*
CP $Fn>&CUS>MSCHEM.LO NET>&CUS>=
CP $Fn>&CUS>CSCHEM.LO NET>&CUS>=
CP $Fx>&CUS>YGOCX.LO NET>&CUS>=
CP $Fx>&CUS>ES-T.LO NET>&CUS>=
PROT NET>&CUS>*.*

Tip
Instead of entering the commands given in step 9, you may choose to enter the following command to execute a
command file:
EC $Fn>&EC>MSCHEMZ.EC $Fn

Question from MSCHEMZ.EC Your Response


Continue (Yes/No)? Yes
This EC will expect the &Z14 media in $Fn. Yes
Is this correct?
Update Experion or TPS nodes? (Yes/No)? Yes
Are you using a CD-ROM? (Yes/No)? Yes
The drive for mounting &Z12 is currently set to $Fn. Yes
Do you wish to change to another drive (Yes/No)?
On what drive will the &Z12 CD-ROM be mounted $Fx
($F1 - $F20)?
This EC will expect the &Z12 CD-ROM in $Fx. Yes
Is this correct (Yes/No)?

9 To support Experion Server nodes, copy the file from the Utilities and Load Modules CD to the History
Module using the following commands, where “$Fx” represents the drive number with Disk_&z12.lcn
mounted:
UNPT NET>&CUS>*.*
CP $Fx>&CUS>ESVT.LO NET>&CUS>=
PROT NET>&CUS>*.*
10 Dismount the Emulated Disks:
• Select Access from the Native Window upper menu bar.
• Select the Mount/Dismount Emulated Disks menu item.
• Click Dismount adjacent to the Drive containing the disk_&Z14.lcn file and the disk_&Z12.lcn file.
• Click OK.

65
5 COMMON PLATFORM TASKS

11 Remove the Utilities and Load Modules CD.

Attention
Steps 13 17 are NOT required if your TPS/LCN is already operating with Universal Stations.

12 Insert the GUS-TPN Software CD.


13 Using steps similar to the previous operation, mount the emulated disk Disk_&Z1.lcn.
14 From the Native Window Command Processor, perform the following copy command, where $Fn represents
the drive number that has Disk_&z1.lcn mounted.
CP $Fn>&CUS>UPBASE.LO NET>&CUS>=
15 Dismount the Emulated Disk disk_&Z1.lcn.
16 Remove the GUS-TPN Software CD.

Tip
Steps 18 - 22 are NOT required if your TPS/LCN is already operating with the following AM/APP load
modules:
• AMCL06.LO
• XACCES.LO
• XOPTN.LO
• AMCL06.SF

17 Insert the TPN Application Module CD.


18 Using steps similar to the previous operation, mount the emulated disk Disk_&z3.lcn.
19 Copy the files from the TPN Application Module CD using the following commands, where, “$Fx”
represents the drive number with Disk_&z3.lcn mounted:
UNPT NET>&CUS>*.*
UNPT NET>&CLX>*.*
CP $Fx>&CUS>AMCL06_2.LO NET>&CUS>=
CP $Fx>&CUS>XACCES.LO NET>&CUS>=
CP $Fx>&CUS>XOPTN.LO NET>&CUS>=
CP $Fx>&CLX>AMCL06.SF NET>&CLX>=
PROT NET>&CUS>*.*
PROT NET>&CLX>*.*
20 Dismount the Emulated Disk.
21 Remove the TPN Application Module Software CD.

Tip
The LCN Diagnosis tool ((disk_&Z18.LCN) is a standalone personality image that runs on GUS through the
Native Window. The tool helps to investigate the LCN network transaction anomalies.

Stop
You have completed this task. Return to the checklist that led you to this task.

66 www.honeywell.com
5 COMMON PLATFORM TASKS

5.2 Update an Existing NCF for Experion Nodes


This procedure will update the TPS/LCN NCF with the Integrated Experion-TPS node (ES-T, ESVT, and ACE-
T) information. This can be done from a Universal Station, from the Native Window on a GUS, or from the
Native Window of an ES-T.

Attention
The ESVT node and the ACE-T node are specialized AM/Experion APP nodes. You must assign one unit to the node
in its NCF.

Attention
When installing and configuring redundant Servers, associated AMs MUST BE CONFIGURED AS SEPARATE
(NON-REDUNDANT) AMs in the NCF. They will not function properly if configured as a redundant pair.

Prerequisites
Determine the requirements for time synchronization between LCN and Experion nodes. For more information,
see “Time Synchronization Considerations” on page 76.
For an ESVT or ACE-T node:
Identify or create one Unit to be assigned to the ESVT or to the ACE-T.
• From Engineering Main Menu, select UNIT NAMES, locate/configure the Unit to be used and note its
index number.
If necessary, verify that the Unit is not already being used:
• Using the Command Processor, type “LSV NET” and verify that a checkpoint directory named &Fxx does
not already exist, where xx is the index number of the unit of interest.

Attention
This procedure requires Engineering access level.
If you have VIEW ONLY access to the Native Window (that is, you are logged on as Product Administrator and the
administrator does not have permission to change the key level of the Native Window), then you will have to do the
following to have permission to copy files to the TPS/LCN History Module:
Sign on to Signon Manager as an engineering user, that is, a member of the Local Engineer group. .

5.2.1 Overview of NCF node configuration procedure


The following figure shows an overview of the NCF configuration procedure for ESVT.

67
5 COMMON PLATFORM TASKS

The following figure shows an overview of the NCF configuration procedure for ES-T

68 www.honeywell.com
5 COMMON PLATFORM TASKS

CAUTION
In the NCF, if you define the STATION DEFAULT ACCESS LEVEL as VIEW for the ES-T then the ES-T cannot
set the Native Window to Operator because it will be clamped to VIEW by the LCN. The VIEW access level
permits you to only call up and view displays. It does not permit you to make any changes.

The following figure shows an overview of the NCF configuration procedure for ACE-T.

69
5 COMMON PLATFORM TASKS

Attention
Review Load Module Memory
Load modules typically increase in size as newer versions are released. You may use the LCN/TPN tool kit schematic
CBREV to determine the version of load modules currently in use. If newer versions have just been installed, ensure
that your NCF configuration allows sufficient space for the larger load modules.
The MAXIMUM amount of free memory must be 20,000 greater than the TOTAL.
For more information about the CBREV schematic, see “Verifying TPS/LCN Installation and Version” on page 357.

5.2.2 Procedure for configuring the NCF Node


1 From a Universal Station or Native Window with engineering access level, go to the Engineering Main
Menu.
2 Go to Support Utilities > Modify Volume Paths.
3 Ensure that the NCF backup path points to one of the bkupasy disks and then return to the Engineering
Main Menu.
Server and/or ACE Node Configuration
4 Select LCN Nodes and select the relevant node number for the Server and/or ACE.
5 On a new node, select APPLICATION MODULE and then go to the next step.
On an existing node, select Modify Node and skip the next step.
6 On a new node, enter the following node information and then go to the next configuration page:
Assigned Units (Assign the unit identified in the prerequisites.)
7 For an ESVT, leave the entries with the default values. AM points, algorithms, and CL processing are not
supported.

70 www.honeywell.com
5 COMMON PLATFORM TASKS

For an ACE-T, if AM points, algorithms or CL programs will be used, configure the User Memory as
described in Application Module Implementation Guidelines; otherwise leave these entries with the default
values.
Go to the next NCF page.
8 For a Server, add the following External Load Modules for the personality so that the ESVT Load module is
the last entry in a load module sequence:
AMCL06_2 AMO
XACCES AMO
XOPTN AMO
ESVT AMO
For an ACE-T, add the following External Load Modules:
AMCL06_2 AMO
XACCES AMO
XOPTN AMO
If AM points, algorithms, or CL programs are being used, configure additional load modules and module
memory as described in Application Module Implementation Guidelines; otherwise leave these entries with
the default values.
9 Enter, Check, and Install the NCF change.
10 Experion Station - TPS Configuration
11 Return to the LCN Nodes display and select the relevant node number for the ES-T.
12 On a new LCN node, select UNIVERSAL STATION and then go to the next step.
On an existing node, select Modify Node and skip the next step.
13 On a new LCN node, configure first page for the Universal Station (refer to ATTENTION box), then page
forward to the External Load Module page.
Refer to the Network Form Instructions manual in the TPS/LCN book set for node configuration instructions
for the Universal Station node type (US, GUS, or ES-T).

Attention
For ES-T nodes, Honeywell recommends selecting YES for the following configuration items:
• Station Options
• Annun During Eng Func
For ES-T nodes, the NO setting will be effective only if Experion audible annunciation is disabled. The NO
setting in the NCF configuration will not disable annunciation driven by the Experion station application.

14 Add the following External Load Modules for the personality so that the ES-T Load Module is the last entry
in a load module sequence:
UPBASE - UP
MSCHEM - UP
CSCHEM - UP
YGOCX - UP
ES-T - UP
15 Clear the value in the MAXIMUM EXTERNAL MODULE MEMORY UP port.
16 Click ENTER.
Result: The total amount of memory required is recalculated and displayed as the TOTAL (MODULES
PLUS ADDITIONAL MEMORY).
17 The MAXIMUM must be 20,000 greater than the TOTAL.
Type in the appropriate value into the MAXIMUM EXTERNAL MODULE MEMORY (WORDS) UP
port.

71
5 COMMON PLATFORM TASKS

18 Enter, Check, and Install the NCF change.


19 Fast Load Disks
20 If you use fast load disks, then copy the new NCF to the fast load disks and emulated fast load disks.
For information on fast load cartridges, refer to the Engineer's Reference Manual

5.2.3 Building AM Points


After you configure the AM on the ACE-T node, you can build and load your AM points by using the TPS
Builder, or by using the Data Entity Builder that is available through the Native Window.
The following AM documents provide information about implementation guidelines, point types, parameters,
and configuration form instructions:
• Application Module Implementation Guidelines
• Application Module Control Functions
• Application Module Algorithm Engineering Data
• Application Module Parameter Reference Dictionary
• AM Configuration Form Instructions
• Control Language Application Module Reference Manual
• Control Language Application Module Overview

Stop
You have completed this task. Return to the checklist that led you to this task.

72 www.honeywell.com
5 COMMON PLATFORM TASKS

5.3 Create Checkpoints for ESVT and ACE-T


An ESVT and ACE-T when installed on an LCN are specialized AM/Experion APP nodes. When you configure
the NCF, you must assign at least one TPS/LCN Unit. This unit assignment determines the name for the node's
checkpoint directory (For example, if Unit AA has a unit index of 04, its checkpoint directory name must be
&F04). A checkpoint file in the appropriate directory must exist on the HM in order to load the ESVT or ACE-
T.
The ESVT and ACE-T can be configured in the HM Volume Configuration to be a node that is auto-
checkpointed, such that the HM reserves space for it and automatically configures the checkpoint volume
(&5nn, where nn is the node number) during HM initialization.
If the above step is not done, then the user can manually create the appropriate HM directory for the specific
Unit Index on a user volume of the HM, and then copy the NULL checkpoint file to that directory. In the later
case, automatic checkpointing is not supported.

Attention
The ESVT clients can access AM points that are on other AM nodes.

Prerequisites
Using the NCF Unit Names display, determine the index (1…100) of the Unit that was assigned to the ESVT
and ACE-T through the NCF LCN Nodes configuration.

5.3.1 Procedure for creating check points


1 From a Universal Station or Native Window with engineering access level, go to the Engineering Main
Menu.
2 On a user volume, create a directory with the name &Fxx:
CD NET>vol &Fxx

Where, vol is the user volume name, and xx is the index of the unit identified in the prerequisite.
3 If using a Universal Station, locate and mount the physical &Z6 zip disk.
If using a Native Window:
• Locate the emulated disk file disk_&z6.lcn on the GUS-TPN Software CD and mount it as an emulated
disk.
• In the Native Window, click the Access > Mount/Dismount Emulated Disks menu item and mount the
emulated disk.
4 Based on the index for the unit identified in the prerequisites, copy the associated master null checkpoint file
from the &amc directory on the disk to the &Fxx directory on the HM.
The master null checkpoint files are named AMxxxMAS.CP, where xxx is unit numbers 001-100.
For example, the Commands for unit 16, drive $F11, are as follows:
CP $F11>&AMC>AM016MAS.CP <space> NET>&F16>AM016MAS.CP

UNPT NET>&F16>AM016MAS.CP

Stop
You have completed this task. Return to the checklist that led you to this task.

73
5 COMMON PLATFORM TASKS

5.4 Additional NCF Considerations

5.4.1 LCN Nodes


Honeywell recommends the following NCF configuration selections.

NCF Configuration Item Recommended Selection


Annun During Eng Func For US and GUS nodes, leave as required.
For ES-T nodes, select YES.
For ES-T nodes, the NO setting will be effective only if Experion audible
annunciation is disabled. The NO setting in the NCF configuration will not disable
annunciation driven by the Experion station application.
There would therefore be no matching Experion settings. The setting would be left
the same as for NCF.

5.4.2 System Wide Values - Console Data


Honeywell recommends the following NCF configuration selections.

NCF Configuration Item Recommended Selection


CL Message Confirmation-After- YES (Message confirmation is allowed only after Acknowledgment occurs.)
Acknowledgement
On an Experion system, uncheck the box Perform Auto Acknowledge when
Confirm Message key pressed (IKB only).
Note: The NCF setting MUST be set to YES (as opposed to recommended setting)
for proper Experion-TPS integration.
Horn Annunciation Policy: Contact 1, Contact 2, or Contact 3
Console Status Event Match the selection for the Urgent Alarm on the Experion Connection Properties
- Sounds page.
System Status Event
For more information about the Experion Connection Properties - Sounds page,
see “Configure Audible Annunciation”.
Operator ACK Only Message Leave as required by the US/GUS nodes, or click None
Operator Confirm Message
Low Priority Alarm Match this configuration with the selections for the Low, High and Urgent Alarms
respectively, on the Experion Connection Properties - Sounds page.
High Priority Alarm
For more information about the Experion Connection Properties - Sounds page,
Emergency Priority Alarm
see “Configure Audible Annunciation”.
Contact 1 Output State STEADY
Contact 2 Output State Note: The MOMENTARY setting may be considered if it exactly matches settings
on the Experion Server-wide Settings - Alarm/Event Options configuration
Contact 3 Output State
page.
Audible Alarm Annunciation Leave as required by the US/GUS nodes.
Suppression Time-Out (Seconds)
This configuration item is related to the operation of the Audible Suppress Option
on the US TPS/LCN Alarm Summary display (see the following ATTENTION
box).

74 www.honeywell.com
5 COMMON PLATFORM TASKS

NCF Configuration Item Recommended Selection


Console-Wide Silence Button? NO
Note: Supporting Experion console functionality requires a setting of NO. The
matching Experion setting should be “Single Station or single console (all Stations
in console)” from the Experion Server-wide Settings - Alarm/Event Options
configuration page.
Contact Cutout Alarms on Alarm Clear When Acked
Summary
MUST be set to “Clear When Acked” for proper Experion-TPS integration.
Area-Based Process Alarm NO
Acknowledgement
The recommended setting is “NO” for proper Experion-TPS integration.
Contact Cutout Alarms on Alarm Must be set to “Clear When Acked”
Summary
Alenbst Indication in Journal for YES
Disabled Alarms

Attention
TPN/LCN Alarm Summary Display
• Use of the Audible Suppress option (the target that is labeled AUDIBLE) on the TPS/LCN Alarm Summary
display is not recommended on ES-T nodes.
• Experion R410 supports suppressing audible annunciations on the Experion Alarm Summary Display.
• With Experion R410, a system wide setting is available to enable or disable the audible suppression and can be
used for setting the highest priority audible alarm.

5.4.3 System Wide Values - Clock Source


To maintain consistent alarm and event time stamping between LCN/TPN nodes and Experion nodes, a selected
Windows node (Experion nodes with a LCNP card, GUS, or ES-T, or Experion APP) must be configured as the
primary clock source. An alternate Windows node may be designated as a secondary clock source.
For details about time synchronization between LCN/TPN and Experion nodes, see “Time Synchronization
Considerations” on page 76.

75
5 COMMON PLATFORM TASKS

5.5 Time Synchronization Considerations


LCN (TPN) time and Windows time should be synchronized to maintain consistent alarm and event time
stamping between LCN and Experion nodes. The LCN and Windows times must be synchronized using one of
the following solutions:
Windows Time Source
Common Time Source (parallel synchronization mechanisms)
For details about LCN/TPN time synchronization, refer to the following documents:
• Configuration Utilities Users Guide:
– Section “TPN Time Sync Controls”
– Section “TPN Time Sync Page”
• GPS Antenna User's Guide
• TPN Bridge Overview and Implementation Guide

Solution 1: Windows Time Source


Using a Windows time source, Windows nodes (such as ESVT, ES-T, and Experion APP) are synchronized
through Windows domain time synchronization mechanisms. The LCN time is periodically synchronized by a
selected Windows node though TPS infrastructure mechanisms. Honeywell suggests using this approach if the
LCN is not currently being synchronized with GPS.
Using this approach,
The LCN NCF must be configured to designate a selected Windows node as the primary clock source.
An alternate Windows node may be designated in the NCF as a secondary clock source.
The clock source node(s) must contain the LCNP4-GPS card (although, for the approach described here, a GPS
source is not required).

Solution 2: Common Time Source, Parallel Synchronization Mechanisms


If it is required to synchronize multiple LCNs, solution 2 is preferable, as the Windows time synchronization is
not as high resolution as the GPS or the LCN, so there can be variations between LCNs, even if basing time on
the same PC network.
Using this approach,
A common, accurate GPS time source must be available.
If the LCN is already time synchronized to GPS time (using existing LCN mechanisms), then that mechanism
can continue to be used.
In parallel, the Windows domain must be synchronized to a GPS source.
The LCN NCF must be configured to designate a Windows node (ESVT, ES-T, or Experion APP) as the
primary clock source.
An alternate Windows node may be designated in the NCF as a secondary clock source.
The clock source node(s) must contain the LCNP4-GPS card.

Stop
You have completed this task. Return to the checklist that led you to this task.

76 www.honeywell.com
5 COMMON PLATFORM TASKS

5.6 Add Experion nodes to System Management Display

5.6.1 Multicast consideration


System Management utilizes multicasting to process information between Experion nodes. Multicasting must be
enabled on all network switches and routers that interconnect participating nodes.
For details, refer to the System Management Configuration Guide, section “Configuring the System
Management Display,” subsection “Using the Multicast/Heartbeat Settings property page for multiple
computers.”
If you are using Fault Tolerant Ethernet (FTE), the multicast configuration establishes the FTE community. The
multicast address setting must be configured from the FTE configuration page and not the System Management
Display.
For details, refer to the Fault Tolerant Ethernet Overview and Implementation Guide, section “Planning a
Honeywell FTE Network,” and Fault Tolerant Ethernet Overview and Implementation Guide section
“Configuring FTE and Network Adapters”.

5.6.2 Procedure for adding a node as managed item


The following procedure demonstrates how to add a node to be monitored by the System Management Display,
a Microsoft Management Console (MMC) containing the Honeywell Node Administration snap-in.

Tip
This procedure assumes you are aware of which domain contains the computer of interest. If you do not know, you
can browse for the computer from the domain's Properties tab.

1 Click Start Menu > All Programs > Honeywell Experion PKS > System Management > System
Management Display to open the System Management display.
2 From the MMC Tree view, right click the domain that contains the computer of interest and select
Properties from the menu.

The selected domain's Properties dialog box appears.


3 From the Domain Properties dialog box, click the Item Properties tab to view the name and properties of
the domain.

77
5 COMMON PLATFORM TASKS

4 Select the Add/Remove Computers tab so that you can browse to the computers of interest.

78 www.honeywell.com
5 COMMON PLATFORM TASKS

5 From the selection window, expand the domain's tree view to locate the computer of interest.
In this example, the computer of interest resides in the domain named DESIGN. It is not necessary to click
the check box of the domain (otherwise you would be monitoring all the computers in that domain), just
click the PLUS sign (+) to expand the view.
6 Continue to expand the view until you locate the computer of interest. Select the check box for the computer
of interest then click OK.

7 The computer of interest appears in the Tree view. You can proceed with other administration tasks or
continue to modify and save the console view.

79
5 COMMON PLATFORM TASKS

Attention
If you attempt to start the TPN Server before the LCNP personality is loaded and running, then the TPN Server
will go to the WARNING state. This is expected behavior.
To attempt to start the TPN Server, right-click the node's TPN Server component and select All Tasks > Start.

Stop
You have completed this task. Return to the checklist that led you to this task.

80 www.honeywell.com
5 COMMON PLATFORM TASKS

5.7 Verify TPN Server Configuration


The TPN Server is automatically configured for your Experion node with TPS options. Use the following
procedure to review or change the TPN Server configuration settings for an Experion node on TPS.

To verify the TPN Server configuration


1 Click Start > Programs > Honeywell Experion PKS > System Management > Configuration Utility.
2 Select Configure > HCI Component to display the HCI Component Configuration page.
3 From the Component Name pull down list, select the TPN Server initially configured for the Experion
node.
Result: The configuration page displays TPN Server properties.
4 Accept the default HCI Persistent Filename for the checkpoint file. The file represents a saved database for
your TPN Server that is located in the directory, C:\ProgramData\Honeywell\Checkpoints.

Attention
With Custom Install Path (CIP) being supported from Experion R410, you can change the default path of
installation (C:\ProgramData\Honeywell) to any possible path.

5 Do not change the Auxiliary Status Display ProgID from the default. The entry represents a status display
used to monitor your TPN Server.
6 Click Enter/Edit Server Specific Configuration to display the remaining configuration pages.

7 Click YES, and then click OK.


The Server Specific Configuration pages appear.

8 Click the Checkpoint / Prime tab.


9 Review specified Time Period or Pre-Defined Times:
a Select the Enabled check box in the Time Period group to establish periodic backups of the TPN
Server's cache.
b An integer value between 1 and 255 is a valid entry in the Checkpoint Every box. The Time Period is
relative to the start-up time of the TPN Server.
c Example: With a Time Period of 1, if the TPN Server started at 10:30 A.M., it automatically checkpoints
at 11:30am, 12:30pm, 1:30pm, and so forth.
d Select the Enabled check box in the Pre-Defined Times group to set up pre-defined times for saving the
cache to the checkpoint file.
e When enabled, the TPN Server copies the cache to the checkpoint file at the specified times. A 24-hour
clock is used to specify the Pre-Defined times. All times are to the nearest hour. Up to six pre-defined
times can be configured. Leaving a Time box blank has no effect on automatic checkpointing. Duplicate
values are allowed, but are ignored by the TPN Server.
Example: 23 (11pm).

81
5 COMMON PLATFORM TASKS

Tip
The check box in the Pre-Defined Times group can be enabled if the check box in the Time Period group is
also enabled. The auto checkpoint options are not mutually exclusive.
Automatic checkpointing helps maintain fast display invocation times, since the TPN Server will not have
to rebuild its entire cache following “unadvised” stops.

10 Click the Default Access and Priority Levels Page tab.


11 Select the access level from the Access Level drop-down list that you want OPC clients connected to the
TPN server to use when writing to TPS points.
12 Retain the defaults on the remaining pages:
• Channels (for the correct default values, see “Verifying Configuration of Board 0 Data Access
Configuration and TPN Server Channels” on page 359)
• Default Access and Priority Levels
• Security
13 Click OK to close the dialogs.

Stop
You have completed this task. Return to the checklist that led you to this task.

82 www.honeywell.com
5 COMMON PLATFORM TASKS

5.8 Connect the Transceiver and TPS/LCN Cables


Use the following procedure to physically connect the node to the TPS/LCN.
1 Click Start > Shut Down > Shut Down.
2 Click OK to verify the shutdown.
3 If necessary, turn off the power to the node.
4 Connect the AUI cable from the LCNP board to the Transceiver (MAU).
5 Connect the cable from the Transceiver to the TPN/LCN.
6 Start up the node.

Stop
You have completed this task. Return to the checklist that led you to this task.

83
5 COMMON PLATFORM TASKS

5.9 Configure LCNP (Board0) Settings

Attention
Do not run multiple instances of the Configuration Utility as it can present inconsistent views of the information and
may cause problems.

5.9.1 Edit LCNP Settings


1 Click Start > Programs > Honeywell Experion PKS > System Management > Configuration Utility.
2 Go to Configure > Board 0 to display the LCNP page.
3 Type the pre-determined LCN Address.
4 Type the pre-determined NG Name, if any. If no NG name, enter a space.
5 Type an LCN Name that is meaningful to your plant personnel.

Tip
If you select LCN Name under Experion TPS System Alarm, the LCN Name appears on the Native Window's
title bar and the System Alarm display. In the following example, the individual node's computer name (EST41)
is specified as the LCN Name.
The same LCN name can be assigned to all stations in the LCN (for example, NorthPlant_LCN). Therefore, the
TPS System Alarm is reported with the same message every time. For more information about the TPS System
Alarm, see the “Managing System Alarms” section.

For detailed information on LCNP (Board0) screen entries, refer to Configuration Utility User's Guide.

84 www.honeywell.com
5 COMMON PLATFORM TASKS

6 If you want to allow the LCNP to be able to be reset from a remote node, select the LCNP Reset Controls
Remote check box
7 Select the source for an Experion TPS System Alarm. For new installs, the default selection is <Disable>.
For systems that have been migrated from a previous release, this might be set to Cluster Server Name. It is
recommended to disable the TPS system alarm and instead use the TPS System Status and TPS Console
Status indicators in the Experion Station status bar.
• Computer Name: There is one TPS system alarm for each ES-T. The Computer Name in the <Source
Name>.
• LCN Name: LCN Name is a user-selected TPS system alarm source identifier to allow the aggregation
of TPS system alarms among a set of ES-Ts, based on configuration or operational considerations.
The Experion PKS System Alarm Summary Display will show a TPS system alarm per LCN Name.
Type the LCN Name in the <Source Name> space.
• Cluster Server Name: Default. Every ES-T in the Experion PKS cluster is configured for the Cluster
Server Name as a default. If Cluster Server Name is selected, there is only one TPS System Alarm on
the Experion PKS System Alarm Summary Display per cluster.
• <Disable>: You can disable the TPS system alarm for a node. It is recommended to use this setting for
users migrating to Experion R410.

Tip
The Experion TPS System Alarm is applicable only for ES-T nodes.
When a TPS System Alarm occurs, a Windows event occurs on each ES-T. The System Event Server (SES)
captures and converts this Windows event into an Experion PKS System Alarm, or updates an existing alarm.
Your selection in step 7 determines what is to be the source of the Experion TPS System Alarm and specifies
the name of the source. In the following example, the Computer Name IDEVESVT18 is the alarm source.

Attention
All ES-Ts must have the same LCN Node Annunciation Policy and the same Process Network Annunciation
Policy in the ES-T Area databases.
Select Computer Name or LCN Name in step 7 if the ES-Ts' Area databases have different annunciation policies.

8 If you want the Personality to:


• Load automatically whenever the node transitions to the PWR_ON state, then select the Enable LCNP
Auto Restart check box.
• Not load automatically, whenever it transitions to the PWR_ON state, then leave the Enable LCNP
Auto Restart check box unchecked.
If you are not sure what to configure, leave the Enable LCNP Auto Restart check box unchecked.

85
5 COMMON PLATFORM TASKS

9 Click Apply.
10 For the ESVT, you have completed this task. Return to the checklist that led you to this task.
For ES-T, continue with the “Edit ES-T Native Window settings” on page 86 procedure.

5.9.2 Edit ES-T Native Window settings


1 Click the Native Window tab.
2 Use the following table to set the options.

Option Option Setting


Enable Local Connections It is recommended that this check box be checked.
Enable Remote Connections Check this box to enable Native Window connection to the local LCNP board
by remote users.
Enable Local Connection Override It is recommended that this box be checked. Check this box to enable the ability
to override a remote user's Native Window connection when a local user Native
Window connection is requested. The local user is notified that the Native
Window is in use by another user (user is identified) and is warned that the
remote user will be disconnected. If the local user overrides the connection, the
remote user is disconnected and is informed that the connection was terminated.
Allow Disconnect Select the check box to allow any user account to disconnect a local Native
Window connection.
Confirm Disconnects It is recommended that this check box be checked.
Clear Display On Disconnect It is recommended that this check box be checked.
LCNP Auto Restart Select the Enable LCNP Auto Restart Menu Item check box to display the
LCNP Auto Restart menu item in the Access menu of the Native Window.
LCNP Reset Enables Local, Remote Select Local to allow a reset only from the local Native Window or Emulators
Status display.
Select Remote to allow the LCNP to be reset from a remote node.
Print Trend Select the Disable Print Trend check box to disable the continuous trend print
function.
Maintain 1:1 Aspect Ratio It is recommended that this box be checked.
Font Smoothing It is recommended that this box be checked.
Full Screen It is recommended that this box be unchecked.
Show Menu/Title Bars It is recommended that this box be checked.
Show Status Bar It is recommended that this box be checked.
Mouse Button Function Selection It is recommended to use the default settings. Click the Help button for function
Options information.
IKB/OEP Annunciation Set to Engineer Menu on close: When checked, closing the Native Window
sets the emulators to the Engineering Main menu and suppresses IKB alarm
annunciation.
TPN in absence of Experion: If an ES-T, then uncheck so Experion events can
annunciate from the IKB/OEP. If a Native-Window-only Station, or Experion-
ready node (that is, the node does not have Experion Station functionality
available), then check so TPN events can annunciate from the IKB/OEP.

86 www.honeywell.com
5 COMMON PLATFORM TASKS

Option Option Setting


Experion Processing of IKB/OEP The operators can invoke Experion Detail, Group, Trend, and Group History
Keys displays directly from the Native Window or GUS displays, associated with any
point in the change zone for the active Native Window or GUS display. For
example, consider the point A100 is displayed in the Native Window change
zone. If you press the IKB Detail key while the Native Window is the active
display, the Experion detail display for A100 is invoked. Similarly, an Experion
Group, Trend, or Group History display is invoked for the point A100 by
pressing the Group, Trend or Hour Avg IKB key, if the change zone point is
configured in an Experion group or trend. If a change zone point is not
configured in an Experion group or trend, then the operator is prompted for
Experion group/group history or trend number to invoke.
For more information, refer to the
Configuration Tool User Guide.

3 For ES-T, continue to the next procedure, “Edit ES-T Keyboard Settings.”

5.9.3 Edit ES-T Keyboard settings


1 Click the Keyboard tab.
2 Honeywell recommends leaving all annunciator contacts Disabled.
3 Continue to the procedure, “Configure TPS/LCN Printer Settings” on page 88.

87
5 COMMON PLATFORM TASKS

5.9.4 Configure TPS/LCN Printer Settings


The three printer configuration choices are described below:
• The No Printer Selected option is used when the node will not connect to a printer. Select this mode if the
printer function of the Universal Station is not to be used. If this mode is selected and the TPS/LCN NCF
has a printer configured for the node, then the Native Window Console Status display will indicate that the
printer for this node is offline.
• The Batch Printer Selection option causes printed output from the Universal Station to be collected until
the configured time or line limit is reached, and then printed as a batch. In this mode, the true status of the
printer is hidden by the Windows operating system, and will most often show as OK on the Native Window
Console Status display, even when the printer is off-line or absent.
• The Continuous Printer Selection option most closely emulates the printing behavior of the Universal
Station. In this mode, only the Signum serial printer is supported. The Signum printer must be connected to
a serial port of this node. It cannot be used across the network. When used in this mode, the printer is
dedicated to this function, and cannot be shared with any other application on this or any other node. In this
mode, print output from the Universal Station is sent immediately to the printer. This is particularly useful
for printing alarms.
A typical Printer tab is shown below.

To configure the “No Printer Selected” option


1 On the Printer tab, select the No Printer Selected option button.
2 Click OK to complete the LCNP board configuration.

Stop
You have completed this task. Return to the checklist that led you to this task.

To configure the “Batch Printer Selection” option


1 On the Printer tab, select the Batch Printer Selection option button.
2 Complete the Windows printer setup, and then do the next step.
3 Click Print Setup to display the standard Windows Print Setup dialog box.
4 Select the desired options and then click OK.
5 Click Font Setup to change the font used for printing.
6 Change Idle Flush Time field to the desired number of seconds.
7 Change Queue Length field to the desired number of lines.

88 www.honeywell.com
5 COMMON PLATFORM TASKS

Attention
Idle Flush Time is the maximum period of time in seconds that RTJ entries are stored before they are
automatically flushed from the RTJ print queue and sent to the printer.
The Idle Flush Time setting controls printing only when the Idle Flush Time maximum is reached before the
Queue Length maximum.
Queue Length is the maximum number of lines allowed in the RTJ print queue before the lines are automatically
sent to the printer.
The Queue Length setting controls printing only when the Queue Length maximum is reached before the Idle
Flush Time maximum.
Idle Flush Time and Queue Length
If RTJ events occur at infrequent intervals, the Idle Flush Time parameter can be set to over a year (32 million
seconds). This forces the Queue Length parameter to activate printing when the desired number of lines is reached,
instead of when the idle time runs out.
If the Idle Flush Time and Queue Length are both set to 60, then after every 60 seconds or every 60 lines
(whichever comes first) the RTJ print queue will be sent to the printer.

8 Click OK to complete the LCNP board configuration.

Stop
You have completed this task. Return to the checklist that led you to this task.

To configure a Network Printer as a TPS/LCN Batch Printer


1 From the Start menu, click on Devices and Printers.
2 Right click and select Add a Printer option.
3 Select Add a network, wireless or Bluetooth Printer option and then click Next.
4 Select The printer that I wasn’t isn’t listed option and then click Next.
5 Select Add a printer using a TCP/IP address or hostname option and then click Next.
6 Enter the Hostname or IP address of the network printer (this is not the IP of the shared printer) and then
click Next.

Tip
Port name will be filled in automatically, add IP_ before the port name.

7 On the Add Printer page, click Next.


8 Click Next.
9 Select Do not share this printer option (since this printer is already shared from another computer in the
same network) and then click Next.
10 Click Finish.
11 From the printer configuration setup page, select the printer which you have configured.
Now the Native Window Console Status for PRINTER should show OK.

89
5 COMMON PLATFORM TASKS

To configure the “Continuous Printer Selection” option


1 On the Printer tab, select the Continuous Printer Selection option button.
2 Select ASPI Serial Printer as the Model as this release of TPS only supports the Signum ASPI printer.

Tip
If your system has additional printer filters installed, select the correct printer type in the Model field. Also,
some print filters may display a Protocol field; if so; set that selection to match the configuration of the printer.

3 Select the correct Port for the printer.

Tip
The printer must not be configured as a shared Windows printer. If the printer is currently configured as a
shared printer, then the printer's port will not be selectable. Use the Printer Control Panel to reconfigure the
printer, so it can be used as a continuous mode printer.

4 Click OK to complete the LCNP board configuration.

Attention
On the Signum 2043 printer, set the LENGTH parameter to be one line for every path (manual, front push, rear
push), allowing the printer to print a real-time alarm line, followed by a one line page feed.

Stop
You have completed this task. Return to the checklist that led you to this task.

90 www.honeywell.com
5 COMMON PLATFORM TASKS

5.10 Load Personality into ES-T

Tip
If LCNP Auto Restart has been enabled for this node, you may not need to do this task, as the personality will
automatically load whenever the node transitions to the PWR_ON state.

To load a personality into an ES-T


1 Log on to the node as Product Administrator.
2 Click Start > Programs Honeywell Experion PKS > TPS Applications > Native Window to open the
Native Window.
3 Click the LEDs: xx button to display the LCNP Status display where “xx” is the LCN address of your node,
and then click Details.
4 Click Reset LCNP, and then click Yes to the Are you sure? prompt.
5 When the State shows PWR_ON and the Native Window shows the GREATER THAN symbol (>), click
Load on the Native Window status bar.
6 Type W and then press <ENTER> in response to the W, N, 1, 2, 3, 4, X? prompt in the Native Window.
The personality load begins. (If “????” appears after the W prompt, there are no personalities available on
this station. Refer to the procedure to copy personalities to the station and then attempt another personality
load.)
7 Type N and then press <ENTER> in response to the NCF? N, 1, 2, 3, 4, X? prompt in the Native Window.
The HM loads the NCF into the node. When the loading completes, the Native Window's System Status
display appears. (If “????” appears after the NCF prompt, the HM is not available in your system. Restart
your HM or locate a current NCF that can be loaded from removable media.)
8 Select the node and then select Node Status.
The Node Status display indicates ES-T as the node type. (If the node appears as GUS, the node's TPN
Server is not running. Select and right-click the TPN Server from the System Management Display, and then
click All Tasks > Start.)

Stop
You have completed this task. Return to the checklist that led you to this task.

91
5 COMMON PLATFORM TASKS

5.11 Load Personality and HM Checkpoint into ESVT

Tip
If LCNP Auto Restart has been enabled for this node, you may not have to perform this task, as the personality will
automatically load whenever the node transitions to the PWR_ON state.

To load a personality and HM checkpoint into an ESVT


1 From the TPS/LCN System Status display, select the ESVT node of interest and then select Node Status.
The ESVT appears as an AM.
2 Select the node of interest and perform a Shut Down as necessary to set the node to the PWR_ON or FAIL
state.
3 Load the LCN-side of the node with the AM personality using the AUTOLOAD NET target.

Tip
Engineer access level may be required to AUTOLOAD. To change the access level to Engineer, sign on to
Signon Manager using an account with ENGR access level.

4 When the loading completes, check that the Node Status display (Native Window) indicates ESVT as the
node type.

Tip
If the node does not appear as an ESVT, verify the following:
• The node's TPN server is running.
• The load modules for the ESVT have been configured in the NCF and exist on the History Module.

Stop
You have completed this task. Return to the checklist that led you to this task.

92 www.honeywell.com
5 COMMON PLATFORM TASKS

5.12 Load Personality and HM Checkpoint into ACE-T

Tip
If LCNP Auto Restart has been enabled for this node, you may not have to perform this task, as the personality will
automatically load whenever the node transitions to the PWR_ON state.

To load a personality and HM checkpoint into an ACE-T


1 From the TPS/LCN System Status display, select the ACE-T (AM) node of interest and then select Node
Status. The ACE-T appears as an AM.
2 Select the node of interest and perform Shut Down as necessary to set the node to the PWR_ON or FAIL
state.
3 Load the LCN-side of the node with the AM personality using the AUTOLOAD NET target.

Tip
Engineer access level may be required to AUTOLOAD. To change the access level to Engineer, sign on to
Signon Manager using an account with ENGR access level.

4 When the loading completes, check that the Node Status display (Native Window) indicates APP as the
node type.

Tip
If the node does not appear as an APP, verify the following:
• The ACE-T node's TPN server is running.
• The external load modules for the ACE-T node have been configured in the NCF and exist on the History
Module.

Stop
You have completed this task. Return to the checklist that led you to this task.

93
5 COMMON PLATFORM TASKS

5.13 Establishing Access Permissions for Signon Manager

5.13.1 Purpose of establishing access permissions


To enable a user or group of users to access the TPS/LCN through a specific node's LCNP, the user or group
must be in a High Security Policy local group.
The best practice is to add your global users to the global groups at the Domain Controller. In Active Directory,
a global user is a normal user account in the user's domain. For example, add Joe Engineer to the global
Engineers group.
The global Engineers group should be a member of the Local Engineers group and have Engineer access by
default. The Link Domain Groups application performs this action. This application should be executed
following installation of the High Security Policy on Experion-TPS nodes.

Attention
Starting with Experion R400, you can use the physical key switch to increase the current security access level on
Experion nodes.

5.13.2 Default access permissions

This Default access Is granted to Members of this Local Group… This Global Group is a member of the Local Group
level…
Engineer Local Engineers Domain\Engineers*
Supervisor Local Supervisors Domain\Supervisors*
Operator Local Operators Domain\Operators*
View Only Local View Only Domain\View Only*
* “Domain” represents the name of the user domain.

Prerequisites for establishing access permissions


The High Security Policy - Domain Controller Package is installed on the Domain Controller; this
installation creates Experion global domain user groups.
The High Security Policy - Workstation Package is installed on the Experion node being implemented. This
installation creates Experion local user groups and occurs during Experion node installation.
The Link Domain Groups application has been executed on the Experion node being implemented. This user-
run script establishes global group membership in the node's local groups.
For example, to configure a user “Joe” as an operator, the following steps must be taken:
1. Complete the steps defined in the Prerequisites to install the “High Security Policy.”
The workstation and domain controller “High Security Policy” packages create local and global domain user
groups. A command script establishes global group membership in the node's local groups.)
2. At the domain controller, create the Windows domain user accounts.
For example, “Domain\Joe.”
3. Add each account to be a member of a global domain group that was created in the High Security Policy
security model.
For example, add “Domain\Joe” account to be a member of the global domain group Operators.

94 www.honeywell.com
5 COMMON PLATFORM TASKS

Tip
Membership in each group also provides access to all lower levels.

1. Complete the definition of “Domain\Joe” account using the Experion Station System
Configuration>Operator Security>Operators page.
For example, define the access level for user account “Domain\Joe” as Operator.
For more information, see “Experion operator security requirements” on page 95.

5.13.3 Experion operator security requirements


Note the following security requirements.
You must use integrated accounts.
The access level must match local group membership.
The access level AckView is not supported on TPS/LCN.
The Experion MNGR access level should be mapped to the TPS/LCN ENGR access level through the local user
group membership (that is, users with MNGR access level should belong to the local Engineers group).
The ViewOnly access level will be obeyed automatically by the Experion and TPS faceplates. With Experion
R400/TPS R420, the VIEW and OPR access levels are applied to the Native Window irrespective of the value
in the CURRENT DEFAULT of the ACCESS CHANGE target. The status bar on the Native Window shows
VIEW for the View Only access levels.
“Use operator security” must be defined for ES-T nodes.
Operator security is recommended for ESVT nodes. You must use Quick Builder to define operator security for
an ESVT (Flex Station).
“Single signon” must be checked.
You must run the Link Domain Groups command if you are in a windows domain.
For more information about setting Operator Security, refer to the Server and Client Configuration Guide.

95
5 COMMON PLATFORM TASKS

96 www.honeywell.com
6 Configure Experion Database

97
6 CONFIGURE EXPERION DATABASE

6.1 Procedures included in this section

Attention
These procedures are to be used in conjunction with an installation checklist.

This section contains procedures related to configuring Multiple Experion clusters on one TPN (LCN). Please
refer to the checklist in Section 2: Supplementary Installation Tasks to determine when to follow each of these
procedures.
This section provides the following procedures.
Plan the partitioning of TPN units
Publication of the TPN System Alarm
Add Experion servers to EMDB
Configure DSA
Verify the unit mapping and the history collection configuration
Save TPS points configuration
Restore TPS points configuration
Remove mappings

98 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

6.2 Procedures in other publications


If you plan to use Distributed System Architecture (DSA), then see the “Configuring Distributed System
Architecture” section in the Client and Server Configuration Guide.

99
6 CONFIGURE EXPERION DATABASE

6.3 Procedure to integrate TPN Units into the Enterprise Model

Attention
Before you map TPS Units to Experion Assets during TPS System Interface configuration, you should first create
Assets using Enterprise Model Builder. See the following,
• “Planning Your Asset Model” in the Server and Client Planning Guide.
• “Creating and Configuring Assets” in the Enterprise Model Builder User's Guide.
Run the Enterprise Model Builder from Configuration Studio to do this task.

Configure Assets using Enterprise Model Builder as shown in the following figure. TPN Units can then be
mapped to Assets.

To integrate TPN Units into the Enterprise Model


1 Click Start > Programs > Honeywell Experion PKS > Configuration Studio to start Configuration
Studio.
• From Connect dialog, click the icon that represents the system of Experion nodes.
• Verify that the Experion Server for the target system supports the EMDB repository; that is, an
IsEMBDB = true indication appears.
• Click Connect.
• Type the user name and password.
User name/password must exist in the Experion operators' database.

100 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Attention
If system icons do not appear in the Connect dialog, then the station you are connecting from does not have
EMDB client capability. You will not be able to build assets from this station. If system icons do appear in the
Connect dialog, verify that the Experion server for the system is an EMDB repository so that you can build assets
as shown in the previous figure.

2 From Configuration Explorer, click the icon representing the target system.
3 From the System Tasks menu, select Configure Assets for this system to start Enterprise Model Builder.
4 Right-click the Assets icon and define a New Asset.
for more information about configuring asset properties, refer to the Enterprise Model Builder Guide.
5 Ensure that the new asset's alarming enable/disable property is checked if you wish to enable.

6 Load the new asset.


7 Define additional new assets as needed.

101
6 CONFIGURE EXPERION DATABASE

Attention
If direct TPS unit mapping is selected, then you will need to build assets that have the same two-character TPN
unit names as well as an SY named asset (see “Map TPS Units to Experion Assets” on page 109).

Stop
You have completed this task. Return to the checklist that led you to this task.

102 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

6.4 Procedure to configure TPS System Interface


1 From Configuration Studio, expand the Server.
2 Click System Interfaces and then click the Configuration tab. The System Interfaces display appears.
3 Click the TPS hyperlink in the Alias field:

Result: The System Interface display appears for the TPS Connection:

4 Select the appropriate configuration options in the Configuration tab.


Configuration Options: Choose the options for your site.

The following table describes the Configuration Options for the TPS Connection.

103
6 CONFIGURE EXPERION DATABASE

Configuration option Setting description


All TPS alarms are Selected (Enabled) Cleared (Disabled)
monitored by at least
If the check box is selected (default setting), If the check box is cleared then all the TPS
one Experion station
all the TPS alarms are monitored by at least alarms and messages viewed on the Flex
one of the Experion stations. stations are marked as Acknowledged as soon
as they are received.

Attention
You must disable this option, if the TPS
alarms are being generated in assets that
are not monitored by any of the
Experion stations.

Failover to Backup Selected (Enabled) Cleared (Disabled)


Server on TPS
In normal operation, this check box must If this check box is cleared, the state of the
communications
always be selected (enabled). When this check TPN Server connection does not cause the
failure if servers are
box is enabled, the Experion system server Experion system server to failover to the
synchronized
will failover to the backup in the following backup. For example, you may clear this
scenarios. check box when the LCN is being
disconnected from the server for a period of
If the Server is synchronized with the backup
time. However, the server continues to be
and active. This may be useful, for example, when
One of the following events occur: performing an online upgrade.

• The communication between the Experion


system and the TPN server is lost.
or
• The communication between the TPN
server and the TPS/LCN is lost.
The status “Servers synchronized” is a
requirement for the Experion system server
failover. When required, the engineer can
synchronize the Backup server with the
Primary through the redundant Server
configuration page. After synchronization,
any changes to the database of the Primary
server is transferred to the Backup server.
Use TPS Groups Selected (Enabled) Cleared (Disabled)
This check box is selected if the TPS groups This check box is cleared if the Experion
are used. groups are used exclusively for the TPN
points.
Use classic TPS If you create Experion groups containing TPS points, it is recommended that you do not select
faceplates and details the Use Classic TPS faceplates option, otherwise you may experience display problems.
on console stations
(does not affect Flex
stations)
Disable automatic Select the Disable automatic deletion of TPS points check box. If selected, the Experion
deletion of TPS points server and console stations do not delete TPS points from their databases even though the TPN
server communicates to the Experion server that the points no longer exist on the LCN.

104 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Configuration option Setting description


Scope of The Associated asset field is used to limit the operators or stations from seeing the TPS
responsibility - system interface in the Experion System Status display. Operators or stations that have access
Associated asset to the selected associated asset will see the TPS system interface in the Experion System
Status display. If you leave the associated asset field empty, the system alarms for this system
interface can be viewed by anyone who has access to the system alarms for the server on
which this system interface is configured.
Clicking the button opens up the Asset Model Browser. Assignable asset(s) that were
previously defined, using Enterprise Model Builder is shown in the Asset Model Browser.
Select the asset from the Asset Model Browser and click Apply.

Point Browser List Selected (Enabled) Cleared (Disabled)


If this check box is selected, Experion If this check box is cleared, the Experion
browses the address space of the TPN server, points cache is populated only with the TPS
populating the Experion tag cache. The points points that are already in the Experion
are not built into the point's heap (heap 1). database. The cache is populated with the new
They are only built into the tag cache (heap points as and when they are found.
9).
This feature must not be used in Experion
releases prior to R300 because it causes
Experion to timeout the TPN Server and drops
the data connection. In R300, the parallel
connection is used for browsing and hence
normal data requests are not interfered. This
approach of parallel connection loads the TPN
Server and the LCN. If the point browsing of
non-discovered points is not required, clear
this check box.
Update When clicked, the TPS points (that are not yet in the Experion point's heap) from the TPN
server are added to the Experion tag cache.

5 Click the Tuning tab.


Do not change the default values of the tuning parameters while configuring the TPS System Interface.

105
6 CONFIGURE EXPERION DATABASE

The tuning properties are automatically adjusted to be compatible with the server's global cache settings.
CAUTION
You can change the values if instructed by the Honeywell support personnel, or if you have extensive
experience with the system interfaces.

For more information about Tuning Properties, see the table in “TPS Connection - Tuning properties” on
page 106.
6 Click the Status tab.
The Status Display shows six green indicators for the TPS System Interface; if not, see the “Troubleshooting
Approach” section.
Notifications check box:
By default, this check box is not selected. Select this check box after mapping the Units. When this option is
enabled, Experion receives alarms/messages/events from the TPN server.

Attention
On each Experion cluster, ensure that the Notifications checkbox on the Status tab of the TPS Connection
display is not selected. Do not change this setting while configuring multiple Experion clusters on single LCN.

StopYou have completed this task. Return to the checklist that led you to this task.

6.4.1 TPS Connection - Tuning properties


The following table describes the tuning properties for a TPS connection.

Property Description
Data Settings
Cache flush time The intervals (in milliseconds) that the subscription list is checked for references to old data. The
default value is 1 second.
Cache age time The amount of time (in milliseconds) old data remains in the dynamic cache. The default value is 60
seconds on the ESVT nodes. Cache age time is 0 on the ES-T nodes, and cannot be changed.
Maximum The slowest subscription time (in milliseconds). The default value is 10 seconds. If the subscription
subscription time time is slower than that specified, the subscribing server switches from subscription to synchronous
read (polls). Maintaining a slow subscription is not efficient.
Connection The maximum time (in seconds) the Experion server allows for a data request to complete. If the
Timeout connection times out, a connection failure is recorded and a new connection is attempted. The default
value is 30 seconds.
List fragment The size of data packets sent over the network. The default is 500 parameter values. This is tuned for
size optimal performance on low bandwidth links.
Drift Deadband The TPS system only sends an updated value to the Experion server if the value has changed by the
deadband percentage since the last update. The default value is 0.00.
Notification Settings
Connection The amount of time (in seconds) a packet of data can remain on the network without being
timeout acknowledged. When the timeout period expires, the connection is broken and communication is
initiated again. The default value is 10 seconds.
Notification The maximum amount of time (in seconds) a notification can be delayed on the publishing server
buffer interval before being sent to the subscribing server. The default value is 2 seconds
Notification The maximum amount of time (in seconds) the publishing server does not send packets to the
keep alive subscribing server. If there are no notifications within this time, an empty keep-alive packet is sent to
interval the subscribing server. The default value is 15 seconds.

106 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Property Description
List Fragment The default value is 100 notifications.
Size

107
6 CONFIGURE EXPERION DATABASE

6.5 Procedure to add and configure Operators


This procedure is used for defining the operator security settings. ES-T requires the use of Signon Manager with
Operator-Based security using Integrated Windows accounts. Signon Manager is also used for controlling the
Native Window security level.

Tip
Before doing this procedure, you must add your operator to a Windows account.

To add and configure operators


1 From Configuration Studio, expand the Server of interest and select System Access.
2 Choose Configure operators and Windows group accounts.
3 For each operator, check Use Windows account.

Tip
The accounts were created on the domain controller and must also belong to the local user group, for example
Local Operators. The link between domain and local groups is established via the Link Domain Groups
command.

Attention
After creating the Assets, use the Operators Assignment tab to assign assets to Operators.

4 From the System Configuration Menu, select the Sign-on Administration menu and select Allow Single
Signon.
For more information about setting Operator Security, refer to the Server and Client Configuration Guide.

You have completed this task. Return to the checklist that led you to this task.
Stop

108 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

6.6 Map TPS Units to Experion Assets

6.6.1 Multiple Experion clusters on one TPN


To configure multiple Experion clusters on one TPN, you must map the TPN units to Experion assets using the
Map TPS Units as follows option in the Unit Mapping tab of the TPS Connection display.
For sites without an Experion cluster on a TPN,
• Configure multiple Experion clusters and on each Experion cluster, map the TPN units to Experion assets as
planned. For more information, see “TPS Connection - Tuning properties” on page 106.
For sites with an already existing Experion cluster on a TPN,
• Disable all the DSA subscriptions for data and alarms between the Experion clusters on the same TPN. Do
not change this setting while configuring multiple Experion clusters on a TPN.
The SY TPN unit must be mapped to a different asset for each Experion cluster on the TPN. For TPN units that
do not belong to an Experion cluster, the mapping for these units must be set to “Not Mapped” on that cluster.
After mapping all the TPN units (belonging to an Experion cluster) to Experion assets, enable notifications for
the TPS system interface by selecting the Notifications checkbox in the Status tab of the TPS Connection
display.

Attention
If you have C300 to HPM peer-to-peer communication happening via ESVT, the peer-to-peer communication
(especially with the TPS points in SCM transitions) does not automatically recover after remapping the TPS Units to
Experion Assets.

Attention
• Before you can map TPS Units to Experion Assets during TPS System Interface configuration, you must first
create Assets using Enterprise Model Builder.
• You must be logged on to the Enterprise Model Builder or Server's Station application with the ENGR or MNGR
security level to perform this task.
• MNGR password of the local account must be the same on all nodes in the ESVT cluster.

Procedure to configure system interfaces


1. From Configuration Studio, with the system's server of interest expanded, click System Interfaces.

109
6 CONFIGURE EXPERION DATABASE

Note: You can also configure System Interfaces from Station when you click System Status on the System
Menu and then click System Interfaces.
2. From the System Interfaces menu, click Configure system interfaces.

3. Select the TPS system interface.


4. Click the Status tab and disable Notifications, if enabled.
5. Click Unit Mapping tab and review the mapping options.
Note: Before you can map TPS Units to Experion Assets during TPS System Interface configuration, you
must first create Assets using Enterprise Model Builder.

6. Select the Unit Mapping option that you want to use to map TPS Units to Experion Assets.

Attention
Depending on your selected option, you will also need to account for the reserved TPN System Unit (SY) in your TPS
Unit to Asset mapping strategy. You map the SY unit, which is a TPN-system defined and reserved unit, so that you
can support system event journaling and silence synchronization from your Experion system.

The Unit Mapping options represent the following:

110 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Option Description
Map all TPS Units to Maps all TPS units (including the reserved TPN System Unit, SY) to the specified Experion
Assignable Asset Asset.
Note: Asset(s) that were previously defined using Enterprise Model Builder appear in the Asset
Model Browser.
Select the asset from the Asset Model Browser and click Apply.

A confirmation dialog box appears. Click Yes on the dialog box to continue. This moves the TPS
points to the specified asset.
Example usage scenario
TPS users with a small number of units or small LCN or users who do not need an Experion
alarm management strategy may consider selecting this option. This option is the easiest to
implement, but provides least flexibility of the 3 options.
Map to Assignable Automatically maps TPS units to Experion Assets with same user-defined names. For example,
Assets with the same Unit T1 is mapped to Asset T1.
name as TPS Units
Note: You must build an Asset named “SY” in order the reserved TPN System Unit (SY) to be
(direct mapping)
directly mapped.
Example usage scenario:
TPS users with a single LCN who want their operators to support a similar alarm management
strategy from Experion as on the LCN may consider selecting this option.

111
6 CONFIGURE EXPERION DATABASE

Option Description
Map TPS Units as Individually map TPS units to Experion Assets.
follows
Note: Asset(s) that were previously defined using Enterprise Model Builder appear in the Asset
Model Browser. Although a user-defined Asset named “SY” is not required, you must still assign
TPN System Unit (SY) to a user-defined Experion Asset. Note that the default selection for TPN
System Unit (SY) is “Not Mapped”.
Select the asset from the Asset Model Browser and click Apply (Refer to the screen capture in
“Map all TPS Units to Assignable Asset”).
A confirmation dialog box appears. Click Yes on the dialog box to continue. This moves the TPS
points to the specified asset. Example usage scenario:
TPS users with a large number of units, large LCN, multiple LCNs, or users who want a
hierarchical alarm management strategy may consider selecting this option. If you are connecting
multiple LCNs to an Experion system using DSA, you must select this option This option
provides the most flexibility of the 3 options.

Attention
When you attempt to change the Map TPS Units as follows option to Map all TPS Units to Assignable Asset
option, a confirmation dialog box appears. Click Yes on the dialog box to continue.
Note that this action would result in TPS points being deleted, creating a momentary Loss of View until all the TPS
points are rediscovered.

1. After completing Unit Mapping, check that Notifications is Enabled on the Status tab. If it is not checked,
alarms from TPS will not be displayed.

See “Mapping of TPS/LCN Units to Experion Assets” on page 242 for special mapping considerations when
more than one LCN is connected to an Experion system using DSA.

Tip
The LCN points and the parameters name must adhere to the Experion point and parameter naming rules.

For more information about the naming rules for the points and parameters, refer to the following sections in the
Quick Builder Guide.
• Naming rules for points
• Naming rules for user-defined parameters

112 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

6.6.2 Configuration example


The following figure shows an example of individually mapped TPS Units to Experion Assets. The TPS Units
that appear in the Unit Mapping tab are initially discovered by a running TPN Server.

6.6.3 SY Unit mapping to Assets


The reserved TPS system unit SY supports system event journaling and silence synchronization. Depending on
the mapping option you choose, you must map the SY system unit to an Asset. You build assets, including an
SY Asset if necessary, using Enterprise Model Builder.

113
6 CONFIGURE EXPERION DATABASE

Map all TPS Units to Assignable Assets


When selecting this option, all user defined TPS units (including the reserved TPS System Unit, SY) are
assigned to one selected Asset.

Map to Assignable Assets with the same name as TPS Units (direct mapping)
When selecting the option, use the Units from the TPS connection as areas (direct mapping). All user-defined
TPS Units are assigned to similarly user-defined Experion Assets. You must build and name Experion Assets to
have the same 2 character names as each of one of your TPS units. You must also build an Experion Asset
named SY to support the TPS reserved system unit, SY.

Map TPS units as follows option


When selecting the option, Map TPS units as follows, all user defined TPS units are assigned to user defined
Experion Assets. You can name your Assets to have unique names representing LCN Areas, TPN Units, or
other plant organizations (for example, Reactor1, Boiler 2). Note that you must also map the TPS reserved
system unit, SY, to an Experion Asset of your choice. The Experion Asset for this option does not need to be
named SY, but you must not leave the TPS reserved system unit, SY, unmapped.

114 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Tip
The unit names on the left are directly obtained from the TPS/LCN.

Stop
You have completed this task. Return to the checklist that led you to this task.

115
6 CONFIGURE EXPERION DATABASE

6.7 Procedure to add Experion Console


Use Configuration Studio with ENGR or MNGR security level to perform this task.

Attention
For more information about the console configuration details, refer to the Server and Client Configuration Guide.

1 From Configuration Explorer, with the system's server of interest expanded, click Stations and Consoles.
2 From the Stations and Consoles menu, click Configure consoles.
3 From the Consoles listing, click a blank line.

4 From the Detail tab, define a console name.

5 Complete the remaining configuration choices on the Detail, Options, and Assignment tabs. Refer to the
Server and Client Configuration Guide for configuration information.
6 Repeat this procedure for each console.

116 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Attention
The node must belong to one Experion Console. The Experion Console and TPN Console should have a one-to-
one relationship. In other words, an Experion Console may not span across multiple TPN Consoles. An Experion
Console should be created to match the TPN Console and the ES-T can be added to this Experion Console.

Stop
You have completed this task. Return to the checklist that led you to this task.

117
6 CONFIGURE EXPERION DATABASE

6.8 Procedure to add Console Station


Use Configuration Studio with ENGR or MNGR security level to perform this task.

Attention
Ensure that each node is added to its matching Experion Console.

1 From Configuration Explorer, with the system's server of interest expanded, click Stations and Consoles.
2 From the Stations and Consoles menu, click Configure console stations.
3 From the Consoles Stations listing, click a blank line.
4 From the Detail tab:
• Type the Network Name for the Experion Station.
• Assign any extension stations to this station (refer to next procedure).
• Select a console name from the drop down list.

Attention
The default Normal update rate is 1 sec. To decrease the load on the LCN, you should consider setting this rate to
4 seconds.

5 Review the listing of Console Stations


Result: The Console Station appears in the list along with its IP address

Attention
If an IP address does not appear, you will not be able to establish communication between the server and station or
complete the TPS/LCN integration. To resolve this situation, review your hosts file setup and computer name entry
for accuracy.

6 Repeat this procedure for each ES-T.

Stop
You have completed this task. Return to the checklist that led you to this task.

118 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

6.9 Support Remote GUS with Console Extensions


To support Experion Remote GUS Displays, you must add Experion Stations as Console Extensions to host an
ES-T.
Use Configuration Studio with ENGR or MNGR security level to perform this task.
1 From Configuration Explorer, with the system's server of interest expanded, click Stations and Consoles.
2 From the Stations and Consoles menu, click Configure console stations.
3 From the Consoles Stations listing, click a Console Station.
4 From the Detail tab:
• Assign any extension stations to the host station. Extension stations are required if you wish to use
Remote GUS Displays with Experion.
• Complete remaining extension configuration.

Refer as needed to the Server and Client Configuration Guide for additional console information.
5 Repeat this procedure for additional consoles.

Stop
You have completed this task. Return to the checklist that led you to this task.

119
6 CONFIGURE EXPERION DATABASE

6.10 Specify Station Toolbar Definition (.stb) File

6.10.1 Experion Station Toolbar Definition Files


Experion Stations use Station toolbar definition (.stb) files to define the actions of the keyboard. Several .stb
files are installed on the ES-T, including the following:
• ikb-ES-T.stb (for the Integrated Keyboard)
• icon-ES-T.stb (for the OEP on the Honeywell Icon Series Console)
• ikb-est_Multiwindow.stb (for the Integrated Keyboard with Multiple Displays)
• icon-est_Multiwindow.stb (for the OEP on the Honeywell Icon Series Console with Multiple Displays)
The above files are similar to the standard files, except that the definitions for user-programmable keys are
removed and the default processing of the user-programmable keys is left to the Native Window (as defined by
the TPS/LCN Area Button Configuration (.KS and .KO) files. This ensures that, by default, the user
programmable keys and LEDs on a Station will operate according to the Button Configuration file of the
TPS/LCN Area installed on the station.

6.10.2 Customizing the file


All .stb files are customizable by the user. The initial files are only starting templates. It is possible to mix
processing of the user-programmable keys, leaving some unconfigured in the .stb file, to be processed by the
Native Window Button Configuration file; and configuring others to be processed by the Experion Station
application.

Attention
If a given user-programmable key is included in the current .stb file (Connection Properties, Toolbars tab), then it is
“owned by Station”. If this key is not in the .stb file, then it should be considered “owned by Native Window” and
should be left for Native Window to control.
The standard (Rxxx) ikb.stb and icon-ES-T.stb toolbar files are examples in which Station owns all user-programmable
keys. The ikb-ES-T.stb and icon.stb are examples in which the user-programmable keys are omitted, thus Native
Window owns all these keys, allowing Native Window to retain ownership of these keys and LEDs by default. Users
can edit these files and save-as to configure the desired mix of both native Window and Station-owned user-
programmable keys.
When Native Window has access to one or more user-programmable IKB/OEP buttons with LEDs, the Experion
system will allow Native Window to update the LEDs of these buttons. In this case, you should avoid configuring the
Experion system to also control these same particular LEDs (for example, by using the Operator Keypad tab for
Console Station configuration), because if both Native Window and the Experion system attempt to control an LED,
the behavior will be unpredictable.

6.10.3 Specifying the .stb file


As part of configuring the connection for the ES-T, indicate the type of keyboard being used and select one of
the keyboard template files provided by the installation. Perform the following steps to specify the ES-T button
configuration file.

To specify the .stb file


1 Select Station > Connection Properties > Toolbars.
2 Browse to Program Files > Honeywell > Experion PKS > Client > System > Rxxx.

120 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Attention
• With Experion R410, 64-bit OS is supported. All 32-bit components are installed in C:\Program Files (x86).
The default path for installation of Experion PKS is C:\Program Files (x86)\Honeywell\Experion PKS.
• The Custom Install Path (CIP) is supported in Experion R410. You can choose any possible path for
installation (for example, D:\TEST\Honeywell\Experion PKS).

3 Select the appropriate .stb file in the Menu, toolbar & keyboard shortcuts as shown below.

For more information, see the Server and Client Configuration Guide.

121
6 CONFIGURE EXPERION DATABASE

6.11 Configure Audible Annunciation

Attention
Use of the Audible Suppress option (the target that is labeled AUDIBLE) on the TPS/LCN Alarm Summary display is
not recommended on ES-T nodes.
Experion supports suppressing audible annunciations on the Experion Alarm Summary display.
With Experion R410, a system wide setting is available to enable or disable the audible suppression and can be used
for setting the highest priority audible alarm.

Attention
Alarm shelving is a form of manual suppression that enables operators to remove alarms from the main alarm
summary displays for a limited time. The following table summarizes the scenarios in which the alarm shelving can be
used on an ES-T.
For example, in the first row, if the console station contains ES-T and GUS and the annunciator is connected to ES-T
and GUS, then you cannot use alarm shelving.

Console contains: Annunciator connected to: Can use alarm shelving?


ES-T US/GUS ES-T US/GUS
Yes Yes Yes Yes No
Yes Yes Yes No Yes
Yes Yes No Yes No
Yes Yes No No Yes
Yes No Yes N/A Yes
Yes No No N/A Yes
No Yes N/A N/A N/A

In order for TPS/LCN alarms to be processed correctly by the Experion alarm subsystem, the NCF and the
Experion configuration must be aligned. The contacts for horn annunciation of alarm priorities must be set the
same in the NCF and in Experion.
Do one of the following procedures based on whether an IKB is present on the ES-T.

6.11.1 Procedure to be followed when the IKB is present


1 Start the Experion Station application and go to Station > Connect > Edit Connection.
2 Click the Sounds tab.
3 Select the Use keyboard contact check box.

Attention
The Use keyboard contact portion of the dialog box will not appear until the IKB Service is installed and running.
(The IKB Service can be installed from the Experion Application DVD, IKB OEP Package.)

4 Uncheck the Use PC Speaker and Use external contact check boxes.

Tip
Checking the Use PC Speaker specifies if the audible alarm is generated through the speakers on the computer
Station is running on.
Checking the Use external contact option specifies if the audible alarm is generated through an external
annunciator.

122 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

5 Select an Event (Urgent Priority Alarm, High Priority Alarm, Low Priority Alarm, Urgent Priority System
Alarm, High Priority System Alarm, Low Priority System Alarm, Confirmable message, Informational
message, Alert, TPS System Status Indicator or TPS Console Status Indicator), and then select a contact
from the Keyboard Contact for selected event dropdown list to align it with the NCF configuration.
Shown below is an example Experion configuration that aligns with the following NCF configuration
example. For addition NCF information, refer to section “Additional NCF Considerations.”
Example Experion Configuration:

Example NCF Configuration:

123
6 CONFIGURE EXPERION DATABASE

6 Verify that you have activated corresponding alarm selections in Experion.

124 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Stop
You have completed this task. Return to the checklist that led you to this task.

6.11.2 Procedure to be followed when IKB is not present


1 Start the Experion Station application and go to Station > Connect > Edit Connection.
2 Click the Sounds tab.
3 Select the Use PC Speaker check box.
4 Uncheck the Use external contact check box.

Tip
Checking the Use external contact option specifies if the audible alarm is generated through an external
annunciator.
The Use keyboard contact portion of the dialog box will not appear.

5 Select an Event (Urgent Priority Alarm, High Priority Alarm, Low Priority Alarm, Urgent Priority System
Alarm, High Priority System Alarm, Low Priority System Alarm, Confirmable message, Informational
message, Alert, TPS System Status Indicator or TPS Console Status Indicator), and then select a sound from
the Sound for selected event dropdown list.
Example Experion Configuration:

125
6 CONFIGURE EXPERION DATABASE

6 Verify that you have activated corresponding alarm selections in Experion.

126 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

Stop
You have completed this task. Return to the checklist that led you to this task.

127
6 CONFIGURE EXPERION DATABASE

6.12 Support TPS on Console Station Extension


ES-CE with TPS Extension is a “marriage” of ES-C and Remote GUS Displays. Functions dependent on the
presence of an LCNP are limited in Remote GUS Displays, and those limitations exist in ES-CE with the TPS
Extension. On ES-CE with TPS Extension (as in a Remote GUS Displays “cluster”), the Native Window can be
active on only one of the stations in an ES-T or ES-CE with TPS Extension “cluster” at any given time.

6.12.1 Native Window Displays


Native Window displays can be invoked only on the Station that currently has possession of the Native Window.
Attempts to invoke Native Window displays will fail on other stations. This also applies to TPN Detail Displays
and Native Window Group Displays. Unlike the ES-T, it is not possible for GUS or HMIWeb displays to invoke
Native Window displays, and vice versa. (This behavior is the same as Remote GUS.)

6.12.2 TPN Faceplates and Group Displays


HMIWeb faceplates for TPN points, HMIWeb detail displays for TPN points and HMIWeb group displays
based upon them, will run on ES-CE with TPS Extension.
GUS faceplates and group displays will run on ES-CE with TPS Extension.
Native Window group displays will run only if the station currently possesses the Native Window. Also, they
cannot be invoked from a GUS or HMIWeb display.

6.12.3 GUS Displays


GUS displays will function on ES-CE with TPS Extension just as they do on Remote GUS Displays.

6.12.4 IKB
The remote GUS Display package currently does not support the IKB. An ES-CE with TPS Extension will
support the IKB in the same way that ES-CE does. Experion components will “own” the IKB on ES-CE with
TPS Extension. (Note that this section describes the behavior of the IKB/OEP on the ES-CE with TPS
Extension, which will differ in some aspects from the behavior of the ES-T).
Hot Keys: Hot keys for the ES-CE with TPS Extension will behave in the same way as for an ES-T (see below),
with the following exceptions:
• User Configured Keys: All User Configured Keys are controlled by the Experion system. The user will
configure the lights and the response to a key press using existing Experion system configuration functions.
The key configuration will be on a per-station basis and will not change when the TPN Area is changed.
• CONS STATS: On the ES-CE with TPS Extension, this key is owned exclusively by Experion system and
invokes the Experion system Console Status Display. This differs from the ES-T, where it is shared by
Experion system and the Native Window.
• GROUP: Will invoke an HMIWeb Group Display or a GUS Group Display, depending on configuration.
• SCHEM: If no HMIWeb or GUS display with the specified name is available, an error indication is
returned.
SIL: Silences alarms on all stations (ES-T, ES-CE with TPS Extension, in the console, if so configured. This
occurs when the SIL key is pressed on any station in the console. SIL key behavior must be configured in both
the LCN (NCF) and the Experion system, as described in “Additional NCF Considerations” in this document
and in the Experion Server and Client Configuration Guide. Note that if a GUS or US is configured with a

128 www.honeywell.com
6 CONFIGURE EXPERION DATABASE

different TPN Area from that configured on the silencing station, the alarm will not be silenced on that station
(with the differing Area).
• SYST STATS: On the ES-CE with TPS Extension, this key is owned exclusively by Experion system, and
invokes the Experion System Status Display. This differs from the ES-T, where the key is shared by
Experion system and the Native Window.
Context Specific Keys: Inputs from context specific keys are passed to the window that currently has focus,
GUS display, HMIWeb display, or Native Window. These keys are fully functional for Native Window. Certain
keys (for example, ramp keys) will be limited in GUS displays (just as they are on Remote GUS Displays).
Specific limitations will be described in the user documentation. Refer to Experion system documentation for a
description of the functionality provided by the context specific keys when a window presenting an HMIWeb
display has focus.
Annunciation via IKB: Annunciation via the IKB, IKB contacts, and PC speakers on the ES-CE with TPS
Extension will behave in the same way as for ES-T
(see “LED annunciation”), with the following exceptions.
• User Configured Keys: Annunciations are driven exclusively by Experion system.
• Console Status: Annunciation is driven exclusively by Experion system on an ES-T and ES-CE with TPS
Extension.
• System Status: Annunciation is driven exclusively by Experion system on an ES-T and ES-CE with TPS
Extension.

129
6 CONFIGURE EXPERION DATABASE

130 www.honeywell.com
7 Multiple Experion Clusters on one LCN

131
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.1 Procedures included in this section

Attention
These procedures are to be used in conjunction with an installation checklist.

This section contains procedures related to configuring Multiple Experion clusters on one TPN (LCN). Please
refer to the checklist in Section 2: Supplementary Installation Tasks to determine when to follow each of these
procedures.
This section provides the following procedures.
Plan the partitioning of TPN units
Publication of the TPN System Alarm
Add Experion servers to EMDB
Configure DSA
Verify the unit mapping and the history collection configuration
Save TPS points configuration
Restore TPS points configuration
Remove mappings

132 www.honeywell.com
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.2 Plan the partitioning of TPN units


You must consider the following factors while planning for the partitioning of TPN units amongst the Experion
clusters.
Impact of loss of view of the TPS points: There could be a loss of view of the TPS points owned by any one
cluster over the DSA due to the planned upgrades, routine maintenance, or unplanned shutdowns. When a
cluster is unavailable, the points from the TPN units mapped on that cluster are not available to other clusters
even though they reside on the same TPN. The only TPS point data and alarms directly available to the ES-T
from the TPN are from those TPN units mapped on the local Experion cluster. Data from other TPN units are
retrieved through DSA. When the ES-T is in degraded mode, data from TPN units retrieved through DSA are
not available.
Logical distribution of the TPN points: The importance of a logical distribution of the TPN units amongst the
Experion clusters in terms of geographical location and/or area of control.
Loading/distribution of history collection of the TPS data: If the TPS point belongs to a TPN unit that is
mapped to an Experion asset on a cluster, then configure the history collection from the TPS point on that
Experion cluster.
Distribution of ESTs: The distribution of ESTs amongst clusters for more number of ESTs.
Limitations on TPN operations: There are certain limitations on TPN operations for data and alarms accessed
over the DSA from another Experion cluster. These limitations are applicable to remote TPN operations
performed on all the nodes in an Experion cluster that are accessing TPN data and alarms from another cluster
through DSA. For more information about the limitations, see “Remote TPN Operations using Flex Stations”.
Mapping TPN units to Experion assets: If EUCN is integrated with Experion network, ensure that all TPN
units in which EHPM points reside, must have assets defined in the Experion EMDB, and units mapped to
Experion assets in the same ESVT cluster.

Attention
While identifying the TPN units to be mapped to the Experion clusters, you might decide to move TPS points from
one TPN unit to another TPN unit. Regrouping TPS points should be completed before starting the procedure.

7.2.1 Planning the partitioning of TPN units for multiple Experion clusters
You must plan the partitioning of the TPN units (and the points within each unit) amongst the multiple Experion
clusters. Identify the TPN units that must be mapped to the assets on each Experion cluster on the same TPN.
Each TPN unit can only belong to one Experion cluster. In other words, if a TPN unit is mapped to an asset on
one cluster, then the TPN unit must not be mapped to any assets on any other clusters. The TPS points that
belong to a mapped unit on a cluster are owned by that cluster. Access to these points from another cluster is
available only through the DSA.
The SY TPN unit is an exception to the rule above, and it must be mapped to each Experion cluster. In addition,
the SY TPN unit must be mapped to a different asset on the clusters. For example, if the SY TPN unit is mapped
to asset SY1 in Cluster1, then in Cluster2 the SY TPN unit must be mapped to a different asset such as SY2.
Honeywell recommends you to create new assets to map the SY TPN unit on each cluster. The assets must be in
a meaningful hierarchical structure. For example,
Create an assignable asset “Cluster1” and an assignable asset “SY1” as a child asset to “Cluster1”.
Create an assignable asset “Cluster2” and an assignable asset “SY2” as a child asset to “Cluster2”.
On Cluster1, map the SY TPN unit to the asset “Cluster1\SY1”.
On Cluster2, map the SY TPN unit to the asset “Cluster2\SY2”.

133
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.2.2 Rules for mapping TPN unit to an asset on one Experion cluster
The following table lists the rules to be followed while mapping the TPN unit to an asset on one Experion
cluster.

Rule Rationale
If a TPN unit is mapped to an asset on one Experion cluster, If this rule is not followed, duplicate alarms are raised for
that same TPN unit must not be mapped to an asset on any the TPS points as the Experion clusters are connected
other Experion clusters. through DSA.
For example, assume point FIC1001 is in unit U1 and unit
U1 is incorrectly mapped to:
asset A1 on Cluster1
asset A2 on Cluster2
If there is an alarm on FIC1001, then alarms are raised on
both Cluster1 and Cluster2, one in A1 and one in A2.
If the same TPN unit is mapped to the same asset on two or
more Experion clusters connected through DSA, it can also
result in item name clash between the clusters for points in
that TPN unit.
The SY TPN unit must be mapped to each Experion cluster. On following this rule, the annunciation events are received
In addition, it must be mapped to different assets on each to allow silencing function to work on each Experion
Experion cluster. cluster. When a TPN system event is received by Experion,
a point is created in the Experion database. Mapping the SY
unit to different assets on each cluster avoids item name
clash between the Experion clusters connected through the
DSA for TPS points in the SY TPN unit.
If EUCN is integrated with Experion network, ensure that If this rule is not followed, the standard history for these
all TPN units in which EHPM points reside, must have EHPM points cannot be collected through CDA.
assets defined in the Experion EMDB, and units mapped to
Experion assets in the same ESVT cluster.

134 www.honeywell.com
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.3 Publication of the TPN System Alarm

Attention
The TPN system alarm has been replaced by TPS System Status and TPS Console Status indicators in the Experion
Station status bar. It is recommended to disable the TPN system alarm. This section is only applicable to users who
want to continue to use the TPN System Alarm.

7.3.1 Configuring publication of the TPN System Alarm


The system must be configured to support the System wide System Event Server (SES) alarms scope. The SES
hosted on the ESVT in each Experion cluster is responsible for collecting the SES alarms from its own cluster.
For more information, see the “Configuring System Event Server and System Management Multicasts” topic in
the “Configuring system performance and event monitoring” section of the Server and Client Configuration
Guide.
In Experion, a consolidated TPN System Alarm is raised to alert the operators of a problem with a TPS system
component. This alarm is a consolidation of all the outstanding TPN system alarms sent by the System Event
Server (SES). With multiple Experion clusters on a single TPN, a TPN System Alarm is reported by each of the
SES in the system. This results in each cluster receiving its own instance of a TPN System Alarm. If these
systems are connected together with DSA then you will see multiple instances of the same TPN system alarm.
There are two approaches to avoid seeing duplicate TPN System Alarms.
Configure only one Experion cluster in the system to report the TPN System Alarm, and all other clusters in the
system not to report the TPN System Alarm.
Configure each Experion cluster on the LCN not to subscribe to any network tree alarms from any other
clusters. Network tree alarms in each Experion cluster remains in that cluster.

Approach 1: Configure one cluster to report the TPN System Alarm


With this configuration, the TPN System Alarm will only be reported by the machines from one cluster. This
alarm can then be accessed through the DSA by other Experion clusters.
You must nominate only one cluster in your system for the purpose of publishing the TPN System Alarms.
You must disable the TPN System Alarm on all the ES-T nodes in the other clusters in the system using the
System Management Configuration Utility.
Perform the following steps, to disable the TPN system alarm.
1. Select an ES-T node from an Experion cluster that is not nominated for publishing the TPN System
Alarm.
2. From the System Management Configuration Utility, choose Configure >Board 0.
3. Click the LCNP tab.
4. Under Experion TPS System Alarm, click <Disable>.
5. Click OK.

Approach 2: Disable DSA subscriptions to network tree alarms between clusters


With this configuration, each Experion cluster on the TPN is responsible for managing the network tree
alarms from its own cluster, and does not subscribe to network tree alarms from other clusters. A TPN
System Alarm is reported by each of the SES to its respective Experion cluster, and the alarm is not
published through the DSA to other clusters.

135
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

Tip
Disabling DSA subscriptions to network tree alarms between clusters disables the TPN system alarm and all
network tree alarm subscriptions. It also indicates that nodes monitored by another cluster do not appear in
the network tree on the local cluster.

If approach 2 is chosen, there is nothing to do at this step.

136 www.honeywell.com
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.4 Add Experion servers to EMDB

7.4.1 Define Experion clusters in your Enterprise Model


All Experion clusters on the same TPN must be configured to belong to the same Enterprise Model system. This
ensures that all Experion clusters on the same TPN share the same assets. It also allows the alarms, including
the SES alarms, to be exchanged between the clusters in the same system over the DSA. The Inter-system SES
alarms, where SES alarms are visible from machines from another system, are currently not supported.
Refer to the Enterprise Model builder User's Guide to perform the following:
• To configure the Experion clusters on the same TPN to be in the same Enterprise Model system
• To define the servers that are to be connected through DSA.

Attention
If using multiple ESVTs on a single LCN, the subscriptions for the data and the alarms between the Experion clusters
are disabled by default, immediately after defining the Experion clusters in the Enterprise Model system. Do not
change this setting at this stage.
For multiple ESVTs on a Single LCN, all Experion clusters on the same TPN must be configured to belong to the
same Enterprise Model system.

137
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.5 Configure DSA

7.5.1 Configuring DSA and data subscriptions between the Experion clusters
You must configure each Experion cluster in your system to subscribe to alarms and data from the other clusters
that you have defined in the Configuration Studio (see “Add Experion servers to EMDB” on page 137).
To configure an Experion cluster to subscribe to alarms and data from another cluster, perform the following
procedure.
1 Choose Start > Programs > Honeywell Experion PKS > Configuration Studio.
Note: Ensure that Station is running.
2 Click Distributed Servers in the tee view.
3 Click View distributed servers.
The Distributed Server Configuration Summary display lists all the Experion clusters defined in the
Configuration Studio.
4 Click one of the Experion clusters. The Distributed Server Configuration detail display appears.
5 Click on the drop down combo box under the heading Alarms and Data Subscriptions, and select “Enable
both Alarm and Data”.
Note: The option is available only when the DSA connection is configured.
If using multiple ESVTs on a single LCN:
The TPN system alarm has been replaced by TPS System Status and TPS Console Status indicators in the
Experion Station status bar. It is recommended to disable the TPN system alarm. The following steps are
only applicable to users who want to continue to use the TPN System Alarm.
If you follow Approach 1 in the “Publication of the TPN System Alarm”, ensure that the “Also subscribes
to: Network Tree” checkbox is selected.
If you follow Approach 2 in the “Publication of the TPN System Alarm”, ensure the “Also subscribes to:
Network Tree” checkbox is cleared. You must perform this on all clusters, and for each DSA connection to
the other clusters.

138 www.honeywell.com
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.6 Verify the unit mapping and the history collection configuration

7.6.1 Commands for verification


The following Table lists the commands to verify the unit mapping and the history collection configuration. Run
the commands in a command prompt and follow the recommendations suggested by the tool.

Command Purpose
chkem /tpsmappings Run this command on the ESVT in each Experion cluster. This identifies all the TPN
units mapped on the local cluster that are also mapped on another Experion cluster. With
the special case of the SY unit which must be mapped to different assets on each
Experion cluster, the tool indicates if on another Experion cluster it has been mapped to
the same asset. The tool also gives an error if the SY unit is not mapped on the local
Experion cluster.
chkem /tpspoints Run this command on all ES-T and ESVT nodes of each Experion cluster. This checks if
the TPS points have been built with the correct point types corresponding to whether
they are owned by the local or a remote cluster. If there are any TPS points identified
with incorrect point types, it may indicate the TPS unit mappings are incorrect.
chkem /tpshistory Run this command on the ESVT in each Experion cluster. This identifies all the TPS
points owned by a remote cluster which had been configured for history collection on
the local cluster. These TPS points need to be removed from history collection on the
local cluster.

139
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.7 Save TPS points configuration


You must retain the configuration information of the TPS points that are to be moved to one of the additional
Experion clusters.
TPS points mapped to the existing cluster.
The planned TPS points to be mapped to a new cluster.
This enables you to apply the same configuration easily on the new cluster(s).

Tip
If you remove a unit mapping on the existing Experion cluster, the points in that TPN unit is deleted from the
Experion PKS point database on that cluster. The configuration information associated with the points is also
deleted.

The following configuration information must be considered.


Trends and groups
History and history archiving
Point Scripts
Alarm groups
Algorithms
Operator keyboards
OPC Integrator

Trends and groups


1 There is a possibility that some or all of the TPN points previously configured in a group or trend on the
existing Experion cluster will be owned by the new clusters to be added to the same TPN. Therefore, the
points from the existing cluster are deleted. While an existing TPS point is deleted from the Experion point
database, it is also automatically deleted from any group or trend it belongs to. You must collect the point
configuration from each configured trend and group before deleting/removing the unit mappings on the
existing cluster. Later on, this allows you to reconfigure the same trend or group with the same points on the
new clusters.
2 To collect all the point configuration information for trends and groups configured, run the following
command on the existing Experion cluster.
3 bckbld -out TrendsGroupsConfig.pnt -np -tag PSA -nh
4 Backup the TrendsGroupsConfig.pnt file. Note that not all the points in this output will be TPS points.

History and history archiving


1 The on-line history will be lost for points that are deleted from the existing Experion cluster. If you need to
keep the history of the points being moved to one of the additional Experion clusters, then you need to
follow the procedure to archive the history files.
2 You should only configure history collection from a TPS point on an Experion cluster, if that TPS point
belongs to a TPN unit that has been mapped to an Experion asset on that cluster. You will need to collect
which points are configured in history collection on the existing cluster, if you want to configure the same
points in history on the new clusters on the TPN.
3 To collect all the history assignments for all the points, run the following command on the existing Experion
cluster.
4 bckbld -out HistoryAssignment.pnt -np -tag PSA -ng -nt
5 Backup the HistoryAssignment.pnt file. Note that not all the points in this output will be TPS points.

140 www.honeywell.com
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

Point Scripts
1 TPS point scripts are created and edited in Station. While a TPS point is deleted from the Experion point
database, the associated point script is deleted. Before removing the unit mappings from the existing
Experion cluster, collect all the scripts that are built on the TPS points. This enables you to attach these
scripts on the same TPS points after they are hosted on the new clusters.
2 To collect the point scripts, run the following command on the existing Experion cluster.
3 bckbld -tag PSA | findstr SCRIPT > PointScripts.pnt
4 Backup the PointScripts.pnt file. Note that not all the points in this output will be TPS points.

Alarm groups
• Some of the TPS points that must be moved to the new Experion clusters on the TPN might be referenced in
the Alarm Groups. While a TPS point is deleted from the existing cluster, it is removed from the Alarm
Groups to which it belongs to. Alarm Group configuration is already stored in the Configuration Studio and
therefore no need to backup this information.

Algorithms
• Points that must be deleted from the existing cluster might be referenced in other point algorithms.
Therefore, scanning must be disabled for the point before deleting the referenced point.

Operator keyboards
• Sites using the IKB or OEP keyboards can map the points to the LEDs. While an alarm is raised for the
point, the associated operator keyboard LED shows the highest priority alarm. This mapping is done on the
basis of the point number, which changes as a result of the TPS point being deleted from the existing cluster
and added on the new clusters. To save the mapping information, identify which point is assigned to which
LED before deleting the TPS points. The mapping is performed on the Flex stations, Console Stations, and
Consoles.

OPC Integrator
• If a point, moved to the new clusters on the TPN, is assigned to an OPC Integrator group on the existing
cluster, then disable the OPCI group to which the point belongs to. Identify the point and the parameters, and
later on, reconfigure the OPCI group. For more information, see “Apply configuration information to the
TPS points” on page 142.

141
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.8 Restore TPS points configuration

7.8.1 Configuring the history collection and the point scripts for the TPS points
Configure the history collection and the point scripts for the TPS points that are now on the new Experion
clusters.

History and history archiving


1 As mentioned in “Configuring history collection for TPS points” on page 305, configure the history
collection only from a TPS point on an Experion cluster which owns the TPS point. If you need to access
history from the points that have been moved to one of the additional Experion clusters, you need to restore
the history archives (taken in the “Save TPS point configuration” procedure) on the new cluster server that
owns the point.
2 To configure the history collection for the TPS points that are now hosted on the new Experion clusters,
perform the following steps.
3 Copy the HistoryAssignment.pnt file collected (as mentioned in “Save TPS points configuration” on
page 140) to each of the new clusters.
4 On each new cluster, open the file and identify the TPS points belonging to that cluster, and delete the lines
for all other points.
5 Run the command: “pntbld HistoryAssignment.pnt”.

Point Scripts
1 To attach the previously saved scripts (as mentioned in “Save TPS points configuration” on page 140) to the
TPS points now hosted on the new Experion clusters, perform the following steps.
2 Copy the PointScripts.pnt file collected (as mentioned in “Save TPS points configuration” on page 140) to
each of the new clusters.
3 On each new cluster, open the file and identify the TPS points belonging to that cluster, and delete the lines
for all other points.
4 Run the command: “pntbld PointScripts.pnt”.

7.8.2 Apply configuration information to the TPS points


After moving the TPS points to the newly created Experion clusters, apply the previously collected
configuration to those TPS points.

Trends and groups


1 To configure a trend or group on any Experion cluster in the system with the same TPS points and the
parameters that were previously configured in a trend or group on the existing cluster, perform the following
steps.
2 Copy the TrendsGroupsConfig.pnt file (collected in “Save TPS points configuration” on page 140) to the
cluster where you want to configure the same trend or group as before.
3 Open the file and identify the TPS points that must be included in a trend or group on the cluster, and delete
the lines for other points.
4 Run the command: “pntbld TrendsGroupsConfig.pnt”
5 This assigns the TPS points to be in the same position and in the same trend or group number as they were
originally configured on the existing cluster. A trend or a group might now consist of a combination of
points from the local server and the points from the remote DSA servers.

142 www.honeywell.com
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

Alarm groups
• To ensure the Alarm Groups contain the correct TPS points, open the Configuration Studio and download
the Alarm Groups again to all Experion clusters in the system.

Operator keyboards
• Apply the IKB or OEP keyboard LED mappings that were noted down in “Save TPS points configuration”
on page 140 to each Experion cluster as needed.

Algorithms
• Any algorithms on the existing Experion cluster referencing the TPS point (that was removed) must be
reconfigured to use the new point before scanning is re-enabled.

OPC Integrator
• For any OPCI group that was disabled in “Save TPS points configuration” on page 140 on the existing
Experion cluster, perform the following steps.
a Reconfigure the point assignment in the OPCI group such that any points and parameters deleted are
reconfigured and correctly referenced.
b Revalidate the OPCI group.
c Re-enable the OPCI group.

7.8.3 Other options


DSA. For remote DSA servers connected to the existing Experion cluster on the TPN, they can access data and
alarms of TPS points which have moved to the new clusters on the TPN by adding the new clusters into their
list of DSA servers.
Third party OPC clients. Third party OPC clients continue to access TPS data and alarms from the existing
Experion cluster without any additional configuration, even for the TPS points that are moved to the new
clusters on the TPN.
Displays. The custom displays continue to work as long as the items on a display references the TPS points and
parameters by their name.

143
7 MULTIPLE EXPERION CLUSTERS ON ONE LCN

7.9 Remove mappings

7.9.1 Removing mappings that are no longer needed on the existing Experion cluster

If… Then…
On the existing Experion cluster, the unit mapping option Select the Map TPS Units as follows checkbox. The data
currently used is “Map all TPS Units to Assignable Asset” for the Map TPS Units as follows table appears. This step
or “Map to Assignable Assets with the same name as TPS does not change the asset that TPS points are already built
Units (direct mapping)” in.
Remove the unit mappings for the TPN units that do not
belong to the existing cluster according to the plan
mentioned in “TPS Connection - Tuning properties” on
page 106. The mapping for these units must be set to “Not
Mapped” and the TPS points in these units will be deleted
from the existing cluster. Ensure that the SY TPN unit is
mapped to a different asset for each Experion cluster on the
TPN.
If on the existing Experion cluster, the unit mapping option Remove the unit mappings for the TPN units that do not
currently used is “Map TPS Units as follows” belong to the existing cluster according to the plan
mentioned in “TPS Connection - Tuning properties” on
page 106. The mapping for these units must be set to “Not
Mapped”, and the TPS points in these units will be deleted
from the existing cluster. Ensure that the SY TPN unit is
mapped to a different asset for each Experion cluster on the
TPN.

After the unit mapping is complete, enable notifications for the TPS system interface by selecting the
Notifications checkbox in the Status tab of the TPS Connection Status display in Experion.
Perform one of the following on the ES-T node, to remove the TPS points that are no longer mapped.
Restart each ES-T node in the existing Experion cluster.
Note: The ES-Ts can be restarted one at a time or all at once depending on the site preferences. However, it is
important that all ES-T nodes restarted before continuing to the next step. Restart the console station
components and not the computer. Perform the following steps to restart the console station components.
• Choose Start > All Programs > Honeywell Experion PKS > Console Station > Start-Stop Experion
PKS Console Station.
• The Console Station Disconnected message box appears.
• Click Stop. And then click Yes in the confirmation message box.
• Click the Start button when it appears.
Or
Failover the ESVT in the existing Experion cluster to the backup server.

144 www.honeywell.com
8 Integrate Experion Control

145
8 INTEGRATE EXPERION CONTROL

8.1 Integrating ACE-T with TPS


The ACE-T with TPS Option node can be directly connected to the TPN using an LCNP and the TPS (AM-
based) infrastructure.

Tip
The AM functionality is configured in the same manner as an Experion APP node. Make sure you have assigned
enough units to the AM and enough AM memory for AM-CL.

8.1.1 Platform
The platform for an ACE-T is the standard ACE platform, with the addition of an LCNP card and selected
components of the TPS infrastructure (for example, TPN Server).
The TPN Server on ACE-T is private, available only to locally resident ACE-T components. The Redirection
Manager is not used.

Attention
The ACE-T is not intended to be used as a general OPC server. The Experion APP must be used for this purpose.
Windows applications on an ACE-T are not supported by Honeywell.

8.1.2 Functionality of ACE-T


An ACE-T provides all ACE functions. ACE is a member of an Experion cluster, and may interface to the TPN
through an APP; that is, through a remote connection to the TPN Server. The ACE-T is a member of an
Experion cluster, and interfaces to the TPN through its local TPN Server.
Therefore, the only difference between ACE and ACE-T is:
• ACE-T is hosted (supported) by an ESVT rather than an Experion Server
The ACE-T node participates in Peer-to-Peer relationships with other Experion controllers in the same manner
as does an ACE on an Experion system.
The ACE-T does not participate in Peer-to-Peer relationships with TPN data owners. Instead, it functions as an
HCI Data Access client of TPN data owners, using its local TPN Server and LCNP. TPN data owners have no
access to ACE data or functions.
The Engineering Repository database and Control Builder tools will be hosted on ESVT, ES-T, and ES-CE with
TPS Extension in the same way they are hosted on the Experion Server, ES-C, and ES-CE, respectively.
For more information, see “ACE-T Guidelines” and the Application Control Environment User's Guide.

146 www.honeywell.com
8 INTEGRATE EXPERION CONTROL

8.2 Integrating Experion Controllers


Experion Controllers C200, C200E, C300, ACE, and FIM can be directly connected to both ESVT and an ES-T.
This capability is restricted to C200s that are connected by FTE. ControlNet connections are not supported.
The C200, C200E, C300, ACE, and FIM participate in Peer-to-Peer relationships with one another as they
would on a “regular” Experion system.
The Engineering Repository database and Control Builder tools will be hosted on ESVT, ES-T, and ES-CE with
TPS Extensions in the same way they are hosted on the Experion Server, ES-C, and ES-CE, respectively.

8.2.1 FTE Network Implications


The addition of Experion controllers to an integrated Experion-TPS system requires that the FTE network be
configured to support these controllers according to Honeywell guidelines. These guidelines are documented in
the FTE user documentation.

147
8 INTEGRATE EXPERION CONTROL

8.3 Experion EUCN control integration

Related topics
“EHPM configuration block” on page 148
“ACE/C300 to EHPM peer-to-peer communication” on page 148
“EHPM point import into ERDB” on page 148
“EHPM and ENIM firmware upgrade” on page 149

8.3.1 EHPM configuration block


The EHPM Controller block is similar to a C300 Controller block in terms of functionality and user interface
environment. However, there is no Control Execution Environment (CEE) associated with this controller, so the
EHPM Controller performs only basic execution of its parameters.
The EHPM Controller block represents the EHPM hardware and is used for defining the EHPM controller in
Control Builder. This block also represents the EHPM Controller in the Experion server.
On the EHPM configuration form, the tabs represent the parameters which are mostly for viewing the current
status of EHPM and statistic values. the EUCN tab displays the EHPM specific information.
The EHPM points and control application are configured using TPN tools. Control Builder configuration
enables CDA access between the ACE/C300 Controller and the EHPM Controller.
For more information on configuring the EHPM Controller block, refer to the Control Building User's Guide.

8.3.2 ACE/C300 to EHPM peer-to-peer communication


After the EHPM points are imported to ERDB, strategies can be configured to read/write values. These
configured strategies can be assigned to C300 and ACE.
Once the strategies are assigned and loaded to any of the controllers, peer-to-peer initiator connection is opened
up with the EHPM acting as a responder.

Note
The EHPM acting as the responder, must be loaded to the monitoring side of the ERDB in Control Builder.

8.3.3 EHPM point import into ERDB


To enable CDA data access between the ACE/C300 Controller and the EHPM Controller, you must the import
the EHPM points into ERDB using the EHPM Point Import Utility.

Note
The EHPM Point Import Utility can be run on non-ESVT clusters allowing offline configuration of EHPM
references in the ACE/C300 Controller.
TPS data access through the TPN Server does not require importing of EHPM points into ERDB.

For a list of point parameter types and its data types supported for CDA data access and for information on
importing EHPM points into ERDB, refer to the Control Building User's Guide.

148 www.honeywell.com
8 INTEGRATE EXPERION CONTROL

Note
If there are already existing Experion Server Peer Responder connections to the points in the EHPM Controller, you
cannot update those points on the controller. If you want to import those points, delete the associated Experion
Server Peer Responder connections and then proceed with import. For information on deleting these connections,
refer to the Control Building User's Guide.
For information on PMD compatibility with EHPM, refer to the Control Builder Components Theory.

8.3.4 EHPM and ENIM firmware upgrade


If the EHPM block is configured in Control Builder, use the Control Builder Migrate function to upgrade
EHPM firmware. To upgrade EHPM TPN personality, refer to the Customer Release Guide in the TPN/TPS
bookset.
Use CTools for EHPMs that are not configured in Control Builder, but has been integrated with the Experion
network (having both BOOT and APP images).
For upgrading EHPM firmware with CTools, refer to the Control Hardware and I/O Modules Firmware
Upgrade Guide in the Experion bookset.

Attention
You must power cycle EHPM after loading firmware, failing to do so interrupts peer-to-peer communication between
ACE/C300 and EHPM controllers.
If peer-to-peer communication is interrupted, reload the EHPM Controller from Project side in Control Builder after
loading firmware and power cyling EHPM. For more information, refer to the Control Building User’s Guide.

Note
For upgrading ENIM firmware and ENIM TPN personality, refer to the Customer Release Guide in the TPN/TPS
bookset.

149
8 INTEGRATE EXPERION CONTROL

150 www.honeywell.com
9 Authoring Custom Displays

151
9 AUTHORING CUSTOM DISPLAYS

9.1 Display Authoring Approach


The HMIWeb Display Builder tool provides a display area for creating and modifying custom displays in
HTML format. The tool provides dockable menus and toolbars that can be placed where the user prefers. An
object explorer presents a tree view of objects in the display. A Properties window shows each object's
properties.

9.1.1 Dynamic objects


When adding a dynamic object to an HMIWeb display, the user selects the Data tab and chooses a point from a
drop down list. The drop down list browses the available TPS/LCN points from the units that were mapped to
the TPS Interface.

For more information about HMIWeb Display Building, refer to the HMIWeb Display Building Guide.

9.1.2 TPS/LCN data access authorization


A data access request from Station to the TPS/LCN makes it request through the TPN Server. The TPN Server
passes the current access level down to the TPS/LCN with every data access, so the TPS/LCN data owner can
make the correct access authorization decision. However, the TPN Server does not support/implement the
additional access constraints specified in the NCF and enforced from the Native Window/Universal Station.
Experion provides its own mechanism for providing an equivalent capability.
If you select Data entry allowed, users with a security level equal to or higher than the specified Security
Level can edit the object's value. The security levels are: Operator, Supervisor, Engineer, and Manager. The
following figure shows an example of how to set the security for an HMIWeb display object.

152 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Refer to the HMIWeb Display Building Guide, section Object Properties>Data Tab>Defining a Link to a Point.
The section describes how to set the security level for the properties of Data Entry Allowed and Security Level.

9.1.3 Entering object script


Clicking an object name changes the script window to allow the user to enter script against that object. Object
names appear bold if script already exists for that object.

153
9 AUTHORING CUSTOM DISPLAYS

9.1.4 Invoke TPS/LCN displays


HMIWeb Displays can invoke TPS/LCN displays using Experion display invocation methods, as illustrated in
the following example (where DATACHNG is the TPS/LCN schematic name).

9.1.5 Shape gallery


The HMIWeb Display Builder tool provides a pre-built gallery of shapes to facilitate display building.

9.1.6 Faceplates
A popup is a secondary window that appears when a user clicks the HMIWeb display object to which it is
attached. A faceplate is a specialized type of popup that shows critical information about the point to which the
object is linked. HMIWeb Displays can invoke faceplates from a script or a button. Experion Faceplates are
available to display Experion and TPN point data. The Experion faceplates allow TPN points to be viewed. The
TPS Interface Configuration Page allows you to choose between Experion and TPS faceplates.

154 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

The following figure shows an example of an analog point Faceplate.

155
9 AUTHORING CUSTOM DISPLAYS

Classic TPS Faceplates also provide a way to invoke TPS/LCN point data from an HMIWeb display and can be
invoked from a script or through the configured faceplate behavior on the object, as described in this guide. A
TPS Faceplate mimics the functionality of one of the slots in a classic Universal Station Group display. TPS
Faceplates provide
Access to process variables, mode and mode attribute parameters through both the display and the keyboard,
and
Access to the Native Window point Detail display.
The following figure shows an example of a TPS Faceplate for an analog controller.
Operators can manipulate parameters of a selected point using the bottom portion of the TPS Faceplate. The
middle portion of the TPS Faceplate displays a graphical representation of the point values. The top portion of
the TPS Faceplate displays the TPS/LCN point name and description.

9.1.7 EHPM faceplate


You can invoke a point faceplate display for an EHPM node similar to invoking a C300 node’s point faceplate
display.
In addition to the values shown in the following figure, the faceplate can also show the Synchronization state,
when applicable, directly below the Redundancy state in the lower panel.

156 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.1.8 Invoke HMIWeb display from Station command zone


Custom and standard HMIWeb displays can be invoked by typing the display name into the Command Zone of
the Station application and pressing <Enter>.

9.1.9 Invoke GUS Display from Station Command Zone


You can invoke GUS Displays when you type the GUS Display name into Experion Station's Command Zone
and then press <Enter>. For example, if you want to build and call up a GUS Display called “Myplant” in
Station, do the following:
Build and validate the GUS Display called “Myplant.pct” using GUS Display Builder.

157
9 AUTHORING CUSTOM DISPLAYS

Place the “Myplant.pct” in an accessible folder that you have defined either,
• in the Area Database's Pathname Catalog. For example, you could enter “C:\GUSDISP” as the folder name.
For more information, refer to the “Pathname Planning” section in the GUS Display Builder User's Guide.
Or,
• in the Displays Search Path Extension from the Configuration Utility. For example, you could enter “C:
\GUSDISP”. For more information, refer to the “GUS Display Runtime Settings Page” section in the
Configuration Utility User's Guide.
In Station's Command Zone, type “Myplant” and then press <Enter>. Result: the GUS Display, Myplant,
appears.

158 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.2 Accessing HMIWeb TPN detail displays


Experion provides a set of native HMIWeb displays that access an extended set of standard operational
parameters associated with a given TPN point. The displays provide easy access to TPN operational parameters.
A link on the HMIWeb's TPN detail display provides immediate access to the Native Window detail display
(depending on Native Window availability) for TPN engineering parameters.
With Experion R410, you can view and control the all the parameters, using Experion TPN point detail displays
as you can with the Native Window point detail displays. While the Native Window display provides the data in
a series of separate pages, Experion station display provides the same data as a set of tabbed displays. The
tabbed display framework of Experion Station window incorporates all the components that are supported in the
Native Window.

9.2.1 Example display with TPN operational parameters


The displays include operational parameters as provided in their respective Native Window displays, but within
a tabbed display framework similar to existing Experion detail displays. The TPN detail displays behave as
HMIWeb displays in terms of availability on all Experion configurations including operation across DSA.

Detail displays present the operating parameters and limits for individual data points and process modules. You
can modify the operating parameters through the HMIWeb TPN detail display.

9.2.2 HMIWeb TPN detail displays for Logic tabs


You can view the logic configuration parameters including logic blocks, flags, numeric, input connections, and
output connections, similar to Native Window pages by configuring the logic points. The logic point provides

159
9 AUTHORING CUSTOM DISPLAYS

the basis for integrated logic functions. All the components of the logic points are available in the HMIWeb
TPN detail displays as tabs. Clicking each tab gives you the parameter details of that particular tab.

Logic General tab


You can view and control the logic point parameters such as PRMDESC, GENDESC, and Numeric values as in
Native Window logic point details on the General tab.

Logic Gate Overview tab


You can view the logic gate overview parameters, which includes, for example, 12_24_4 style graphical logic
gate connections.
The Experion Station display incorporates the same active component that supports the GUS display, that is,
XPMLOGIC_DISPLAY.PCT.
Note that this display scales better to the standard 16x10 aspect ratio.
The faceplate is removed from this display to enable larger and more readable graphical display of the logic
overview.

Tip
The logic tab is shown at 100% as the logic Active X component of the logic graphical display does not support the
zoom to fit option. You can view the logic tab as per your requirement with the help of the scroll bars.

160 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

In Connect tab
The logic point provides the basis for integrated logic functions. Assign inputs to the logic point during
configuration, using logic input connections. You can specify up to 12 inputs that are assigned to logic point.

161
9 AUTHORING CUSTOM DISPLAYS

Out connect tab


Use logic output connections to write the values of local parameters of a respective logic point to the configured
destinations. You can configure up to 12 outputs for each logic point.

162 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Flag-Num tab
You can view the logic configuration array, numeric, and flag values as can be done on the Native Window
detail display.

163
9 AUTHORING CUSTOM DISPLAYS

Configuration tab
You can view the logic block configuration parameters on Experion TPN detail page as can be done on Native
Window logic point detail page.
The Configuration tab displays the ALG S1/R1, S2/R2 values.
The following figures are an example of 12_8_8 and 12_16_4 type of PM point.
Note that the ASSOCDSP and $CDETAIL parameters are removed from the General tab and consolidated on
the Configuration tab. This avoids duplication of the parameters in two different displays.

164 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

165
9 AUTHORING CUSTOM DISPLAYS

Logic tabs for SM


You can view and control the logic point parameters such as PRMDESC, GENDESC, and Numeric values
along with the other parameters as in the Native Window logic point details on the General tab.
Clicking each tab gives you the parameter details of that particular tab.

166 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.2.3 HMIWeb TPN detail displays for Device Control tabs


You can view the device control tabs as you view in a Native Window, by configuring the device control points
in the Native Window. The device control pages include the general connect page, logic page, flag-num page,
maintenance parameters, and so on. The Device Control (DevCtl) point provides a way to modify a device and
to view the strategy through a single point. This point also helps the operator to graphically trace the source of
an interlock condition.

Device Control General tab


You can view all the device control point type parameters that are configured in the first page of the native
window.

167
9 AUTHORING CUSTOM DISPLAYS

Device Control Logic tab


With R430, the device control logic tab is available in the detail display for the device control points.

Note
The device control logic tab is visible to only those device control points which have logic inputs. The device
control logic tab on the Experion TPN detail display provides the same functionality as the Native Window “Logic”
page for detail displays on the Native Window for device control points.

168 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Digital Connect tab


You can view the digital connect tab by configuring the device control points as can be done on the Native
Window.

169
9 AUTHORING CUSTOM DISPLAYS

General Connections tab


You can view this tab by configuring the device control points in the Native Window. The Device Control
(DevCtl) point provides a way to modify a device and view the strategy through a single point.

170 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Gate Configuration tab


You can view all the DEVCTL Gate Configuration parameters using Experion TPN detail display as can be
done on the Native Window.

171
9 AUTHORING CUSTOM DISPLAYS

Flag-num tab
You can view the DEVCTL array values on Experion TPN detail display as can be done on the Native Window
FLG-NUM page for points of this type. You can modify the NNINSET, NUMERIC, and FLAG parameters as
can be done on the Native Window.

172 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Maintenance tab
You can view the Device control Maintenance parameters using Experion TPN detail display as can be done
using the same page on the Native Window for points of this type. The Maintenance parameters for this point
are State Transitions, Accumulated Time, Safety Overrides, and Statistics. You can reset the Statistics
parameter if the Redtag parameter is set to ON.

173
9 AUTHORING CUSTOM DISPLAYS

9.2.4 HMIWeb TPN detail displays for Regulatory Control tabs


Regulatory Control (RegCtl) points are used to perform standard control functions by executing the algorithms
that have been configured. Predefined and custom displays are available to support these control strategies.
Select a point name or connection point.parameter on any connections page. Navigate to that point by selecting
the detail button or by double-clicking the point.

PV Connect tab
You can view this page by configuring the AM regulatory control points in the Native Window. You can
navigate to the PV Connections tab and view the PV connections for the TPN point.

174 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Control Connect tab


You can view this tab by configuring the AM regulatory control point in the Native Window. Control
connections can be both input connections and output connections.

175
9 AUTHORING CUSTOM DISPLAYS

Contact Cutout tab


The contact cutout function prevents a proliferation of alarms from being reported to the operator. You can use
this function to cut out alarms on a point when they are generated because of alarm conditions that have been
detected at other points.

176 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

General Connect tab


You can view this tab by configuring the regulatory control point in the Native Window. Get the details of the
general input and general output connection pages from this tab.

177
9 AUTHORING CUSTOM DISPLAYS

General tab with CL Switch


CL Switches are added to Regulatory Data Points in an AM to communicate the state of custom CL strategies to
Universal Station operators. In addition, it is used to provide a standard way for the operator to make strategy-
change requests to the CL logic. The two parameters of CL switch are Current state and Requested state.

178 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

CL Block tab
The CL Block tab shows the array of CL Slots, which is a listing of up to 256 line items. This is shown in
Experion on a single CL Block tab, with UI components (for example, scrollbar, page up/down buttons) to
enable traversal of the list. Configure the regulatory control points in AM to view the CL block tab. You can
change the activity status as per your requirement.

179
9 AUTHORING CUSTOM DISPLAYS

HG Tuning tab
You can view this tab by configuring the Highway Gateway (HG) points in the Native Window. Access the HG
Tuning parameters and connections from the Experion detail display. This includes HG Extended controller
regulatory parameters, such as SOASRC, SOASIGNL, input connections, and so on.

180 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.2.5 HMIWeb TPN detail displays for Sequence Parameters


A process module point in the xPM performs the loading of the sequence. The process module point, after being
configured and loaded with the compiled CL, displays the status of the sequence and the associated parameters.
With Experion R430 and TPN R685, you can load and control Sequence programs from Experion TPN detail
pages as can be done from Native Window detail pages.

Sequence point messages


You can view messages for the detailed sequence point from this page.

181
9 AUTHORING CUSTOM DISPLAYS

Sequence point arrays


Click on Mod Nums tab to display the Module Numerics data.

182 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Click on Mod Flags tab to display the Module Flags data.

183
9 AUTHORING CUSTOM DISPLAYS

Click on Mod Strings tab to display the Module Strings data.

184 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Click on Box Nums tab to display the Box Numerics data.

185
9 AUTHORING CUSTOM DISPLAYS

Click on Box Flags tab to display the Box flags data. You can set the flag in ON or OFF state.

186 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Click on Box Strings tab to display the Strings data. The number of selected strings appears in the header.

187
9 AUTHORING CUSTOM DISPLAYS

Sequence point — operator changes


You can modify the time value from the Experion detail display.
Note that the value under 1000 days is formatted as <days> HH:MM:SS. If the duration is less than 24 hours,
then the format is HH:MM: SS).

188 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Click on Box times tab to display the Box time data with the modification of time values. The time is displayed
in the format Date: Time: Duration.

189
9 AUTHORING CUSTOM DISPLAYS

190 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Click on Box timers tab to view the timer array values. You can start, stop, or reset timer.

191
9 AUTHORING CUSTOM DISPLAYS

You can select a timer point on the Box Timers tab to:
• Start or stop a timer
• Reset a timer
• Change the preset value of a timer
• Change the time base of a timer

192 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Click on Config tab to view the Alarm Priority, Control Lock access, Set Point Lock access, and Operator
Option for the Process Module. You can also view the Time and Date Stamp information as in the native
window detail display.

193
9 AUTHORING CUSTOM DISPLAYS

Sequence point — Load tab


With Experion R430, the Load tab is available in the detail display for the Sequence points (those with
DISPTYPE parameter equal to “SEQUENCE”). This new detail display tab for sequence points provides the
interface for users to identify available sequence programs for the given sequence point. It also enables the user
to select and load a particular sequence program.

Attention
For proper functioning of the Load tab, the TPS/LCN must be at a minimum release of R685, otherwise an error
message is shown in the Command zone message area if you attempt to retrieve sequences.

Attention
The Load tab is available in the detail display for the sequence points only on EST nodes, but not on Flex nodes.

Attention
You cannot save sequence programs from Experion TPN detail pages as can be done from Native Window detail
pages.

194 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Click on Load tab to display the Load page.

195
9 AUTHORING CUSTOM DISPLAYS

To identify available sequence programs, you may select whether to look at the LCN network (NET), or select a
removable media drive (for example, $F1, $F2, and so on.) using the Media Source drop-down menu. You can
select the Get Sequences button to retrieve the available sequence programs from the selected source which
apply to the currently detailed sequence point.
Click on a particular sequence program from the list and then click on Load Sequence button to display the
system response.

Click on Clear Selection button to deselect any selected sequence program, which also disables the Load
Sequence button.
Once the sequence program is successfully loaded, faceplate response (on the left side of the detail display)
indicates the currently loaded sequence program.

196 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.2.6 HMIWeb TPN detail display for CDS Parameters


You can view and modify all the custom data segment (CDS) parameters using Experion TPN detail display, as
you do using Native Window. The CDS parameters are displayed on the Custom Data Segment tab of the
Experion station detail display. The custom parameters are available for regulatory point with CL as algorithm,
CL Switch, and custom point in the Application module from the Engineering menu.

Attention
• Experion CDS tab does not include Engineering Units descriptors for CDS parameters.
• Experion CDS parameters include non-standard parameter names but exclude standard parameter names (for
example, PV, SP, OP, and MODE) that exist at the very beginning or end of the CDS parameters.
• Experion CDS parameters do not display arrays that have enumeration values as their indices.

197
9 AUTHORING CUSTOM DISPLAYS

9.2.7 HMIWeb TPN detail displays for Smart Transmitter Data Configuration Parameters
You can view Smart Transmitter Data using Experion TPN detail display, as you do using the Native Window
Configuration page for UCN STIM points. You can view the Smart Transmitter data, including STIGAT,
SENSRTYP, PVCHAR, CJTACT, PIUOTDCF, DECONF, and so on.

198 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.2.8 HMIWeb TPN detail displays for Array Points


Array points help you access Flag, Numeric, String, and Time variables. You can access the array parameters
from Experion TPN details as you can from a Native window detail pages.

General tab
You can view MODNUM, MODTYPE and so on in the General tab.

199
9 AUTHORING CUSTOM DISPLAYS

Configuration tab
You van view USERID, STSMSG, SPLOCK, and PRIMOD in the Configuration tab. The Configuration tab
also displays the alarm summary for this array.

200 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Numerics tab
The Numeric tab displays the number of numerics displayed for this array, for example, the number of
numerics configured is 60 as per the following figure.

201
9 AUTHORING CUSTOM DISPLAYS

Flag tab
The Flag tab displays the number of flags configured for this array, for example, the number of flags configured
is 10 in the following screen capture.

202 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Strings tab
String tab displays the number of Box Strings that are available. The Array point accesses and obtains string
data in lengths of 8, 16, 32, or 64 characters.

203
9 AUTHORING CUSTOM DISPLAYS

Times tab
Times tab displays the time and the number of times configured for this array. Click on the time array value and
a check box is highlighted at the bottom to either set the time value as duration or date. You can set the timer
value either as Duration or as Time Format.

204 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.2.9 HMIWeb TPN detail displays for EHPM Node


You can invoke a point detail display for an EHPM node similar to invoking a C300 point detail display. An
example of EHPM detail display Main tab is shown in the following image. Two more tabs are provided for the
EHPM detail display besides the Main tab, the EUCN tab, and the Config Details tab.

Main tab
You can view the Tagname, Device index, IP Address and so on in the Main tab.

205
9 AUTHORING CUSTOM DISPLAYS

EUCN tab
You can view the HPM Node Number, UCN Network Number, Authentication Group and so on. Parameters
provided in the EUCN tab of the EHPM detail display are shown in the following image.

Note
The format of the Authentication Server value is identical to the format of an IP network address.

206 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Config Details tab


Config Details displays the same tabbed object as provided in the Control Builder for a given EHPM node.

207
9 AUTHORING CUSTOM DISPLAYS

9.2.10 Native Window Detail invocation


You can invoke a Native Window Detail display from the HMIWeb TPN detail display.

208 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Additional tabbed displays


Additional tabbed displays can appear providing operator's information as follows:

209
9 AUTHORING CUSTOM DISPLAYS

Control tuning parameters

Trend information

9.2.11 Display invocation


You invoke HMIWeb TPN detail displays the same way as invoking Native Window detail displays in earlier
releases, which includes:

210 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Double-clicking a parameter included on a given Experion display


Selecting the DETAIL key on an IKB/OEP keyboard and entering the point
Selecting the detail icon in the Station toolbar
Enter point name in command window, press F12.

Note
The ENTER key can be used instead of F12 (if this option has been enabled for your system), but this searches for a
matching display name first and only look for a point name if no display name is found. The full point ID must be
entered.

9.2.12 Enabling HMIWeb TPN detail displays


TPS Integrated Nodes already have HMIWeb TPN detail displays loaded and enabled; you do not need to
perform any additional configuration. During Experion node installation, the display files install by default to
directory, C:\ProgramFiles\Honeywell\Experion PKS\Client\System\R3xx, along with other standard Experion
system displays. The Experion node's default configuration is to invoke the HMIWeb TPN detail display instead
of the Native Window Detail display.

Attention
• With Experion R410, 64-bit OS is supported. All 32-bit components are installed in C:\Program Files (x86). The
default path for installation of Experion PKS is C:\Program Files (x86)\Honeywell\Experion PKS.
• The Custom Install Path (CIP) is supported in Experion R410. You can choose any possible path for installation
(for example, D:\TEST\Honeywell\Experion PKS).

Native Window Detail display invocation


If you prefer to invoke Native Window Detail displays instead of HMIWeb TPN detail displays, you enable the
Native Window option from System Configuration > System Interfaces > TPS > Configuration >
Enable“Use Classic TPS Faceplates.”

9.2.13 HMIWeb TPN detail display integration with SafeView


Earlier released SafeView workspace configurations utilizing the HW_System_Detail category for their point-
detail window management require no changes in order to manage the HMIWeb TPN detail displays.
Workspaces designed specifically to utilize the Native Window for purposes including presentation of TPN
point detail displays may continue to do so. However, if you choose to keep the Experion node default
configured to no longer invoke the Native Window detail displays, then you will need to update your SafeView
workspace configurations accordingly.

9.2.14 Script invocation of HMIWeb TPN detail


When you use a programmatic interface to invoke a HMIWeb TPN detail for a TPN point, you need to specify
the proper (.htm) file name. You can identify the filename by examining the TPN's DISPTYPE parameter of the
point in question. There is a corresponding detail display with the DISPTYPE before the .htm suffix. The
displays are in three categories: Analog, Digital, and Miscellaneous, as described below.
Analog: PID, ANALGIN, ANALGOUT, ANALOUT, OUTPUT, NONPV, PVOUTPUT, DAS, ANALGACC,
3INPUT, NUMERIC, COUNTREU, COUNTER, TIMER, POSPROP, LLSUMMER
Digital: DIGCOMP, DEVCTL, DIGIN, DIGOUT, DIGINOUT, SWITCH, SEQUENCE
Miscellaneous: CUSTOM, ARRAY, NULL, ACID, LOGIC

211
9 AUTHORING CUSTOM DISPLAYS

9.2.15 Example script invocation of HMIWeb TPN detail


The following script fragment illustrates an HMIWeb TPN detail invocation:
window.external.currentpage “sysdtltpspid.htm?hscpoint=HG050708”

The following figure summarizes script syntax.

9.2.16 Identifying the DISPTYPE parameter


You can identify the DISPTYPE parameter value through the use of the DATACHNG following display:

9.2.17 Examples of other script invocations


The following script fragments illustrate invocations:
Invoke GUS display, where “some” is the GUS display name:
window.external.CurrentPage = “some.pct”
Invoke Native Window display, where “some” is the Native Window display:
window.external.CurrentPage = “some.do”
Invoke HMIWeb display:
window.external.CurrentPage = “some.htm”

212 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Invoke HMIWeb faceplate:


window.external.Parent.InvokePopup “some.htm”,40,30,0

213
9 AUTHORING CUSTOM DISPLAYS

9.3 Deploying HMIWeb Faceplates for TPN


When HMIWeb faceplates are used for accessing the TPN points, they are consistent with the current Experion
faceplate usage in terms of configuration, invocation, general user interactions, and SafeView management. The
HMIWeb faceplate, if used with TPN points, appears similar to current HMIWeb faceplate styles as those used
for Experion. HMIWeb Faceplate displays, if used for accessing TPN, can also operate across DSA connections.
The following example shows an HMIWeb faceplate displaying a Native Window's TPN control point.

9.3.1 Supported TPN point types


HMIWeb-based faceplate displays are available for the following TPN point types.
AM Points: REGAM, FLAGAM, NUMERCAM, TIMERAM, COUNTAM, SWITCHAM, CUSTOMAM
NIM Points: ANINNIM, ANOUTNIM, DIINNIM, DIOUTNIM, DICMPNIM, REGPVNIM, REGCLNIM,
LOGICNIM, FLAGNIM, TIMERNIM, NUMERNIM, DEVCTL, PRMODNIM
HG Points: ANLINHG, ANLOUTHG, ANLCMPHG, DIGINHG, DIGOUTHG, DIGCMPHG, REGHG,
COUNTHG, HGTIMER, FLAGHG, PRCMODHG, CTLCOUNT, NUMERCHG, LGCBLKHG
It is not unusual for common faceplate parameters such as SP to actually be associated with a parameter of a
different name. For example, the PVTV parameter may be used to represent the SP parameter on the faceplate.
The faceplate will (for PVTV) range the value per SPEUHI/LO or PVEUHI/LO as applicable. Additionally, the
faceplates will employ SP/PVDSPHI & SP/PVDSPLO range-overrides when they are available.
HMIWeb TPN faceplates can participate in HMIWeb group displays. These group displays may consist
exclusively of TPN points or may include a mixture of TPN points and points from other sources which have
HMIWeb faceplates.

214 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Note: TPS Fieldbus points are not supported by the HMIWeb TPN faceplate or HMIWeb TPN Detail displays.

9.3.2 Configuration overview


Configuration of a TPN-based point follows similar approaches as an Experion-based point as shown in the
following figure. This example assigns a faceplate behavior to an alphanumeric object.

9.3.3 GUS display invocation of HMIWeb faceplate


GUS displays are able to invoke HMIWeb faceplate displays. Based on a TPN point name, the GUS display
script that is handling operator requests may obtain the name of the detail display from the local TPN Server,
append the “_fp” suffix to create the faceplate name, and invoke it using the Experion station automation
interface. Note that GUS displays may continue to use classic TPS (GUS) faceplates.

Example
For a given parameter displayed on a GUS display, determine the DISPTYPE parameter value for that same
point, and then use that DISPTYPE value to invoke the proper Experion HMIWeb faceplate for that point. In
the example below, a given parameter is shown on a GUS display and, when the operator clicks on that
parameter, an Experion HMIWeb faceplate is displayed for that TPS point. The point is known to have a
DISPTYPE value of PID.

Tip
You can discern any point's DISPTYPE value using the standard “datachng” schematic, and typing
<yourpointname>.DISPTYPE into one of the fields.

215
9 AUTHORING CUSTOM DISPLAYS

An OnLButtonClick script then is constructed to invoke the proper HMIWeb faceplate associated with “PID
type” points as shown below.
Sub OnLButtonClick()
invokedisplay “sysdtltpspid_fp.htm?currentpoint=hg050708”
End Sub

In general, the script for invoking a given point.parameter's faceplate is:


Invokedipslay “sysdtltps<DISPTYPE>_fp.htm?currentpoint=<name of point>”

9.3.4 Station invocation script invocation example


The HMIWeb faceplate does not provide any intrinsic programmatic interfaces. Each faceplate may, however,
be invoked programmatically from Station via the following example automation call. Note that when using a
programmatic interface to invoke a HMIWeb faceplate for a TPN point, you have specified the proper faceplate
(.htm) file name. This can be determined by examining the TPN's DISPTYPE parameter of the point in
question.
Application.InvokePopup “sysdtltpsPID_fp.htm?currentpoint=analogpoint”, 0, 0, 1.
The classic TPN ActiveX-based faceplate may also be invoked programmatically, as shown in the following
script fragment.
Application.InvokePopup “sysdtltps_fp.htm?currentpoint=analogpoint”, 0, 0, 1

9.3.5 Identifying the DISPTYPE parameter for a faceplate


You can identify the DISPTYPE parameter value through the use of the DATACHNG display, as noted
previously for HMIWeb TPN detail displays. DISPTYPE is also viewable from the faceplate's title bar.

216 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.4 Supporting Display Operations in TPS/LCN

9.4.1 TPS/LCN and Experion Display support


Display operations for ES-T and ESVT nodes are supported in the following manner:
Experion Group displays support inclusion of TPN points.
The multi-window Station application provides a command zone, a status window, and a configurable number
of display windows. For an ES-T, the SafeView application manages the various Station windows and a single
Native Window.
HMIWeb Displays allow operators to view and manipulate data including data from the TPS/LCN, data from
other Experion servers through DSA, data from local, direct-connect Experion controllers, and data from
SCADA interfaces. HMIWeb displays running in an ES-T access TPS/LCN data directly. HMIWeb displays can
invoke TPS/LCN displays in the Native Window.
The Native Window allows operators to view existing standard and custom TPS/LCN displays. The Native
Window supports all functions of the TPS/LCN displays.
Experion displays can be invoked from the Native Window.
The TPS Faceplates are one way that operators can control TPS/LCN points through user-authored displays.
The TPS Faceplate may be embedded in HMIWeb displays.

Tip
If you are migrating from US /GUS to ES-T, accessing remote points through HMIWeb with DSA is preferred over
NG as TPN server is not capable of writing enumerated values, such as mode and across network gateways.

9.4.2 Replacing TPS/LCN schematics


You can replace existing TPS/LCN Schematics or GUS displays as HMIWeb displays on a per display basis
without having to modify existing TPS/LCN Schematics, GUS displays or Button Configuration files.
For example, consider a system with 500 TPS/LCN Schematics, all of which reference MyDisplay.DO through
the SCHEM actor:
SCHEM (“MyDisplay”)
After MyDisplay.DO is replaced with a corresponding HMIWeb (that is, a file named MyDisplay.HTM),
execution of the Actor SCHEM (“MyDisplay”) in any existing TPS/LCN Schematic or Button Configuration
File will result in invocation of MyDisplay.HTM.
The TPS/LCN SCHEM actor first looks for an HMIWeb display. If the HMIWeb display with the requested
name does not exist, the SCHEM Actor attempts to invoke a GUS display and finally, the TPS/LCN Schematic
if the GUS display name does not exist.

9.4.3 Pathname search behavior


When an HMIWeb display is invoked, the system searches a set of pathnames to locate a display; thus, the
invoking display does not have to carry the full pathname of the HMIWeb display. The pathnames for HMIWeb
displays are separate from the pathnames used for TPS/LCN Schematics.

9.4.4 Pathnames for HMIWeb displays


Pathnames for HMIWeb displays are defined as part of Station application's connection properties.

217
9 AUTHORING CUSTOM DISPLAYS

9.4.5 Pathnames for Universal Station schematics


Pathnames for Universal Station style schematics are supported from the TPS/LCN's Area database pathname
catalog.

9.4.6 Pathnames for GUS displays


Path names for GUS displays are defined as they have been in the past within GUS Display Builder. For more
information on GUS pathnames, refer to the “Managing Your Environment” > “Schematic Invocation” section
in the GUS Display Builder Guide.

218 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.5 Implementing the TPS Faceplate Control

9.5.1 Inserting TPS Faceplate Control as an ActiveX control


The TPS Faceplate Control is an ActiveX component for viewing and manipulating parameters of a selected
TPS/LCN point from an HMIWeb Display.
The Honeywell TPS Faceplate Control appears on the HMIWeb Display Builder's list of ActiveX controls
available for insertion into an HMIWeb display.

9.5.2 TPS Faceplate Property page in HMIWeb Display Builder


In HMIWeb Display Builder, the TPS Faceplate presents the following property page. HMIWeb Display Builder
assigns the name to the particular Faceplate ActiveX Control object in the form of Control###, where ###
represents a sequence number.

219
9 AUTHORING CUSTOM DISPLAYS

9.5.3 TPS Faceplate usage consideration


If you add the Honeywell TPS Faceplate ActiveX to a HMIWeb display and add a tag name from a unit that is
not assigned through its Asset to the Experion station, the information for the point is still displayed and can be
modified by the operator even though the unit has not been assigned through its Asset to the Experion station.

Attention
The TPS Faceplate control should be used only in displays intended for use on ES-T nodes but not used in displays on
an ESVT or in displays on Flex Stations directly connected to an ES-T node.

9.5.4 Script access to TPS Faceplate properties and method

Property Name Script Access in HMIWeb Display


Description
Name Not applicable. No data, no error.
TagName Must be accessed explicitly through the “Object” element, as in:
Control001.object.tagname = “A100”
Visible Not applicable. Results in error. Instead, use the “Style” object, as in:
Control001.style.visibility = “hidden”

Method name Script Access in HMIWeb Display


SetFocus Not applicable. Results in error. Instead, use the “Focus” method, as in:
Control001.focus

220 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.5.5 Faceplate sysDtlTPS_fp.htm


A faceplate popup display: sysDtlTPS_fp.htm is provided as part of the Experion installation. The display
contains a single TPS Faceplate ActiveX Control, which is scripted to:
retrieve the TPS/LCN point name,
activate the faceplate with the given point name,
present errors emitted by the faceplate in Station's Message Zone.
The sysdtltps_fp.htm display services the built-in Faceplate behavior on the HMIWeb display for the TPS/LCN
data points. The sysdtltps_fp.htm display has the generic TPS_Faceplate SafeView category. The display may
be used as-is to service the HMIWeb Faceplate behavior, or as an example template when creating customized
faceplate displays.

Attention
Note: For the TPS/LCN points, there is a strong relationship between the name of the standard faceplate display and
the execution of the Faceplate behavior. In the initial release of the Experion Station-TPS, this display file name must
be sysDtlTPS_fp.htm.

9.5.6 Invoking the faceplate - popup display


The HMIWeb display has an alphanumeric (for example, alpha001) object that is associated through the Data
tab with a TPS/LCN point.parameter. Clicking the object will result in the invocation of the standard TPS
faceplate popup display. The TPS Faceplate will then present the associated TPS/LCN point.

221
9 AUTHORING CUSTOM DISPLAYS

9.5.7 Invoking the TPS faceplate through scripting


Example 1: Faceplate control control001 embedded in current display script:
sub onbuttonclick…
control001.object.tagname = strPointName
control001.focus
end sub

Example 2: Invoke TPS faceplate custom display, passing tagname in the invocation parameter list:
An HMIWeb display test.htm has a pushbutton001 object. On mouse click, the custom TPS faceplate display
(tps_custom_fp) will be invoked, setting the tag name A100 on the faceplate object control001. Keyboard input
focus will be set at the TPS faceplate control window.
Sub pushbutton001_onclick
'invoke the tps_custom_fp display and set tag “A100”
window.external.currentpage = “tps_custom_fp.htm?currentpoint=A100”
End Sub

Tps_custom_fp.htm:
Sub Page_onpagecomplete
'this display is assumed to be invoked from another hmiwebdisplay by the following script:
' window.external.currentpage = “displayname?currentpoint=pointname”
' per convention, the string “?currentpoint=?” must be there - note: no spaces
'
' the invocation URL for this display will be then: “…displayname?currentpoint=pointname%26…”
' -- during display startup we need to extract the “pointname” string and give it to the faceplate
activex (control001)
dim strHRef
dim strPointName
dim nPointNameStart
dim nPointNameEnd
strHRef = window.location.href ' get the invocation URL
' msgbox strHref ' simple debugging
nPointNameStart = InStr(1, strHRef, “?currentpoint=”, 1) '
if nPointNameStart > 0 then
nPointNameStart = InStr(nPointNameStart, strHRef, “=”, 1)
nPointNameEnd = InStr(nPointNameStart, strHRef, “%26”, 1)
if nPointNameEnd > 0 then
strPointName = Mid(strHRef, nPointNameStart + 1, nPointNameEnd - nPointNameStart - 1)
else
strPointName = Mid(strHRef, nPointNameStart + 1)
end if
' check for the network gateway character “\” that maybe presented as “%5C”
strPointName = Replace(strPointName, “%5C”, “\”, 1, -1, 1)
end if
' set tagname; must go through the “.object” explicitly
control001.object.tagname = strPointName
' assign keyboard input focus to the faceplate control
control001.focus
End Sub

222 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.6 Accessing Actors

9.6.1 About Actors


Actors are built-in software components providing specific functions and operations on the TPS/LCN's GUS or
US nodes, such as invocation of the Point Detail display.

9.6.2 Purpose of Actors in TPS/LCN


Actors in a GUS or US schematic typically provide a way to call up specified displays on the same or other
screens in the Universal Station console. Additionally, actors can output messages to the screen, update
displays, read data from the screen and store it, or read information from various databases and present it on the
screen. Activating a target on a US schematic or pressing one of the configurable buttons on the operator's
keyboard triggers execution of scripted actors. Some of the actor functions connect internally to IKB and OEP
“hot keys.” With the exception of the SCHEM actor, all actors execute according to the documented TPS/LCN
definition.
For more information about Actors, refer to the TPN/LCN Actors Manual.

9.6.3 SCHEM actor for display invocation


The SCHEM actor attempts to invoke an Experion display file (.htm or .dsp) with the given name. If such
display exists, it appears in the Station application window; otherwise, the US schematic with the given name
appears in the Native Window.

Tip
GUS displays will appear if in the search path.

9.6.4 KEYLEVEL actors


HMIWeb displays use scripting functions,
SetDataValue with security level and,
SetDataValue synchronously with security level
To execute writes at particular access levels.

Tip
Functions must be enabled in Experion Server-wide Station Settings, Security.

9.6.5 Experion Standard displays - no access through Actors


The TPS/LCN standard display invocation actors will not invoke the Experion standard displays. For example,
the ALARMSUM actor in a target on a US schematic will invoke the standard Native Window Alarm Summary,
not the Experion Alarm Summary display. If this behavior is unwanted then US schematics that have targets
with the standard display actors must be re-implemented as HMIWeb displays on an ES-T. The configurable
buttons that are dependent on these actors must be redefined using Experion configuration tools.

223
9 AUTHORING CUSTOM DISPLAYS

9.7 Accessing Actors from HMIWeb script using TPS Commands

9.7.1 About TPS Commands


The TPS Commands component allows the Station application to access the selected Native Window display
actors through display scripting. Display authors create an instance of the automation object using the ProgID
TPSCommands to create the component, as in the following example:
set tpscmd = CreateObject(“TPS.Commands”)

Display authors then include script to invoke the TPS/LCN Display, as in the following example where a Native
Window Detail display is invoked to display the tagname A100 and position the initial display on page three.
tpscmd.InvokeDisplay “TPN_Detail”, “A100”,3

Attention
Use of TPS Commands should be limited to only those cases where the Experion Station display invocation method
does not meet the need.
Internally, Experion Station uses the TPS Commands object to invoke Native Window actors when the display
invocation request cannot be serviced by the Experion display.
For example, if the desired action is to display page three of a TPS/LCN Detail Display, then the use of TPS
Commands is warranted.
Honeywell strongly recommends that the Experion Station display invocation method to access TPS/LCN data be used
whenever possible in order to avoid future schematic maintenance issues.

9.7.2 Installation of TPS Commands


TPS Commands is installed as part of the ES-T; specifically, the TPS display infrastructure sub-package.

9.7.3 InvokeDisplay method


The InvokeDisplay method has the following syntax:
InvokeDisplay DisplayName [, Parameter1[, Parameter2, …]]
Where:

DisplayName [string] US custom schematic name or one of the predefined standard


display names (refer to the table TPS/LCN standard displays that
follows in this section).
The DisplayName may include display file extension (“.DO”).
With the exception of standard display names, length of the
DisplayName string (excluding optional file extension) may not
be greater than eight.
Parameter1, Parameter2, … [string or integer] Optional parameter(s); as required by the TPS/LCN standard
displays only

Return value: None (see the ErrorMsg property)


The InvokeDisplay method will start the Native Window application if it is not already running. The
InvokeDisplay request is sent to the LCNP in the form of an appropriate TPS/LCN actor.

224 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

Concurrently, the Native Window application main window restores, if necessary, and activates. In this way the
operator immediately uses focus-dependent keys (such as Point Manipulation (PMK) keys after invocation of
the Point Detail display), without additional clicking on the Native Window display.

Attention
The display invocation request will fail if Native Window currently displays any Engineering Menu functions.

9.7.4 TPS Command Properties

Property name Description Comment.


NodeNumber [integer] TPS/LCN node number Read-only.
ConsoleNumber [integer] TPS/LCN console number Read-only.
AreaNumber [integer] TPS/LCN area number Read-only.
ErrorMsg [string] Non-empty if the last executed Read-only, Max string length is 80
method has failed characters.

9.7.5 TPS Command Error messages


The following error messages indicate system installation and/or configuration problems. In all circumstances,
check the contents of Windows Event Viewer Application and System Event logs for additional information.

ErrorMsg Interpretation
LCNP board is not present or not configured. The system has no LCNP board or the LCNP board has not been installed
or configured properly.
Internal error: cannot connect to hopcsrvr.exe Verify that the software is properly installed and configured.
Unable to open Native Window (N). Verify that the software is properly installed and configured. Note the value
of “N” and contact Honeywell TAC.

Note that the Native Window SCHEM actor does not return an explicit error to the caller if the particular
custom US schematic does not exist. Instead, Native Window schematic display area is cleared and presents the
error message text.

9.7.6 TPS/LCN standard display invocation using display name


Selected TPS/LCN standard displays may be invoked through the TPSCommands InvokeDisplay method, using
the predefined display names. Some of the invocations may require additional parameters. Note: the list of
TPS/LCN Standard Displays is much larger (refer to the TPS/LCN Actors manual.). The displays that are not
included in the table below may only be invoked using Native Window.

TPS/LCN Standard InvokeDisplay using Parameters Comments


Display DisplayName
Detail Display “TPN_Detail” PointName [string] First page will be shown if
SelectedPage parameter is omitted.
SelectedPage [1..] {optional}
ErrorMsg will be set to “CAN NOT
FIND POINT” if invalid point name
has been given.
Group Display “TPN_Group” GroupNumber [1-450] Group numbers 401-450 will invoke
the Module Group Display.
Module Group SelectedSlot [0-8] {optional}
Display No slot will be initially selected if
SelectedSlot = 0 or omitted.

225
9 AUTHORING CUSTOM DISPLAYS

TPS/LCN Standard InvokeDisplay using Parameters Comments


Display DisplayName
Group Trend Display “TPN_Grptrend” GroupNumber [1-400] No slot will be initially selected if
SelectedSlot = 0 or omitted.
SelectedSlot [0-8] {optional}
System Status “TPN_Sys_stat”
Display
System Menu “TPN_Sys_menu”
Display
Alarm Summary “TPN_Alarmsum” UnitNumber [0-36] {optional}
Display
Message Summary “TPN_Msgsum”
Display
Console Status “TPN_Consstat”
Display

226 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

9.8 Script Examples for Invoking Displays

9.8.1 Invoking TPS Schematic from HMIWeb Display


To invoke a TPS/LCN schematic, follow the Experion documentation. The following example shows invocation
of the schematic “boilr22.”
Sub pushbutton001_onclick
window.external.currentpage = “boilr22”
End Sub

9.8.2 Invoking TPS/LCN Point Detail from HMIWeb Display


To invoke a point Detail display for a TPS/LCN point, follow the Experion documentation. The following
example shows invocation of the point “am2r0001.”
Sub pushbutton002_onclick
window.external.RequestTask 21, 73, 0, 0, 0, “am2r0001”
End Sub

If the TPS/LCN point Detail display must be positioned on the second page (instead of the default first page),
the TPSCommands object must be used explicitly:
Sub pushbutton003_onclick
set tpscmd = CreateObject(“TPS.Commands”)
tpscmd.InvokeDisplay “TPN_Detail”, “am2r0001”, 2
Window.external.MessageZoneText(tpscmd.ErrorMsg)
End Sub

9.8.3 Invoking TPS/LCN System Status Display from HMIWeb Display


Sub pushbutton004_onclick
set tpscmd = CreateObject(“TPS.Commands”)
tpscmd.InvokeDisplay “TPN_Sys_stat”
Window.external.MessageZoneText(tpscmd.ErrorMsg)
End Sub

9.8.4 Obtaining PSDP data in HMIWeb Display


Tip
The SY unit is required to be mapped in order to read PSDP values.

Use the PSDP (Processor Status Data Point) data for a node to obtain the CPU usage at the LCNP board:
' the shape has a text object that presents current CPU usage (%free) at the lcnp board
' the shape's parameter PRSTS_TAG is this node $PRSTS point
Sub Page_onshapeload
set tpscmd = CreateObject(“TPS.Commands”)
MyNode = tpscmd.NodeNumber
if MyNode < 10 then
PRSTS_TAG = “$PRSTS0” & Cstr(MyNode)
else
PRSTS_TAG = “$PRSTS” & Cstr(MyNode)
end if
End Sub

227
9 AUTHORING CUSTOM DISPLAYS

9.9 Automatic priming of TPS points on Experion

9.9.1 What is autopriming?


The autopriming function populates the TPN Server cache with internal LCN references to ensure a fast initial
data access for TPN point parameters. With the Experion R400 the autopriming option is available on ES-T,
ESVT and ACE-T nodes. Autoprime removes the need for local manual priming. Experion server database is
populated when the point parameters are accessed for the first time.
With Experion R400 TPN Server uses a new compact cache format supporting the priming of all points and
parameters on the local LCN. Autopriming can be enabled or disabled on each ESVT.
Before moving the nodes to the production LCN, TPN Server checkpoint files must be deleted from all the
nodes in the ESVT cluster. This drives an automatic re-generation of internal ids, which is required when
connected to the production LCN. Follow the procedure for deleting the checkpoint file:
1. Stop the TPN server
2. Copy TPN server checkpoint from the ESVT node and rename to match the TPN Server checkpoint file
name on the node to be copied.
3. Restart the TPN server

9.9.2 Off-line development LCN used with simulator nodes to build and test displays
Before moving the nodes to the production LCN, it is recommended that TPN Server checkpoint files are
deleted from all the nodes in the ESVT cluster. This avoids the automatic re-generation of internal ids, which is
time consuming, in the TPN server caches when connected to the production LCN. Follow the procedure for
deleting the checkpoint file:
1. Stop TPN server
2. Delete TPN server checkpoint file
3. Power down the node

Pre-requisites for Autopriming


To ensure proper operation of lookup and import into local cache of primed points from the ESVT over the
network, the following conditions must be met:
Password of the local account under which the TPN Server process is running (LocalComServer) must be the
same on all nodes in the ESVT cluster. Password is provided during installation of the node.
Firewall must be open for the TPNServer process (tpndss.exe) on all nodes in the ESVT cluster. Firewall is
open automatically during installation of the nodes.
If the autoprime option is disabled, ESVT does not automatically browse and prime all points on the TPN.

9.9.3 Features of autopriming


There is an “Autoprime” option available on each ESVT node. Other nodes in the ESVT cluster (ES-T, ACE-T)
get the internal LCN references from the ESVT TPN Server caches when needed avoiding the need for any
additional priming.
When the Autoprime option is enabled, the ESVT automatically primes all the points on the LCN. All
parameters that are configured on the LCN points are primed in the TPN Server. TPN server on the ESVT node
performs the autoprime every time the server restarts. The first-ever conversion of a point and all its parameters
takes approximately 3-4 seconds.

228 www.honeywell.com
9 AUTHORING CUSTOM DISPLAYS

The TPN Server Auxiliary status display on the ESVT System Management display shows the status of the
autopriming client.
Note: Once the point has been primed, its internal representation is saved in the TPN server checkpoint file.
Thereby, on the subsequent restart of the TPN Server the points are not converted on the TPN again.
The new points added to the LCN are detected and automatically primed by ESVT. When the new displays are
developed and added to the system, there is no need for additional priming as all points usually are primed by
then. If the ESVT nodes are offline, newly added points on the local LCN are detected when the ESVT nodes
come back online, due to the regular autopriming/browsing activities. Points that are deleted from the LCN are
automatically deleted from TPN Server caches.

9.9.4 Need for local priming


In some scenarios, nodes must prime point(s) locally on LCN, without importing point conversion data from the
ESVT.
When the initial automatic prime is in progress on the ESVT and some of the points have not yet been primed
Points not in the scope of autoprime (For example, remote LCN points using Network Gateway access)
LCN data owner was down while ESVT was autopriming (and the node came back online since then)
ESVT node (both nodes if redundant ESVT nodes) is down when a node tries to access a point for the first time.

229
9 AUTHORING CUSTOM DISPLAYS

9.9.5 Parameter Conversion Timeout


The “Parameter Conversion Timeout,” if enabled, sets the time limit for conversion of a group of items. If any
of the parameters are not primed within allocated time, TPN Server indicates the items that did not convert
using the E_PENDING error code.
On Experion APP nodes, the conversion-pending timeout is disabled by default. You can enable it, if all the
clients of the TPN Server can react properly on the E_PENDING errors.
Note: Some clients of the TPN Server can internally override the value of the Conversion Timeout. Experion
client internally chooses a specific timeout value depending on what kind of data is being requested.
If the parameter is NOT in Experion Database, the system displays “reloading the page” message. However, if
the parameter exists in Experion database, the system displays “item converting” message.

Migration from previous releases


After migrating to a new release, the TPN Server uses the checkpoint file that has been created in the previous
release. The R400 TPN Server backups the checkpoint file of the previous release and creates a checkpoint file
using the new internal compact format.

TPN Server checkpoint deleted


If the TPN Server is started without checkpoint, it will rebuild its cache by collecting data from the TPN Server
cache on the ESVT node. If the TPN Server is started on a redundant ESVT node without checkpoint, it
synchronizes to the internal cache of the TPN server on the other ESVT node. However, in case of a non-
redundant ESVT node, the full initial autopriming will happen.

9.9.6 ESVT node is down


When the ESVT node is down (both ESVT nodes if ESVT is redundant) and the first ever data access is
requested from the TPN, the points are converted locally and only the local cache is updated.
Note:
1. First ever access to the TPN on an ES-T node may take a longer time if the ESVT node is not available or it
has not finished initial priming of the TPN yet. HMIWeb display may need to be re-invoked until all
parameters on the display have been converted by the local TPN Server.
2. After the initial priming has been completed on the ESVT nodes, the ESVT TPNServer checkpoint can be
manually copied over (and renamed) to other nodes in the cluster, if the network may not available during
normal operation.

Experion APP node


The Experion App node does not participate in autopriming. The TPN Server priming actions are executed
locally when requested by the clients. You can configure the conversion-pending timeout option for TPN Server
on Experion App nodes. TPN Server cache and checkpoint are in new compact form.
Note: The “Parameter Conversion Timeout,' can only be enabled, if all the clients of the TPN Server can react
properly on the E_PENDING errors codes that are returned when adding items to an OPC group. If the error
persists, the client is usually expected to retry the attempts to prime.

Multiple ESVT clusters on the same LCN


Each ESVT cluster is automatically primed with all the points from the LCN regardless of which LCN units are
mapped to each cluster.

230 www.honeywell.com
10 GUS Functionality on ES-T

231
10 GUS FUNCTIONALITY ON ES-T

10.1 GUS Functionality Summary

10.1.1 Operating System Support


GUS components (Native Window, GUS Display Builder) and Runtime components perform on the operating
systems supported on the Experion nodes. This includes the base TPS components for all operating systems
supported on the Experion Server, ACE-T and Console and Console - Extension nodes. GUS functionality in
Experion is described in the following section.

10.1.2 GUS Display Builder


Functionality of the GUS Display Builder is unchanged in Experion. GUS Display Builder can be installed on
any node as long as the hardware and operating system requirements are met; however, the on-line GUS display
validation capability is only available on the ES-T and Experion-TPS Console-Extension (CE) nodes.

10.1.3 GUS Display Runtime


Functionality of the GUS Display Runtime is generally unchanged in the ES-T. GUS display runtime only
operates on Experion Station and Experion-TPS Console - Extension nodes with TPS options. Operation on the
Console - Extension nodes with TPS options (and the hosting ES-T) nodes is equivalent to the operation of the
GUS Remote Displays cluster, with its limitations (for example, lower limit on maximum number of concurrent
GUS displays). The following exceptions apply:
GUS displays are intended to support current TPS applications, referencing local TPN data. They may also
access any remote data that is available via HCI/OPC, using the current HCI data client. However, this
capability does not support integrated control applications involving data from Experion controllers. Such
applications require the use of HMIWeb displays.
The GUS Alarm Window ActiveX control is not supported on Experion nodes with TPS options. Existing GUS
displays that are embedding this control will present the standard “control not installed” error. Instead, these
displays can be user updated to invoke the Experion Alarm Summary as a separate display. The Alarm
Summary requests will invoke the Experion Alarm Summary display in the Experion Station. The GUS Alarm
Window ActiveX control is not included in the installation packages; the supporting TPN load modules
(GUSALA, GUSALAG) should not be configured for ES-C nodes.
The GUS Button Service is not available on Experion nodes with TPS options. In GUS, pressing a focus
independent key (for example, SCHEM) while a GUS display is in focus results in a dialog requesting operator
input. On Experion nodes, the Experion Station command prompt window will processes operator's input.
Generally, the IKB/OEP focus independent keys will be serviced by the Experion Station or by the Native
Window. The Native Window will also service by the Experion Station or the engineering keyboard function
keys, when a GUS display is in focus. Note: per ES-T convention, the Experion Station processes the focus
independent keys first; if Experion does not define action for the key, this key will be transferred to the Native
Window. The focus dependent keys (ACK etc.; in some cases DETAIL) will operate unchanged when GUS
display is in focus.
Display interactions with Native Window are supported on the ES-T node, even if the node is hosting Console -
Extension nodes with TPS options. Native Window can be re-assigned to the ES-T if it is currently active on
another node. In TPS, the GUS Remote Displays Client that is running on the GUS Remote Displays Server
disables such interactions.

232 www.honeywell.com
10 GUS FUNCTIONALITY ON ES-T

10.1.4 GUS Remote Displays


The functionality of GUS Remote Display servers is included with the GUS Display Runtime on an ES-T.
Configuration options enable the remote displays service (servers), which then can service GUS Remote
Display Clients running on ES-CE stations connected to this ES-T.

10.1.5 Cross-Environment Display Invocation


Invocation of displays among the Experion Station and Native Window environments is possible and will
follow the rules where it requests Experion first:
The “Invoke Display” (and similar) requests from GUS displays attempt to invoke an Experion display first; if a
display is not found then Experion Station will be asked to invoke a GUS display. If this fails on a node, it will
result in a request to show the schematic in the Native Window.
The “Invoke Display” (and similar) requests from Experion Station will attempt to invoke an Experion display
first; if such display is not found then GUS runtime will attempt to show the display. If a GUS display is not
found then, on the ES-T node, the request will be presented to the Native Window.
On ES-T, invocation of displays from Native Window will attempt to invoke an Experion display first; if such
display is not found then GUS runtime will attempt to show the display. If a GUS display is not found then, the
request will be presented to the Native Window.
Invocation of displays using keyboard keys follows the route of the display invocation from the Experion
Station, with the exception for the case where the Native Window is servicing a programmable key that contains
an invocation of a standard display. On an ES-T, display invocations resulting from the SCHEM and GP_PRO
actors in Native Window will first consult Experion Station.

10.1.6 GUS HCI Client


Access to HCI/OPC data (for example, a third party OPC server) from GUS displays continues to be possible
using the GUS HCI Client. Note: GUS collectors (for example, ACKSTAT) operate unchanged in GUS displays
and are applicable to the HOPC Server/TPN data only.
Although data from Experion controllers would also be available through this mechanism, it is strongly
recommended that HMIWeb displays be used for integrated control involving Experion controllers.

10.1.7 Local TPN Server


The TPN Server that is running on an ES-T node is private and is used mainly by the Experion system direct
data access components. Custom applications wishing to access TPN may do so by connecting to the Experion
OPC Server that is running on the Server.

233
10 GUS FUNCTIONALITY ON ES-T

10.2 Handling F1-F17 keys when GUS application is in focus


This section explains how the keyboard function keys respond in different application environments.

Tip
GUS is an optional package.

10.2.1 Function key behavior


In the regular TPS GUS, the function keys F1-F17 (PF1-PF17) are serviced by the GUS button service, which
processes the keys according to the definition in the LCN area button file. On an ES-T, the F1-F17 keys are
processed by the application that has input focus. When a GUS application (GUS display, GUS Group Display
or GUS Faceplate) has input focus, the F1-F17 keys will be directed to:
GUS application if the key action has been configured in the registry.
Experion station if NULL action has been defined.
Regular Windows processing, if there is no registry definition for this key.
By default, installation of the GUS Display Runtime configures the following key actions in the registry:

Key Action
F1 HELP
F2 PRIOR DISP
F9 ACK
F15 (PrintScreen) MAN
F16 (Scroll) AUTO
F17 (Pause) NORM
Ctrl/F9 FAST
Ctrl/F12 MSG CLEAR
Ctrl/F17 RAISE
Shift/F2 ASSOC DISP
Shift/F12 MSG CONFIRM
Shift/F15 OUT
Shift/F16 SP
Shift/F17 LOWER

The remaining Fn/Ctrl/Shift key combinations have NULL assignment and will be redirected to the Experion
station.
Other applications will process F1-F17 keys according to this application configuration. In order to achieve
consistency of the F1-F17 key actions across applications, each application's key configuration data may have to
be modified. For example, Native Window will follow key actions as defined in the current LCN area button
file; Experion station and displays will process keys according to the definition in the station keyboard
configuration ( .stb) file.

Tip
GUS and Native Window applications do not recognize ALT key as key modifier.

234 www.honeywell.com
10 GUS FUNCTIONALITY ON ES-T

Tip
The assignment of the F1 - F17 keys for the GUS applications is stored under the following registry key: HKLM/
Software/Honeywell/ESTGusKey. The registry editing tool REGEDIT must be used to change this configuration;
then replicated on each ES-T and Experion-TPS Console-Extension node (with help of exported .reg file).

235
10 GUS FUNCTIONALITY ON ES-T

236 www.honeywell.com
11 Managing Operations, Alarms, and Events

237
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.1 Managing Scope of Responsibility


Scope of Responsibility (SOR) represents the set of the entities for which an operator is responsible. The Scope
of Responsibility consists of the currently assigned TPS/LCN Area (assigned using Native Window facilities),
the Experion Asset (assigned using Experion Enterprise Model Builder and/or System Interface Unit Mapping),
and the operator's SOR. For an ES-F connecting through a Server, the SOR is defined using Experion Enterprise
Model Builder and/or System Interface Unit Mapping with TPS/LCN Units mapped to Experion Assets.

11.1.1 About Enterprise Model


The Enterprise Model provides a means of organizing the core operational environment around a hierarchical
asset model; typically configured to represent the physical assets of the plant or mill. The Enterprise Model is
fully integrated with the TPN. One Experion Server in your system must include the Enterprise Model Database
(EMDB).

11.1.2 Use Enterprise Model Builder to create Assets


The Enterprise Model Builder is an application that allows you to configure the Experion scope of
responsibility. Enterprise Model Builder is a standard tool in the Configuration Studio. EMB supports the
configuration of the Asset Model and Alarm Groups.

238 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.1.3 Unit to Experion Asset relationship


TPN Units (and the points that they contain) can be associated with Enterprise Model Assets in the same way
they were previously associated with Areas. TPN units are mapped to Experion assets either through
configuration or direct mapping.
The following figure shows a direct mapping relationship of TPN Units and Experion Assets. In this example,
the Experion Assets have been configured with the same names as the TPN Unit names in order to support
direct mapping of units to assets.

239
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

The following figure shows a hierarchical asset configuration where Experion Assets have several levels; in
other words, an Experion Asset is a child of another Experion Asset. In this example, TPN Units T1 and T2 are
mapped to Assets Tank1 and Tank2 respectively. TPN Unit A2 is mapped to the Experion Asset Mixer1.
Because Experion Assets Tank1 and Tank2 are children of Mixer1, TPN Units T1 and T2 are also in effect
mapped to Experion Asset Mixer1.

A TPN Unit can only be mapped to one Experion Asset. More than one TPN Unit can be mapped to an Asset,
but the Unit itself can only be assigned to one Asset. Assets can be structured in a hierarchy as shown in the
figure.

240 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.1.4 Assignment of assets


Mapping units to assets also means that you can manage TPS data and notifications in an appropriate manner.
For example, you can configure particular Stations, Consoles, or Operators so that they can only receive
notifications from certain TPS units (mapped to assets) through alarm and event management configuration.

Attention
The Scope of Responsibility (SOR) of the Operator includes Experion Controller Assets and assets that contain LCN
Units. On integrated Experion-TPS ES-T nodes, this is also qualified by the current LCN area.
If the LCN Unit is not in the current LCN area, the Operator will not have access to this Unit.

241
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Figure 1: Operator Assignment Page

11.1.5 Mapping of TPS/LCN Units to Experion Assets


A display supports the configuration of TPS/LCN unit names to the Experion Assets of interest. For details, see
“Map TPS Units to Experion Assets” on page 109. Note that depending on the option you select, System Unit
SY unit also must be properly mapped.

11.1.6 Mapping when more than one LCN is connected to Experion using DSA
If you are connecting more than one LCN to an Experion system that has DSA between its ESVTs, then:
You must select the mapping option, “Map TPS Units as follows;”
For each LCN, you must map each TPS system reserved unit, SY, to its own Experion Asset. You should give
that Asset that's meaningful to your personnel;
If duplicate TPN point names occur in same named units on multiple LCNs, each unit must be mapped to its
own Experion Asset. For example, LCN1 has Unit AA with point A100. LCN2 also has a Unit AA with point
A100. In this case, each unit should be mapped to its own Experion Asset.

242 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.1.7 Enabling alarming for Experion Assets with mapped TPS Units
Operators will not be able to access TPS/LCN units that are not mapped to Assets.
If the Experion SOR is not “Full Access” and if the Experion SOR excludes particular TPS/LCN units, this
operator will not be able to see alarms from these units, even though they may be in the current TPS/LCN SOR
(TPS/LCN Area).
If the Experion SOR has TPS/LCN units that are not in the current TPS/LCN SOR (TPS/LCN Area), then this
operator will not be able to see alarms from these units.
1 Enable or disable alarms for the assets from Configuration Studio. Select Alarms and Event Management.

2 Select Configure alarm and point processing.

243
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

3 From the resultant display, enable or disable alarms for your assets.

4 From the System Interfaces screen, click the link to the Asset Assignment display. Using links from this
display, assign Experion Assets (TPS/LCN Units) to Consoles, Console Stations, Flex stations, and
Operators to define the Scope of Responsibility (SOR).

11.1.8 TPS/LCN Area Change


A TPS/LCN Area Change is accomplished using the Native Window Console Status display. When the
TPS/LCN Area is changed, the Experion Alarm display refreshes to show the current alarms in the new
TPS/LCN Area.

244 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.1.9 Super area


One of the styles of TPS/LCN Scope of Responsibility (SOR) management is the super area. With this style, up
to 36 TPS/LCN Units are put in a single TPS/LCN Area and the Area is assigned to an Asset for the stations in
the console.
Operators manage the units in their SOR by individually enabling and disabling units through the Console
Disable/Enable function presented on the TPS/LCN Unit Assignment display.
An ES-T allows the super area style of SOR management.

11.1.10 KEYLEVEL.KL File Access Overview


With Experion R310.1 and later, the TPN Server will implement the functionality of the Configurable Access
Levels contained in the KEYLEVEL.KL file.

Attention
Only the KEYLEVEL.KL method of configurable access levels is supported. The following access levels are NOT
supported.
• Detail/Group Display
• $AUXUNIT
• ALENBST
• Box Variables
• Parameter Groups

The KEYLEVEL.KL will be read in from the History Module by the TPN Server during start-up of the TPN
Server. If the file exists on the HM, the KEYLEVEL.KL file will be read and a new file created in the C:
\ProgramData\Honeywell \Databases for use by the TPN Server.

Attention
With the Custom Install Path (CIP) supported in Experion R410, you can change the default path of installation (C:
\ProgramData\Honeywell) to any possible path.

Since no syntax checking is performed by the TPN Server, the user will have to correct the syntax errors in the
KEYLEVEL.KL file using the LCN Text Editor.
Syntax errors can be viewed using the native Window Auxiliary Status Display.
If the KEYLEVEL.KL file does NOT exist on the HM, then no key level changes will be applied at write time.
If, however, the file cannot be read, the system HM is down or unavailable, then the TPN Server will use its
locally created PC-side file, if one already exists.
Upon a successful read of the HM's KEYLEVEL.KL file, the TPN Server will create an internal mapping of
LCN parameter number. This number is obtained by converting the LCN parameter name in the file to access
level obtained from the file.
The KEYLEVEL functionality will be available on the Console Station irrespective of the availability of the
Cluster Server.

11.1.11 HMIWeb display stores


For writes from HMIWeb displays, the Experion data access client uses the logged-in level of the Experion
Station, either operator-based or station-based security, to determine the level to be passed to the TPN Server.
This will not change.
However, the TPN Server will use this access level passed on each write request from Experion to determine the
actual store access level passed down to the LCN based on the KEYLEVEL.KL rules as shown in the following
table.

245
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Attention
VIEW level keylock cannot be directly set on the Native Window unless configured to do so in the Native Window
Console Status settings.

Experion Station Access Level Equivalent LCN Access Level for parameter in Resultant Access Level passed to
KeyLevel KEYFILE.KL LCN by TPN Server
MNGR ENGR P Store Rejected
MNGR ENGR E Engineer
MNGR ENGR S Engineer
MNGR ENGR O Engineer
ENGR ENGR P Store Rejected
ENGR ENGR E Engineer
ENGR ENGR S Engineer
ENGR ENGR O Engineer
SUPR SUPR P Store Rejected
SUPR SUPR E Store Rejected
SUPR SUPR S Engineer
SUPR SUPR O Engineer
OPER OPER P Store Rejected
OPER OPER E Store Rejected
OPER OPER S Store Rejected
OPER OPER O Engineer
ACKONLY VIEW P Store Rejected
ACKONLY VIEW E Store Rejected
ACKONLY VIEW S Store Rejected
ACKONLY VIEW O Store Rejected
VIEW VIEW P Store Rejected
VIEW VIEW E Store Rejected
VIEW VIEW S Store Rejected
VIEW VIEW O Store Rejected

11.1.12 TPN Server Auxiliary Display indicator


On the main tab of the TPN Server Auxiliary Display, at the bottom, there will be an indication that shows the
time that the KEYLEVEL.KL file was most recently read in from the HM along with how many parameters
were read in.

Tip
This only shows for ES-T and ESVT nodes (as opposed to Experion APP and ACE-T nodes).

246 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.1.13 Refresh the KEYLEVEL.KL file from the TPN Server Auxiliary Display
Use the demand checkpoint feature from the System Management Display, All Tasks->Checkpoint to refresh
the contents of the KEYLEVEL.KL file from the History Module. This will avoid having to stop and restart the
TPN Server if all you want to do is refresh the contents of the KEYLEVEL.KL file. In other words, when a
checkpoint is demanded or occurs on the auto-checkpoint frequency, then the KEYLEVEL.KL will also be
refreshed.

247
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.2 Managing Process Alarms

11.2.1 Experion Alarm Summary Displays


ES-T uses the Experion Alarm Summary displays which provide an integrated display of alarm notifications
from the local TPS/LCN, Experion, and other OPC-compliant event servers, including Honeywell applications
and third-party OPC event servers.
Alarms known to the local TPS/LCN are represented in both the Native Window TPS/LCN Alarm Summaries
and the Experion Alarm Summaries, with the same statuses (for example, acknowledgement status). This
consistency is maintained on a console wide basis. The Experion Alarm Summary display consists of Alarm
Groups, Assets, and System Components.

Customizing the Experion Alarm Summary Display


You can customize the alarm summary to filter, sort, and view alarms.

Note
“Trip Value” column is displayed on the Experion Alarm Summary by default, whereas “Alarm Limit” column is
displayed on the Native Window Alarm Summary. You can customize the Experion Alarm Summary to show
“Alarm Limit” column instead of “Trip Value” column if you prefer to view the same column information as can be
viewed from the Native Window Alarm Summary.
Trip Value: The actual value at which the point was when it went into the alarm state.
Alarm Limit: The value of the actual trip limit that was exceeded, for example, PVHITP’s value.

For more information about customizing the alarm summary, refer to the Server and Client Configuration
Guide.

11.2.2 Enable/Disable/Inhibit
Experion follows the same convention as OPC for alarm enable and disable, where disable corresponds to the
TPS/LCN inhibit. Experion-TPS nodes support the Experion/OPC convention as follows:
TPS/LCN System Disable and Inhibit and Console Disable will be reflected as an OPC Disable to Experion.
Pseudo disable/inhibit conditions such as box idle and contact cutout will also be reflected to Experion as
Disables.
You may perform any Enable/Disable/Inhibit using existing Native Window functions and the disable is
reflected on all the appropriate Experion displays.
Generally, in the Experion alarm approach, alarms are not removed from the Experion Alarm Summary without
the operator's knowledge. The TPS/LCN Console Disable (shown in the following figure) is an exception,

248 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

where alarms are automatically removed from the selected TPS/LCN Unit on the Native Window Alarm
Summary and on the Experion Alarm Summary.

11.2.3 Enable/Disable audible alarm suppression


Attention
Experion R410 supports suppressing audible annunciations on the Experion Alarm Summary display.

For more information on suppressing audible alarms, refer to the Server and Client Configuration Guide,
Operator's Guide, and Server and Client Troubleshooting Guide.

11.2.4 Correctly manage disabled alarms on ESVT


Prior to TPN R680, the ESVT received ALENBST=DISABLED alarms. With TPN R680, there is an option in
the NCF, which will not allow Experion to display ALENBST=DISABLED alarms on an ESVT, but rather
journal them.
This indication is applicable for process alarms generated by AM, NIM and HG and SOE alarms for HG.
In the NCF, an option (YES/NO) is provided for the optional selection of this functionality. The option is to be
specified in the System Wide Values/ Console Data portion of the NCF.

249
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

If the NCF option “ALENBST INDICATION IN JOURNAL FOR DISABLED ALARMS” is set to NO, and
the point's ALENBST parameter is set to DISABLED, then ALENBST=DISABLED alarms
appear on the Alarm Summary of the ESVT (or Flex Station's)
are journaled to the Experion Event Summary
If the NCF option “ALENBST INDICATION IN JOURNAL FOR DISABLED ALARMS” is set to YES, and
the point's ALENBST parameter is set to DISABLED, then ALENBST=DISABLED alarms
DO NOT appear on the Alarm Summary of the ESVT (or Flex Station's)
are journaled to the Experion Event Summary

Attention
You must ensure the following to correctly manage the disabled alarms on an ESVT:
• At least the R680 LCN software
and
• NCF option “ALENBST INDICATION IN JOURNAL FOR DISABLED ALARMS” set to YES
The older versions of the LCN (pre R680) software will continue to function as before but without this new
functionality.

If you decide to enable the NCF option in TPN R680 and use the new functionality in R310, the following
difference in behavior is observed between the ES-T and ESVT.
When you change the ALENBST parameter of a point which has an active alarm from DISABLE to ENABLE,
the ESVT Alarm Summary (or Flex Alarm Summary) will display the timestamp of when the alarm was
originally generated. The ES-T Alarm Summary will display the timestamp when the ALENBST parameter was
reset to ENABLE and the data owner re-generated the alarm and sent it to the underlying Native Window alarm
list; the ESVT does not receive this regenerated alarm, and uses the original timestamp.

Attention
The ES-T and ESVT's alarm summaries are different. The ES-T's Alarm Summary is the only one considered to be in
synch with the Native Window. Never operate alarms or count on their accuracy on their state from an ESVT. New
alarms will be received on an ESVT, but their state management (ACK, ENA, timestamp) is not guaranteed. To
summarize, it is best to operate on TPS alarms from the ES-T.

11.2.5 Alarm presentation

HMIWeb displays
Alarm presentation and acknowledgement in user-authored HMIWeb displays offer the functionality found in
Experion. Acknowledgement of a TPS/LCN alarm from an HMIWeb display is reflected at all ES-T's in the
Console.

Alarm Group equivalence to PRIMMOD


ES-T Alarm Group functionality, for both standard alarm displays and HMIWeb displays, is the equivalent to
the PRIMMOD alarming functionality found in TPS/LCN. To import your existing Primmod groups, refer to
“TPS PRIMMOD and Experion Aggregate Alarming.”

250 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Sequence of Events
The TPS/LCN sequence of events (SOE) notifications is archived on the Server and can be viewed from an ES-
T through the Experion SOE Summary Display.

Alarm List Overflow


An alarm list overflow on the underlying US, results in a system status event notification sent from the LCNP to
the Windows resident Experion software. The display associated with the notification of a TPS/LCN alarm list
overflow is the TPS/LCN Alarm Summary Display, allowing the operator to use the TPS/LCN Alarm Summary
Display to take corrective action.
Since the Experion alarm list accommodates 2000 notifications, it is likely that the Experion Alarm Summary
display will have the notifications that were lost from the TPS/LCN Alarm list due to overflow. An operator
may wish to take no corrective action (that is, to resynchronize with the Alarm Summary Display), because it
could result in the loss of alarms, and because the alarm summaries will eventually resynchronize after the
overflow condition is resolved.
Alarm list overflow conditions on the Experion alarm list is not reflected in any TPS/LCN Native Window
displays.

TPS/LCN Lost Events Notification and Recovery


When an ES-T detects a lost TPS/LCN event condition, a System Event Notification is generated and the LED
on the SYS STATS key indicates the presence of an unacknowledged system alarm.
Pressing the SYS STATS key results in presenting the Experion System Status display and the display contains
a notification of the lost events. Invocation of the associated display for the Lost Event notification results in the
invocation of the TPS/LCN Area Alarm Summary in the Native Window, allowing the operator to initiate the
event recovery process and observe its progress.

11.2.6 Changing Alarm Priority to NOACTION or PRINTER


Changing Alarm Priority on ESVT
1 On the Server node, ensure that the alarm condition is returned to normal (RTN) before changing the alarm
priority to NOACTION or PRINTER. On an ES-T node, the user may change the alarm priority parameters
to any value regardless of whether the alarm is active or not.
2 On a Server node, if you change an alarm priority parameter from a value of LOW, HIGH, or EMERGNCY
to a value of PRINTER or NOACTION while the alarm is active (still in ALM), then the Experion Alarm
Summary on a Server node will give the appearance of a “stuck” alarm.
3 To remedy a “stuck” alarm on the ESVT that occurred due to the above condition, perform the following
steps:
• Change the alarm priority parameter (for example, PVHIPR or PVROCPR) back to LOW, HIGH, or
EMERGNCY. This should cause the alarm to re-alarm.
• Ensure that the alarm condition is returned to normal (RTN).
• Change the value of the alarm priority parameter to PRINTER or NOACTION.

Tip
Because the Server is an alarm journaling mechanism (similar to the History Module), the TPS/LCN alarm
queue that it “hears” does not receive PRINTER or NOACTION alarms.

Changing Alarm Priority on ES-T


1 On an ES-T node, if you change the alarm priority parameter from LOW, HIGH, or EMERGNCY to
JOURNAL, JNLPRINT, PRINTER, or NOACTION, then an intentional inconsistency will exist between
the Native Window Alarm Summary and the Experion Alarm Summary.
2 The Native Window Alarm Summary automatically removes unacknowledged and acknowledged active
(ALM) alarms when the alarm priority changes to JOURNAL, JNLPRINT, PRINTER, or NOACTION.

251
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

3 The Experion Alarm Summary does not remove unacknowledged alarms, but marks their state as Disabled
(grayed out) and Inactive (RTN). When the state changes to Acknowledged, they are removed. This is
consistent with other Experion Alarm Summary alarm sources, such as C200 controller alarms.

Attention
If the ES-T receives a TPS/LCN event (such as an Area change) that forces a re-read of the Native Window Alarm
Summary, then the Experion Alarm Summary re-synchs with the Native Window Alarm Summary (through the
TPN Server). The re-synch removes those alarms from the Experion Alarm Summary that were shown as
unacknowledged or disabled, and that had been removed already from the Native Window Alarm Summary.

11.2.7 Changing the values of ALMFMT and DIGALFMT parameters


Honeywell recommends that you change the values of the ALMFMT and DIGALFMT parameters only when
their point is NOT in alarm.
If you change ALMFMT or DIGALFMT while the point is in alarm, depending on what alarm format you
choose, a “stuck” alarm may result on the Server's Experion Alarm Summary. The only known remedy for this
“stuck” alarm condition is to stop and restart the TPN Server component on the Server (see “Stuck alarms on
ESVT” on page 252 for the procedure).
The ES-T's Experion Alarm Summary may be more tolerant of changes to the ALMFMT or DIGALFMT
parameters while the point is in alarm.

Attention
Always ensure that the point is not in alarm before attempting to change the ALMFMT and DIGALFMT parameters.
It is NEVER advisable to change these parameters while the point is in alarm.

11.2.8 Deleting points that are in alarm


Attention
In order to avoid confusing or inconsistent alarm reporting, do not delete:
• Points that are in alarm
• Connections to points that are in alarm
• Points that are connected to points that are in alarm

11.2.9 Stuck alarms on ESVT


Two situations described above (see and “Changing the values of ALMFMT and DIGALFMT parameters” on
page 252) can cause ESVT alarms to appear to be “stuck” in the alarm summary. There are other scenarios
where alarms may appear to be stuck in the alarm summary. For example, this may occur when an ESVT
receives a Box Idle, Node Failure, Hiway Slot Failure, or Hiway Box Failure event from the LCN. When one of
these LCN events causes a “stuck” alarm condition, stop and start the TPN Server by performing the following
steps:
From the System Management Display, select the TPN Server component on the ESVT. Right-click and select
All Tasks > Stop.
After the TPN Server shows a status of “Stopped,” right-click on the component and select All Tasks > Start.

11.2.10 Managing sequence program (PROCMOD) alarms


Honeywell recommends that you operate a PROCMOD point (sequence program) from its Native Window
Detail display.
The sequence program alarm state (ALM/RTN) shown on the Experion Alarm Summary may not be consistent
with the alarm state shown on the Native Window Alarm Summary. You should use the Experion Alarm

252 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Summary as an indication that there is an outstanding sequence program alarm, and as a pointer to the Native
Window Detail Display for that PROCMOD point. Prior to acknowledging the sequence alarm, you should
always invoke the Native Window Detail Display to learn the exact status of the sequence program.
The Experion Alarm Summary shows only one sequence alarm per source name. The condition name of the
sequence alarm is always $SEQALM. For example, there may be four sequence alarms shown on the Native
Window Alarm Summary (one in ALM, the other three in RTN); however, only the latest sequence alarm will
be shown on the Experion Alarm Summary.
If you acknowledge the one sequence alarm from the Experion Alarm Summary, it acknowledges all of the
outstanding sequence alarms (from that source name) down to the TPS/LCN.

11.2.11 Disabling PROCMOD (sequence) point alarms


The PROCMOD point does not have an ALENBST (alarm enable status) parameter.
If you perform a System Inhibit or a System Disable for a TPS/LCN Unit from the Native Window Unit
Assignment display, the ALENBST parameter of all the points in that unit will be set to either INHIBIT or
DISABLE, respectively. Points (like PROCMOD) that do not have the ALENBST parameter are not affected.
The TPN Server has no knowledge of the ALENBST parameter, but the System Inhibit or System Disable event
triggers the ES-T's TPN Server to “disable” (Experion paradigm) alarms for all points in the TPS/LCN Unit,
including the PROCMOD (sequence) points that are in alarm.
When you perform a System Enable for the TPS/LCN Unit, the data owners (AM, NIM, and HG) re-alarm the
points that are still in alarm. This may cause the sequence alarms on the Native Window Alarm Summary and
Experion Alarm Summary to be out of synch.
The TPN Server relies on the data owners to re-send their alarms to populate the Experion Alarm Summary;
however, this does not happen for PROCMOD (sequence) alarms, so the TPN Server cannot re-send the
outstanding PROCMOD alarms to the Experion Alarm Summary.

Sequence Alarm Example 1


The PROCMOD point named PRCMD01 in TPS/LCN Unit 01 has an acknowledged, active sequence
alarm.

Action Behavior on Native Window Alarm Summary Behavior on Experion Alarm Summary
1. The user performs a No change for PRCMD01, as there is no Alarm for PRCMD01 disappears, because it
System Inhibit or System ALENBST parameter for a PROCMOD is already ACKd.
Disable on TPS/LCN point.
The TPN Server marks it (and every other
Unit 01.
The alarm is left on the screen, as source in TPN Unit 01) as “disabled,” which
acknowledged. is a condition for removal.
2. The user performs a The data owner (NIM or HG) does not re- The data owner (NIM or HG) does not re-
System Enable on TPN alarm this alarm. alarm this alarm.
Unit 01.
There is no change for PRCMD01. The alarm is not re-alarmed on the Experion
Alarm Summary.
The alarm is left on the screen.

Sequence Alarm Example 2


The PROCMOD point named PRCMD01 in TPS/LCN Unit 01 has an unacknowledged, active sequence
alarm.

253
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Action Behavior on Native Window Alarm Summary Behavior on Experion Alarm Summary
1. The user performs a No change for PRCMD01, as there is no Alarm for PRCMD01 changes to the disable
System Inhibit or ALENBST parameter for a PROCMOD point. state (grayed out), because the TPN Server
System Disable on TPN marks it (and every other source in TPN
The alarm is left on the screen, as
Unit 01. Unit 01) as “disabled.”
unacknowledged.
2. The user performs a The data owner (NIM or HG) does not re-alarm The data owner (NIM or HG) does not re-
System Enable on TPN this alarm. alarm this alarm.
Unit 01.
There is no change for PRCMD01. The alarm is not re-alarmed on the Experion
Alarm Summary.
The alarm is left on the screen.
The alarm remains disabled.

Attention
If the ES-T receives a TPS/LCN event (such as an Area Change) that forces a re-read of the Native Window
Alarm Summary, then the Experion Alarm Summary re-synchs with the Native Window Alarm Summary
(through the TPN Server) and the outstanding sequence alarms will be shown on the Experion Alarm Summary.

11.2.12 Using SOE points


The sequence of Events (SOE) alarm for the Hiway Gateway's (HG) HLPIU SOE point is supported in the
R301 (or later) Experion Alarm Summary on the ES-T or ESVT. Use the ES-T and ESVT load module versions
in the ULM media for respective Experion releases.
The alarm can be seen on the Native Window's Alarm Summary and in the Experion SOE Journal.

11.2.13 Alarm Shelving


Alarm shelving is a form of manual suppression that enables the operators to remove alarms from the main
alarm summary displays for a limited time.

CAUTION
Do not shelve TPS alarms with “unknown” timestamp. It is not supported.

You may experience the following problems if the annunciation is not setup properly for shelved alarms:
Annunciator is activated for a few seconds when a TPS alarm that has been shelved goes back into alarm.
Annunciator is silenced without operator interaction.
Refer to Section “4.11 Configure Audible Annunciation” to fix the problem.

254 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.3 Managing Operator Messages


The Experion Message Summary display provides an integrated display of messages from the local TPS/LCN,
Experion, and from other OPC-compliant event servers including Honeywell applications and third party OPC
event servers.
This section describes the differences in system response when an operator acknowledges or confirms a
message from the Experion Message Summary or from the TPS/LCN Message Summary. This section describes
message behavior for two types of messages: Informational (non-confirmable) and Confirmable.

11.3.1 Clear messages


With Experion R400, there is a user selectable option (called the Clear message required option) to manually
clear the acknowledged/confirmed messages from the Experion Message Summary.
When Clear message required option is selected, messages remain in the Message Summary in both Experion
and Native Window after ACKED (for Informational Messages) and ACKED/CONFIRMED (for Confirmable
Messages).
When Clear message required option is cleared, messages disappear from the Message Summary in both
Experion and Native Window after ACKED (for Informational Messages) and ACKED/CONFIRMED (for
Confirmable Messages).
With Clear message required option selected, if few messages are acknowledged/confirmed, they remain in
the Message Summary. Without manually clearing the messages, if the Clear message required option is
cleared, the acknowledged/confirmed messages disappear from the Message Summary.
The following message scenarios are described:
Experion acknowledgment
TPS/LCN acknowledgment
Mixed acknowledgment
Confirmed from other areas or consoles
TPS/LCN Area Change

Attention
Honeywell recommends that messages be acted upon, whenever possible, from the Experion Message Summary.

Refer to the Server and Client Configuration Guide for information on customizing the Experion Message
Summary.

11.3.2 Informational (non-confirmable) messages

Unacknowledged messages
Experion: blinking letter “I” icon
TPS/LCN: blinking red asterisk (*)

255
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Acknowledgement from Experion


Attention
Acknowledging messages from the Experion Message Summary acknowledges and clears the message from both
message summaries. You can change this setting for the operators to manually clear messages, using the Clear
message required option.
This approach provides the most effective way to keep your message summaries consistent.

Action: Right-click Acknowledge Message, or Acknowledge Page of messages (as shown in the following
figures).

Result: Acknowledges and Clears the message(s) in both message summaries, when Clear message required
option is not selected. That is, there is no need for an additional step to clear the acknowledged message(s) from
the TPS/LCN Message Summary. The message is acknowledged and remains in the Message Summary, when
Clear message required option is selected. To clear the message from the Message Summary,
Right-click the ACKED message
Click Clear Message in the shortcut menu

256 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Refer to the following documents for more information about clearing of messages.
• Server and Client Configuration Guide
• Operator's Guide
• Server and Client Troubleshooting Guide

Acknowledgment from TPS/LCN


Attention
This approach requires operator intervention to keep your message summaries consistent. An operator working from
the TPS/LCN Message Summary must manually clear the message from the TPS/LCN Message Summary.

Action: Acknowledge from any TPS/LCN Message Summary in the console.


Result:
Experion: Acknowledged and cleared (By default, acknowledged messages are cleared on Experion). You can
change this setting for the operators to manually clear messages, using the Clear message required option.
TPS/LCN: Acknowledged but not cleared (as shown in the following figure).

An operator using the TPS/LCN Message Summary must take an additional step to clear the message. The
following figure illustrates one method of clearing a message.

257
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

TPS/LCN area change


When a TPS/LCN Area change occurs, the operator should expect to see a system alarm in the Experion System
Status, indicating that an area change is in progress. The alarm automatically returns to normal upon Area
Change completion.

As a result of an Area Change, informational messages re-appear as acknowledged messages in the TPS/LCN
Message Summary. The messages do not appear in the Experion Message Summary, because acknowledged
messages are also cleared in Experion by default. The operator must clear the messages from the TPS/LCN
Message Summary.

258 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.3.3 Confirmable message behavior


Attention
• If using a station with no IKB then ACK twice to confirm a message on the Experion Message Summary. If you
are using a station with an IKB, then use the Confirm Message menu item or the MSG CONFM key.
• Confirming messages from Experion confirms and clears the message from both message summaries and the
TPS/LCN Process Module display by default. This approach provides an effective way to keep your message
summaries consistent.
• To keep message summaries and process module displays consistent, operators should acknowledge previously
confirmed messages from the Experion Message Summary.
• To keep message summaries and process module displays consistent as a result of a TPS/LCN area change,
operators should clear previously acknowledged and confirmed messages from the TPS/LCN Message Summary.
• Confirmable and non-confirmable messages do not appear on the Server only if the “Maintain unacknowledged
alarms for Experion - TPS” is unchecked.
• Honeywell requires the following NCF configuration setting, meaning that message confirmation will be allowed
only after Acknowledgment occurs:
CL Message Confirmation-After-Acknowledgement YES
• To keep message summaries and process module displays consistent, the Experion setting “Perform Auto
Acknowledge when Confirm Message key is pressed (IKB only)” should be unchecked.

Unacknowledged confirmable messages


Experion: blinking letter “C” icon
TPS/LCN: blinking red letter “c”
(See examples in the following figure.)

259
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Confirm from Experion


Action: Confirm an already acknowledged confirmable message.
Result: Confirms and clears the selected message in both message summaries.

Confirm from TPS/LCN


Action: Confirm an already acknowledged confirmable message.
Result: The message is cleared from the Experion Message Summary by default. If the Clear message required
option is selected, the message has to be manually cleared using the Clear Message option.

Acknowledge from TPS/LCN then confirm from Experion


If a confirmable message is first acknowledged from a TPS/LCN display and then confirmed at the Experion
Message Summary, the message is confirmed and cleared at both the Experion Message Summary and the
TPS/LCN related displays that support confirmable messages.

Confirm from other TPS/LCN areas or consoles


Example scenario:
Two ES-Ts: Station A and Station B
Same TPS/LCN Console
Different TPS/LCN Areas containing the same TPS/LCN unit
Action: Station A acknowledges a confirmable message from TPS/LCN display.
Result: Acknowledgement occurs at Station A only. At Station B the message appears as unacknowledged in
both Experion and TPS/LCN message summaries.
Action: Station A confirms the message from Experion.

260 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Result: Confirms and clears in both of Station A's summaries. At Station B, the message summaries provide
indications that the message is already confirmed, as shown in the following figure. Note: Messages that appear
already confirmed are regarded as informational messages in Experion.

Action: Operator acknowledges previously confirmed messages from Experion (as shown in the following
figure).
Result: Messages clear from the both message summaries.

Previously confirmed message then TPS/LCN acknowledgment


Action: Operator acknowledges an already confirmed message from a TPS/LCN display.
Result: Message is acknowledged and cleared on Experion by default. You can change the setting for the
operator to manually clear the message. On the TPS/LCN display, the message appears acknowledged, but not
cleared. The operator must clear the message from the TPS/LCN display.

TPN area change


An Area Change flushes alarms and messages from the TPN Server. When an Area Change completes, alarms
and messages are re-read from the Native Window alarm and message lists. Messages reappear in the TPS/LCN
Message Summary as acknowledged and/or confirmed, but not cleared. Experion regards the messages as
already acknowledged, confirmed, and cleared, so those messages do not appear in the Experion Message

261
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Summary. In this situation, it will be important for the operator to clear the messages resulting from an Area
Change from the TPS/LCN Message Summary.

11.3.4 Clear message before acknowledging


Action: Operator tries to clear message before ACKED/COMFIRMED.
Result: The following message appears in the Station message zone.
“Message must be acknowledged/confirmed before clear”

11.3.5 Recovery of TPS Messages that are not cleared yet


Action: Acknowledge and confirm few of the TPS messages appearing in the Message Summary. And then,
restart Experion Server.
Result: The acknowledged and confirmed TPS messages remains in the Message Summary. They must be
manually cleared using the Msg Clear option.

11.3.6 Message list overflow


A message list overflow on the ES-T's underlying Universal Station personality results in a system status event
notification being sent from the LCNP to the Windows resident Experion software. Since the Experion message
list is capable of accommodating 1000 notifications, it is likely that the Experion Message Summary display
will have the notifications that were lost from the TPS/LCN Message list due to overflow.
An operator may wish to take no corrective action (that is, not to resynchronize with the Message Summary
Display) because that action could result in the loss of messages, and the message summaries will eventually

262 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

resynchronize after the overflow condition is resolved. Message list overflow conditions on the Experion
message list are not reflected in any TPS/LCN Native Window displays.

263
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.4 Managing System Alarms


In prior releases, when there was a problem on the Native Window System Status display a TPN System Alarm
would be raised in the Experion system status display.
With Experion R410, the TPS System Status and the TPS Console Status indicators in the Experion Station
status bar replace the TPN system alarm.
For new installs, the TPN system alarm has been disabled by default. For migrated systems it is recommended
to disable the TPN system alarm. To disable the TPN system alarm, perform the following steps on each ES-T:
1 Open the Configuration Utility: Start > All Programs > Honeywell Experion PKS > System
Management > Configuration Utility
2 Select: Configure > Board 0 (or the name of your board)
3 Set “Experion TPS System Alarm” to <Disable>.
4 Click OK.

11.4.1 TPS System and Console Status Indicators


The TPS system and console status indicators on the Native Window are also shown in the Experion Station
status bar on ES-T nodes. Clicking the S calls up the Native Window System Status display. Clicking the C calls
up the Native Window Console Status display. The S and C indicators do not appear on Flex Stations and
Stations over DSA. To view the TPS System and Console Status indicators on Flex Stations and over DSA, call
up the faceplate of an ES-T in the Experion System Status display.
Refer to the Experion PKS General Release Software Change Notice (SCN) for the ES-T load module version
that is required for the 'S' and 'C' indicators to function.

264 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Native Window Experion Station Status Bar Console Station IKB/OEP


Faceplate
TPS system indicator active and Solid S with blinking Unacked Alarm SYST STATS LED
unacknowledged background color blinking
TPS system indicator active and Solid S with solid Acked Alarm SYST STATS LED
acknowledged background color steady
TPS system indicator return to normal Solid S OK SYST STATS LED
off
TPS console indicator active and Solid C with blinking Unacked Alarm CONS STATS LED
unacknowledged background color blinking
TPS console indicator active and Solid C with solid Acked Alarm CONS STATS LED
acknowledged background color steady
TPS console indicator return to normal Solid C OK CONS STATS LED
off
Experion is unable to determine TPS system Blank boxes where S and C Unknown SYST STATS LED
or console alarm state are normally shown off
CONS STATS LED
off

The TPS system indicator and TPS console indicator can be configured to sound the annunciator. Refer to
Section “4.11 Configure Audible Annunciation”.

265
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.4.2 TPN system Alarm Functionality


Attention
The following sections are applicable only to users who want to continue to use the TPN System Alarms.

When using an ES-T, you can see a TPN system alarm-related event presented as an Experion system alarm.
When the alarm occurs, a Windows event occurs which, in turn, is captured by the System Event Server (SES)
and converted into an Experion system alarm or update to the state of an existing alarm.

When the alarm occurs, a Windows event occurs which, in turn, is captured by the System Event Server (SES)
and converted into an Experion system alarm or update to the state of an existing alarm.
When a TPN system alarm occurs, it is annunciated to the operator via an LED associated with the SYST
STATS membrane-key on the IKB/OEP keyboard. The LED has four states: OFF, SLOW BLINK, FAST
BLINK, and STEADY ON. The states are used to represent whether the TPN has one or more system-related
problems and whether those alarms have each been acknowledged and/or have returned to normal. However, the
problem can be rectified from the LCN System Status display.

11.4.3 Alarm annunciation on node status change


A system alarm is generated whenever an HCI software component (running on Windows environment) fails in
an ES-T/ESVT/ACE-T node. This alarm is generated optionally for the failure of HCI components. The
composite HCI status is reflected in the auxiliary status of the node. When the auxiliary status changes to
SEVERE, an alarm is annunciated and recorded in the Experion Station System Alarm Summary. The
description of the alarm is displayed in the Experion Station Event Summary. With all the HCI components on
the node running, the auxiliary status shows OK.For more information, refer to the System Components
Configuration Utility User's Guide.

Attention
When the composite status of the HCI components changes to WARNING, the auxiliary node displays the status as
WARNING. If any of the HCI components is in the FAILED state, the auxiliary status of the node changes to
SEVERE.

11.4.4 System Status LED behavior of TPN versus Experion

Alarm and ACK state Experion Behavior TPN Behavior


System alarm active - unacknowledged LED blinking LED blinking

266 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Alarm and ACK state Experion Behavior TPN Behavior


System alarm active - acknowledged LED steady LED steady
System alarm return to normal - unacknowledged LED blinking LED off
System alarm return to normal - acknowledged LED off LED off

Note in the listing that TPN differs from Experion in that an unacknowledged system alarm, when returned to
normal, results in the LED going OFF. However, in an ES-T, given that Experion still holds the light to blinking,
the IKB/OEP LED will remain blinking until acknowledged in Experion.
Note also that system status alarm acknowledgement is not explicitly coordinated between Experion and the
TPN system. That is, acknowledging a solitary TPN system alarm on Experion will not likewise acknowledge
the alarm on the TPN. Therefore, given that the LED is shared between the two systems and the highest level of
LED “wins”, since the TPN considers the alarm unacknowledged, the LED will remain blinking.

Attention
While the TPN System Alarm tracks the IKB/OEP keyboard's SYST STATS LED, a physical IKB/OEP is not
required. However, at least one ES-T on a given LCN is required

Tip
SES is required for the TPS System Alarms to function.

11.4.5 No ACK Integration between TPN and Experion


There is no explicit acknowledgement integration between TPN and Experion with respect to the TPN SYST
STATS LED state and the associated TPN System Alarm on the Experion System Alarm Summary. When TPN
transitions the SYST STATS LED from blinking to steady, therefore, it has no effect on the Experion TPN
System Alarm status. Similarly, acknowledging the Experion TPN System Alarm will stop blinking for this
alarm's icon in Experion, but this has no effect on the TPN system. That is, each is managed separately. Note
that, per normal Experion behavior, when an acked alarm returns-to-normal, it is removed from the summary.

11.4.6 System Status LED behavior of TPN versus Experion

Alarm and ACK state Experion Behavior TPN Behavior


System alarm active - unacknowledged LED blinking LED blinking
System alarm active - acknowledged LED steady LED steady
System alarm return to normal - unacknowledged LED blinking LED off
System alarm return to normal - acknowledged LED off LED off

Note in the listing that TPN differs from Experion in that an unacknowledged system alarm, when returned to
normal, results in the LED going OFF. However, in an ES-T, given that Experion still holds the light to blinking,
the IKB/OEP LED will remain blinking until acknowledged in Experion.
Note also that system status alarm acknowledgement is not explicitly coordinated between Experion and the
TPN system. That is, acknowledging a solitary TPN system alarm on Experion will not likewise acknowledge
the alarm on the TPN. Therefore, given that the LED is shared between the two systems and the highest level of
LED “wins”, since the TPN considers the alarm unacknowledged, the LED will remain blinking.

Attention
While the TPN System Alarm tracks the IKB/OEP keyboard's SYST STATS LED, a physical IKB/OEP is not
required. However, at least one ES-T on a given LCN is required

267
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Tip
SES is required for the TPS System Alarms to function.

11.4.7 Combined Experion/TPN System Alarm LED Behavior


The following table describes the behavior of the SYST STATS led with respect to the combined system. Note
that additional Experion system alarms would follow existing LED behavior, i.e., additional Experion system
alarm(s) result in LED remaining blinking/steady per the highest alarm state. Also note that if either TPN or
(more likely) Experion specifies “Fast blink” vs. “Slow blink”, then “Blinking” means the highest (fastest) state.
Therefore, if Experion is configured to blink System Status LED as “fast” then, when both TPN and Experion
are unacknowledged, the LED will “fast-blink”. When Experion is ackowledged and TPN is unacknowledged,
the LED will “slow-blink”.

TPN System Alarm State TPN and Experion ACK State (for TPN System Alarm) LED State
Active TPN unacked, Experion unacked Blinking
Active TPN acked, Experion unacked Blinking (per Experion)
Active TPN unacked, Experion acked Blinking (per TPN)
Active TPN acked, Experion acked Steady
Return to Normal TPN unack, Experion unacked Blinking (per Experion)
Return to Normal TPN unack, Experion acked OFF
Return to Normal TPN acked, Experion unacked Blinking (per Experion)
Return to Normal TPN acked, Experion acked OFF

11.4.8 No ACK Integration between TPN and Experion


There is no explicit acknowledgement integration between TPN and Experion with respect to the TPN SYST
STATS LED state and the associated TPN System Alarm on the Experion System Alarm Summary. When TPN
transitions the SYST STATS LED from blinking to steady, therefore, it has no effect on the Experion TPN
System Alarm status. Similarly, acknowledging the Experion TPN System Alarm will stop blinking for this
alarm's icon in Experion, but this has no effect on the TPN system. That is, each is managed separately. Note
that, per normal Experion behavior, when an acked alarm returns-to-normal, it is removed from the summary.

268 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.5 TPN Console Acknowledgement


Experion retains the console-wide acknowledgement capabilities found in TPS/LCN and TPS systems. ES-T,
GUS, and US can be members of a TPN console. The ES-T members of a TPN console will also form an
Experion console. Experion Station-TPS Console Extension is a member of the same TPN and Experion
consoles as their host ES-T.

Attention
An Experion console cannot span more than one TPN console, nor can a TPN console include more than one Experion
console.

11.5.1 Experion Configuration


To configure a console for Experion, see the “Configuring a Console” section in the Server and Client
Configuration Guide.

11.5.2 LCN Configuration


A console may include zero or more US nodes, zero or more GUS nodes, and one or more ES-T nodes.
Consoles are configured using the NCF configuration functions as shown in the following figure.

269
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.6 Process History and Event Storage


The ESVT provides process data historization and archiving, and event data archiving. The Server obtains
TPS/LCN data and event notifications through its local TPN Server.

Attention
The inadvertent specification of array parameters for Experion history collection can cause significant performance
impacts to the system. As an example, HPM device-control-point parameter PVFL is not a single parameter, but is
actually an array of the following three parameters: PVFL(0), PVFL(1), and PVFL(2). You should type in the
parameters individually during Experion history configuration as shown in the following example: A100.PVFL(0),
A100.PVFL(1), and A100.PVFL(2).

11.6.1 Event database


The event database maintained by the Server is kept consistent with the event journal on the TPS/LCN History
Module node. Events known to the local TPS/LCN are represented in both locations, although event attributes
may differ between local TPS/LCN events and those from other sources. The Server event database can be
viewed using Experion displays.
Events are collected and then periodically copied from the Experion system database to the ESVT's SQL Server
event database for queries and reporting. Events are archived from the online event database according to a
schedule you specify. You can set up automatic archiving or you can set an alarm to alert an operator to archive
events.

11.6.2 Operator events


Operator events, including changes made through Native Window displays are stored in the event database on
the Server and can be viewed using Experion displays.
You use the Station application's Configuration Display to define settings for a particular Station. You can
assign a printer to Print Operator changes, which enables printing of all changes to points an operator has made
from the ES-T.

11.6.3 Viewing process history


Process history is available through various mechanisms, including standard Trend Displays, a custom display
with a trend object, Microsoft Excel Data Exchange, and relational databases using the Experion ODBC driver.
Process history continues to be collected on the TPS/LCN History Module for use by Native Window facilities.

270 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.7 Importing TPN History Configuration


The TPN History Configuration Import Tool lets you retrieve existing point history configuration data from the
TPN History Module and move that configuration to Experion and be used as an Experion history collection
configuration. Only the history configuration is imported (that is, what point.parameters are being collected).
The collected history data is not imported. You must be familiar with both the TPN History Module and its
history collection configuration and the Experion history collection functionality to use the tool.

11.7.1 Example of imported history display


The tool displays the discovered Units and History Groups in the left pane. The right pane displays the data
points to be exported to Experion and the Experion collection rate.

11.7.2 Changing history rates before export


When you save the collected history configuration into a comma-separated .csv file, you then have the option of
editing the file. You can change default collection rates of items and delete or add new items. To complete the
import, you open the .csv file by clicking the Read .CSV button in the tool and then export the file into
Experion history configuration.

11.7.3 History import requirements and recommendations


The import tool runs on an ESVT. If the ESVT is redundant, export into Experion succeeds only on the primary
server.

271
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

TPN Server must be running and connected to the underlying TPN. The alias name of the connection to the TPS
system in Experion must be set to “TPS”. On the TPN, the History Module containing the target history
configuration must be running in the on-line personality.
The user account must belong to the local Product Administrators group. Operation of the tool is not supported
for the user account that does not belong to this group.
A File Transfer installation on the ESVT is highly recommended. With File Transfer, the process of gathering
history configuration from the TPN is more efficient.

Tip
If TPS File Transfer is installed on the ESVT, the process of gathering history configuration from the TPN is more
efficient. The tool uses File Transfer to get data about configured history groups, their collection rates and
configured parameter slots within the groups (information about the slots used within the groups is available with
TPN Release 660 and later; on previous TPN releases, the tool will check all the slots in the group). Having the
configuration data read from the NCF enables the tool to ask for items directly, without exacting a time consuming
probe for all the possible configurations.

11.7.4 Import History configuration

To import history configuration from TPN


1 Click Start > Programs > Honeywell Experion PKS > TPS Applications > TPN History Import Tool to
open the TPN History Configuration Import display.

2 Click Get HM Groups.


For the next several minutes, the tool collects configuration data from the TPN. Discovered units and groups
appear in the TPN Units/History Groups pane.

272 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Attention
If TPS File Transfer is not installed, a prompt appears to confirm the Get HM Groups operation and the import
may take hours to complete.

3 Click OK to close the message box when data collection completes.


The data points and the collection rate appear in the right pane.

To interpret imported history configuration


1 You expand the unit names to view the history group number in the left TPN Units/History Groups pane as
shown in the following figure. This pane displays the configuration information for the Unit name and
History Group number and, if File transfer is installed, displays the group collection rate and Unit descriptor.

2 When you select the Unit in the left pane, the tool automatically selects all the groups under that unit.
3 When a group is selected, all of its associated point dot parameters appear in the right Data Points pane,
displaying its mapped collection rate as shown in the following figure.

4 The tool automatically maps TPN history collection rates to the Experion history rates as shown in the
following tables.
5 If TPS File Transfer is not installed on the node, all parameters are mapped to Experion's Standard history
collection rate.

273
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

TPN rate (in seconds) Experion collection type Experion collection rate (in seconds)
5 Standard 60
10 Standard 60
20 Standard 60
60 Standard 60

6 The following figure shows the imported history configuration when the File Transfer was not installed. The
default collection rate (60) is applied to all point.parameters.

7 If TPS File Transfer is installed on the node, all the parameters are mapped to Experion history collection
rates as shown in the following table.

TPN rate Experion collection type Experion collection rate


(in seconds) (in seconds)
5 Fast 5
10 Fast 10
20 Fast 20
60 Standard 60

8 The following figure shows the imported history configuration when the File Transfer was installed. The
collection rate for every group appears in brackets next to the group name.

274 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

9 You can check or un-check the desired groups until your list of points in the right pane is as desired. When
the export list is ready, you then select Export to send the configuration to the Experion history collection
configuration.

11.7.5 Using comma separated files (.csv) with history data


You can store and retrieve the history configuration data in .csv files. You can then edit the files with a text
editor or spreadsheet program to remove or change the configuration data.
Click the Save.CSV button to save the history configuration data in a .csv file.
Click the Read .CSV button to load the edited history configuration data in the TPN History Configuration tool.
The Read.CSV and Save.CSV buttons open the standard Window File Open/Save dialogs.
The tool does not assign a default directory to the .csv files. The line format in the .csv file is as follows:
<Point.parameter>,<TPNUnitname>,<ExperionCollectionType>,[ExperionCollectionRate]

Data Data type Data value


Point.parameter String Any
TPNUnitname String Any
ExperionCollectionType String FAST
STANDARD
EXTENDED
EXCEPTION

275
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Data Data type Data value


ExperionCollectionRate Integer
[Optional]

Attention
If any of the lines in the .csv file has a syntax error, those lines are not loaded in the TPN History Configuration
Import tool.

With Experion R400, the ExperionCollectionRate can be optionally added for every line/point in the .csv file.
Therefore, all .csv files created in the previous releases are accepted by the tool. If the collection rate is not
specified, the following settings are assumed.

Experion Collection Type in .csv file Default Collection Rate (seconds) assumed when not explicitly specified in .csv file
Fast 5
Standard 60
Extended 3600
Exception* 5

Note: *Exception is a new collection type introduced in Experion R400.

11.7.6 Example file results


The following table shows an example of history configuration data read from a .csv file read into the tool.

Data in .csv File Data Read into Tool

11.7.7 Export History configuration

Considerations
1 The export operation primes all the parameters in the Experion and theTPN Server internal data files. The
priming operations are time consuming. Therefore, it may take several minutes (or hours, depending on the
total number of parameters) to export the history configuration.

276 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

2 If you do not run the tool on a primary server, the export operation fails immediately with an error message.

To export history configuration to Experion


1 In the TPN History Configuration Import display, click Export.
All items from the Data Points pane are written to the Experion history database. A progress bar indicates
the progress of the export process.
After successfully exporting the history configuration, the pntbld files are created and the following message
appears.

2 Click Browse Export Files in the TPN History Configuration Import tool. The path, where the input and
output files are created appears.

Files created in export operation


1 The export process creates two sets of files: tpnhistimportiN.pnt (i for “in”) and tpnhistimportoN.pnt (o for
“out”), ten ( N = 0 .. 9) files each. Because these are text files, you can view them with a text editor. Each
time you click the Export button, the files are reused and their previous content is lost. If the content of
these files are of interest to you, then you should copy them to an archive location. The input and output files
are created in \ProgramData\Honeywell\TPNServer\HistImport. Note that the local Windows Group,
“Product Administrators,” needs “Modify” permissions on this folder.

Attention
With the Custom Install Path (CIP) supported in Experion R410, the user has the option to change the existing
default path of installation (C:\ProgramData\Honeywell) to any possible path.

2 When you click the Export button, the tool builds the tpnhistimportiN.pnt as an input to the Experion
history configuration as shown in the following figure.

3 The tool then calls a method in Experion to do the actual history configuration. The results of that operation
are reported in the tpnhistimportoN.pnt file as shown in the following figure.

277
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

278 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.8 ES-T Keyboard Behavior

Attention
When using the ES-T keyboard for Native Window functions such as entering Picture Editor commands, use the Ctrl
key with the Enter key to perform Return-key functions because the keyboard does not have a Return key.

11.8.1 IKB and OEP hot keys


The table below describes the functionality of the available hot keys on the Integrated Keyboard (IKB) or
Operator Entry Panel (OEP). Hot keys are fixed-function keys that are focus-independent, meaning they are
independent of the application that is in focus (active/in foreground) at the time the key is pressed.

Key ES-T Behavior


User Configured Through configuration, you have three options for the set of the user-configured keys of an IKB/OEP
Keys as described below.
1. Keys are controlled by Experion:
Use Experion configuration functions to configure LEDs and key actions.
Key configuration is on a per-station basis.
Key configuration is not affected by TPS/LCN Area change.
2. Keys are controlled by the TPS/LCN:
Use the existing TPS/LCN Button Configuration files to configure LEDs and key actions.
Key configuration is on a per TPS/LCN Area basis.
Each key is controlled by either Experion or the TPS/LCN.
3. You determine the key behavior on a key-by-key basis:
Keys controlled by the TPS/LCN behave according to the TPS/LCN Button Configuration (.KS
and .KO) files for the selected TPS/LCN Area.
Keys controlled by Experion behave according to the Experion Station Toolbar definition (.stb)
files.
Key configuration remains constant over TPS/LCN Area changes.
ALM SUMM Invokes the Experion Alarm Summary display.
ALM ANNC Invokes the TPS/LCN Alarm Annunciator display in the Native Window.
CONS STATS Invokes the Experion Console Status display, the TPS/LCN Console Status display, or both
displays as described below:
If the LED state is… Then, CONS STATS key invokes…
OFF due to no alarm from either subsystem Both displays
ON due to alarm from TPS/LCN The TPS/LCN Console Status display in the Native
Window
ON due to alarm from Experion The Experion Console Status display
ON due to alarm from TPS/LCN and Both displays
Experion
UNIT ALM Invokes the Experion Alarm Summary display.
SUMM

279
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Key ES-T Behavior


GROUP Selects the Message Zone in the Station application, allowing a user to specify the Group display to
be invoked. Groups are identified with integer identifiers.
Either a TPS/LCN Group display in the Native Window or an Experion Group display is invoked,
depending on the specified Group number. Experion Group displays are assigned a range of integer
IDs separate from the integer IDs for TPS/LCN Group displays. The range is configurable.
PRIOR DISP Calls back the previously displayed page.
MSG SUMM Invokes the Experion Message Summary.
SCHEM Selects the Message Zone in the Station application, allowing a user to select a particular user-
authored display.
If an HMWeb display with the requested name exists, it is invoked. If no HMIWeb display with the
requested name exists, then the TPS/LCN schematic with the requested name is invoked.
SIL Silence handling is based on NCF and Experion System-Wide Settings, tab Alarm/Event Options.
The NCF recommended value is: “Console-wide silence Button? NO”
The Experion System-Wide Settings recommended value is: “Silence action applies to: Single
Station or single console (all stations in console)”.
Silencing alarms on other stations in the Experion cluster is based on the Experion System-Wide
Settings only. The recommended value is “Silence action applies to: Single Station or single console
(all stations in console)”.
SYST MENU Invokes the Experion System Menu.
SYST STATS Invokes the Experion System Alarm Summary, the TPS/LCN System Status display, or both
displays as described below:
If the LED state is… Then, SYST STATS key invokes…
OFF due to no alarm from either subsystem Both displays
ON due to alarm from TPS/LCN The TPS/LCN System Status display in the Native
Window
ON due to alarm from Experion The Experion System Alarm Summary
ON due to alarm from TPS/LCN and Both displays
Experion
UNIT ALM Invokes the Experion Alarm Summary display.
SUMM
UNIT TREND Invokes the TPS/LCN Unit Trend display in the Native Window.

11.8.2 LED annunciation


The following table describes the LED annunciation through the IKB/OEP in terms of the subsystem that drives
the annunciation.

Key Annunciated by…


User Configured Keys Either Experion or TPS/LCN, depending on user configuration
ALM SUMM Experion
Alpha Shift IKB/OEP hardware
CONS STATS Either Experion or TPS/LCN, as the annunciation is shared
FAST Experion. This LED reflects the status of the Experion system update rate regardless of whether
Experion or Native Window has focus. For Native Window status, refer to the “F” button on the
Native Window display. On (red) indicates Fast.
Note: For more information about FAST key, refer to the SafeView Users Guide.

280 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Key Annunciated by…


MSG SUMM Experion
RECRD Experion
SYST STATS Either Experion or TPS/LCN, as the annunciation is shared

11.8.3 Focus-dependent (context specific) keys


Attention
When using the ES-T keyboard for Native Window functions such as entering Picture Editor commands, use the
<CTRL> key with the <ENTER> key to perform Return-key functions because the keyboard does not have a
<RETURN> key.

The action of focus-dependent keys is context-sensitive (unlike the IKB and OEP “hot keys”), meaning that the
action of the key depends on the application window in focus (active/in the foreground) at the time the key is
pressed.
For descriptions of the key actions performed when the Native Window has focus, refer to the Keyboards
manual.
For descriptions of the key actions performed when Experion has focus, refer to the Operator's Guide.

11.8.4 IKB Keyswitch


EPKS has been updated to store the following two new values:
• The software determined Security Level
• The IKB KeySwitch determined security level
These values are kept separate from the existing security level. They are stored in CRTCNT - a word in
CRTTBL that includes details of control level, security level and other security related data. This location is
used for storing the combined value as defined in the following table.

IKB Key Switch Value


No VIEW ONLY1 OPER2 SUPV ENGR
IKB
EPK VIEW ONLY3 VIEW ONLY VIEW ONLY VIEW ONLY4 SUPV ENGR
S
ACK ONLY3 ACK ONLY ACK ONLY ACK ONLY4 SUPV ENGR
Calc
ulate OPER OPER OPER OPER SUPV ENGR
d
SUPV SUPV SUPV SUPV SUPV ENGR
Value
ENGR ENGR ENGR ENGR ENGR ENGR
MNGR MNGR MNGR MNGR MNGR MNGR

Table notes:
1. IKB KeySwitch can be configured in SOM such that when in “Oper” position, this actually means “View
Only.” This column represents the resulting value when the IKB is in this mode.
2. When IKB Key Switch is in OPER position, it is considered to be not in use, so EPKS calculated value is
used.
3. Only applicable when using Operator-Based security.
4. Only two cases where the lower of the two security levels is used. The EPKS value is used even though IKB
has a higher value. This is a result of Note 2, and allows for Note 3 operation when Operators are
configured with these security levels and an IKB is in use.

281
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

Attention
When using an IKB on a Console Station or Console Station Extension and the Server is unavailable, this functionality
will continue to work. All data required for this functionality is available on the Console Station, so it will not be
impacted by the Server being offline.

282 www.honeywell.com
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.9 Implementing Remote Native Window


Remote Native Window runs on Experion Station nodes. ES-T is qualified as servers. With Remote Native
Window, you can operate remote TPS systems that are interconnected by DSA. It also aids in the
implementation of centralized control rooms. Its major benefit is to provide the capability to invoke key TPN
engineering functions remotely, since most of these functions are available only in the Native Window.

11.9.1 Operations
Remote Native Window is not integrated into Experion, as is the “local” Native Window on an ES-T. Some
specific constraints are as follows:
If an IKB is present on a station using Remote Native Window, then the IKB will only work if the Remote
Native Window has focus (that is, the Remote Native Window application is user-selected).
Cross-environment display invocations are not supported for Remote Native Window, as they are for the ESVT.
Specifically, Experion and GUS displays cannot invoke Remote Native Window displays, and vice versa.
For an ES-T or an ES-T Console Extension node with TPS Extension, the user must be aware that the Remote
Native Window will likely show a different TPN Area/Console than that of his/her station.

283
11 MANAGING OPERATIONS, ALARMS, AND EVENTS

11.10 Remote TPN Operations using Flex and DSA-connected Stations

Attention
Flex and DSA-connected Stations are not recommended for operation and control of TPN connected equipment. For
operation and control of TPN-connected equipment, use one of the following options:
• ES-T with a direct connection to the TPN
• Console Extension Station connected to an ES-T with a direct connection to the TPN
Flex Stations and DSA-connected Stations can be used only for view-only casual access of TPN-connected equipment.

11.10.1 Flex Station and remote operation functionality using DSA


When you optionally use DSA, the remote TPN operations using ES-F and remote operator stations connected
via DSA are supported. Remote Native Window can be invoked on these stations to provide Native Window
only functionality as described in the previous section.
Flex Stations and DSA-connected Stations are interfaced to the TPN through the ESVT, whereas, the ES-T has
a direct TPN connection. For TPN-connected Experion systems, Flex and DSA-connected Stations have
limitations in the following areas:
• Limited capacity of the ESVT to serve TPN data to the connected Stations. All Flex Stations, DSA-
connected stations and other ESVT functions such as APIs and history collection access data from the TPN
via the onboard LCNP interface card. The maximum amount of data that an ESVT can provide is
approximately 1600 parameters per second.
• These stations cannot participate in a TPN Console. Therefore, acknowledgements from these stations are
not visible to any members of any TPN Console. However, they are visible to other ES-Fs.
• Although the Remote Native Window can be invoked on these stations, it is not integrated as is the Native
Window on an ES-T because an LCNP board is not present on remote client stations.
• If you are using DSA for remote operations with an ES-T and Console Station Extension, then you must use
HMIWeb displays. Native Window and GUS displays on these stations function with the local TPN only,
with the exception that these stations can invoke a Remote Native Window as described earlier.
• Operator messages cannot be confirmed to the data owner from these stations.
• There are minor changes in alarm behavior resulting from the fact that acknowledgements are handled solely
by Experion software on the Server. For example, any alarm status change (for example, from a box idle)
following Return to Normal is not reflected in unacknowledged alarms.

284 www.honeywell.com
12 Administering Experion-TPS Nodes

285
12 ADMINISTERING EXPERION-TPS NODES

12.1 Managing Experion-TPS Security


Experion-TPS nodes have several security mechanisms and tools available for managing the secure operations
of your system. They include the following:
High Security Policy model leverages the Microsoft Windows Group Policy security model to enable you to
control how programs, network resources, and the operating system behave for users and computers in your
organization. Implementing the High Security Policy in a domain environment allows you to implement
security settings at the group level. The security settings then apply to every user in the group regardless of the
computer they are logged on to.

Attention
In a domain, you must run the Link Domain Groups command after installation.

Signon Manager is an application that provides a point of single sign on, allowing users to log on to multiple
participating applications, such as Station and Native Window, by providing their credentials to Signon
Manager.
ES-T uses Experion Operator-based security and integrated accounts. Windows accounts are used to
authenticate a user, and an operator definition in Experion is used to authorize the user. In general, operator-
based security with traditional operator accounts works as follows:
• You assign a specific security level to each user.
• Users cannot access any Station functions unless they enter a valid ID and password.
• To access a higher security level than the one they are currently using, users need to sign on to Signon
Manager as a different operator who has the higher security level.
• Assets are assigned to the operator, regardless of which Station they are currently signed on to.
Server password utility
Pre-configured console with Microsoft's Security Editor

12.1.1 High Security Policy model


The High Security Policy model provides a user environment for each operational user type such as
Supervisors, Engineers, and Product Administrators. Each user type is granted the privileges and system access
needed to perform their required functions while at the same time protecting system resources. The security
model is installable for domain controllers and workstations. The following figure shows the local groups
created for a workstation.

286 www.honeywell.com
12 ADMINISTERING EXPERION-TPS NODES

For more information about the High Security Model, refer to the “Using High Security Policy” section in the
Server and Client Configuration Guide.

12.1.2 Signon Manager


Signon Manager is the tool for operator authentication on ES-C or Server nodes. It allows client applications to
base security operations on the current system user without requiring a full Windows log-off and log-on, which
would result in a brief loss-of-view at that workstation. When a node is “Signon-aware,” a small window
appears to identify the currently signed-on user; a task bar icon also appears as shown in the following figure.

Clicking the task bar icon invokes a Signon Manager dialog to allow you to change the currently signed on user
or to temporarily override a currently signed on user.

287
12 ADMINISTERING EXPERION-TPS NODES

Attention
Signon will be refused if:
• The user is not a valid windows account,
• The user is not a configured Experion operator,
• An Experion Station signon restriction is in effect for this user (for example, a time or station restriction), or
• The Station application shows a different user (instead of MNGR). The “Use windows account” must be checked
in the Area Assignment.

For more information about Signon Manager, refer to the following documents.Server and Client Configuration
Guide.

12.1.3 Station/Operator
Operator security settings can be edited from Configuration Studio as described in “Procedure to add and
configure Operators”.

12.1.4 About Station time-outs


Depending on the configuration settings at your site, the Station you are using may time out if you have not
used either the keyboard or mouse for a predetermined period.
The behavior of the Station when it times out depends on the configuration of that station or your operator
profile. So, for example:
• If you log on to a Station using a traditional operator's account (such as oper or supv), the Station reverts to
the lowest security level (read-only) and may or may not change to a different display.
• If you logged on to a Station using your own individual operator account, the Station display changes to a
new display or displays the Log in dialog box.

12.1.5 Station time-outs and Signon Manager


If you use the Signon Manager to log on to Station and a time-out period has been configured for your system,
the timer box on the Signon Manager bar flashes red (and shows the time-out value) as the time-out approaches.
By default the time-out warning appears 30 seconds before the time-out comes into effect.
Depending on the configuration settings of your site, you may also find that the Signon bar is made visible if it
is currently hidden. In addition your system may have been configured to provide an audible time-out warning.

288 www.honeywell.com
12 ADMINISTERING EXPERION-TPS NODES

If you have signed in using the Signon Manager override and a time-out period has been configured for
“override users,” you may be able to change the pre-configured time-out period when you sign in. You can do it
as long as your system has been configured to allow this and you do not specify a higher time-out period than
the maximum that has been configured for override users at your site.

Tip
If you need to extend the time-out period further while you are signed in as an override user, you can sign in as the
same override user again to restart the time-out interval. While you sign in as the same override user, you can
specify an extended time-out period if that feature is configured at your site.

12.1.6 Signon Manager Settings in Configuration Utility

Signon Manager Tab


Keep Signon display on- When this option is on, a small window remains on-screen at all times, indicating the user
screen at all times currently signed on, unless covered by a higher priority window. This window provides the
simplest way to sign off and to access the dialog allowing signing on. When this option is
(Default = on)
off, the window is hidden.
Signon Display Colors This option allows the user to make the current user window either more or less obvious,
depending on site preference. To change the colors of the window, do the following steps:
(Default = blue text on light
blue background) 1. Click Text and/or Background. Each button displays the standard Windows color
selection dialog box.
2. Select the color and then click OK. The preview window above the buttons shows the
selected color combination.

12.1.7 Invoking the Signon Manager


Signon Manager starts whenever a user logs on to Windows.
To open the Signon dialog box, click the Signon Manager's current user window, or click the Signon Manager
icon in the taskbar.
If the Signon Manager icon is not present in the taskbar, make the following selections to start the Signon
Manager utility: Start > Programs > Honeywell Experion PKS > System Management > Signon
The drop-down list for the user names in the Signon Manager User window is the last five names accepted
within a Windows logon session, so it always starts empty and is populated as Signon Manager sign-ons
succeed.
For more information about the Signon Manager User interface, see “Managing Experion-TPS Security” on
page 286.

289
12 ADMINISTERING EXPERION-TPS NODES

12.2 Password Security and Synchronization

12.2.1 Secure passwords


Attention
To avoid having passwords compromised, Honeywell highly recommends that you change the factory default
passwords to be strong passwords (such as passwords that include one or more spaces as characters).

12.2.2 Windows Services & DCOM Servers Log-on tool


A Honeywell tool (svrpass.exe) can be used to display Windows services and DCOM servers that are registered
to run under a selected account. After entering secure passwords for specific Honeywell accounts, use this tool
to synchronize the Windows and DCOM services associated with those accounts.

When to use the Windows Services & DCOM Servers Log on tool
Attention
This password tool must be run on every node that will use the changed account.

Use the Honeywell Windows Services & DCOM Servers Log on tool after changing passwords for any of the
accounts that are used for running the Services and DCOM servers, such as LocalCOMServer, Mngr, and other.

290 www.honeywell.com
12 ADMINISTERING EXPERION-TPS NODES

Procedure for using the Windows Services & DCOM Servers Log on tool
After entering secure passwords for the specific accounts named previously, do the following steps to
synchronize the Windows and DCOM services associated with those accounts.
1. Click Start > Programs > Honeywell Experion PKS > System Management > Windows Services &
DCOM Servers Log on tool.
2. Select an Account Name from the dropdown list.
Under Associated Servers, the tool lists the Windows services and DCOM servers associated with the
selected account name.
3. Type the password for the account and then click Apply New Account.
If the password you just typed matches the account's password, the tool synchronizes the associated
Windows services and DCOM servers with the new account information. Then, a message appears
indicating that the operation succeeded.
4. Repeat steps 2 and 3 as necessary for each changed account.
5. Run the password tool and repeat this procedure on every node that is using the changed account(s).

Attention
This password tool does not change the password on the account.

291
12 ADMINISTERING EXPERION-TPS NODES

12.3 Supporting System and Network Availability


When using Experion-TPS nodes, the following options are available for enhancing network availability:
• Redundant Servers
• Fault Tolerant Ethernet (FTE)
• Redirection Manager (RDM)
• System Event Server (SES)
• System Performance Server (SPS)

12.3.1 About Redundant Servers


You can improve system availability with server redundancy. The Server supports redundant server
configurations providing a warm fail over architecture with online database replication.
For more information about redundant servers, see:
• Server Redundancy section in the Server and Client Planning Guide
• Configuring and Monitoring a Redundant Server System section in the Server and Client Configuration
Guide

12.3.2 About Fault Tolerant Ethernet


Honeywell Fault Tolerant Ethernet (FTE) represents a way to achieve Ethernet redundancy through the use of
Honeywell's FTE driver and redundant commercially available equipment. Fault Tolerant Ethernet enabled
components allow network communication to occur over a functioning route. If that route should fail and
another route exists, then communication occurs over that route.
For more information about Honeywell Fault Tolerant Ethernet, refer to the following documents.
• FTE Status Display and User Guide
• FTE Installation and Service Guide

12.3.3 About Redirection Manager


Redirection Manager (RDM) provides high availability and reliability of OPC client connections to OPC
Servers. The Redirection Manager enables OPC clients to transparently redirect requests to an alternate OPC
server.

Attention
Redirection Manager should not be configured to use the private TPN servers that reside on the Experion-TPS nodes.

For more information about Redirection Manager, refer to the Redirection Manager User's Guide.

12.3.4 About System Event Server


System Event Server (SES) integrates Windows system events into the Alarm and Event subsystem. Event
examples include HCI Server status changes, Experion or TPS node failures, and Experion or TPS configuration
changes.
For more information about System Event Server, refer to the System Management Configuration Guide.

292 www.honeywell.com
12 ADMINISTERING EXPERION-TPS NODES

12.3.5 About System Performance Server


The System Performance Server (SPS) provides an interface to performance and configuration information. The
availability of this data allows it to be integrated into operator displays and process applications.
For more information about System Performance Server, refer to the System Management Configuration Guide.

293
12 ADMINISTERING EXPERION-TPS NODES

12.4 Distributed System Architecture


Distributed System Architecture (DSA) allows you to integrate up to thirty servers into a single system. DSA is
appropriate for:
Large-scale, plant-wide systems
Geographically-dispersed systems
For more information about Distributed System Architecture, see:
• “Distributed System Architecture” section in the Server and Client Planning Guide
• “Configuring Distributed System Architecture” section in the Server and Client Configuration Guide

294 www.honeywell.com
12 ADMINISTERING EXPERION-TPS NODES

12.5 Configuring an ES-T Station for Native-Window-Only Operation


It is possible that it may be necessary to use an Experion-ready ES-T for Native-Window-only operations when
an ESVT is not available. An ES-T station normally has Experion software and TPS add-on software. In this
case, you can disable the Experion components, leaving only the Native Window operations capability.
With this arrangement, you should assign the IKB/OEP to the TPN so that TPN alarms can be annunciated at
the IKB/OEP.
When using the Native-Window-only capability of an ES-T, GUS displays are NOT supported at the station.
GUS displays cannot be viewed because the Experion GUS Displays runtime requires Experion components.
The Experion components can be re-enabled at a later time when an ESVT node is available so that the ES-T
node can operate in the full Experion environment.

12.5.1 Configuring for Native-Window-Only Operation

Task Done? Notes


Verify that system System prerequisites are as follows:
prerequisites are met.
• ES-T has been defined as a US node on the TPN.
• GUS Personality package has been installed in the ES-T.
• ES-T node has been added to the network domain.
Experion PKS High Security policies have been implemented.
Deactivate Experion PKS Do the following steps:
services on the ES-T node
1. Click Start > Settings > Control Panel > Administrative Tools > Services.
by setting Experion PKS
startup services for a 2. Right-click the service name and then click Properties.
manual startup. 3. Click Manual in the Startup type to set all of the following Experion PKS
services (if present/applicable) for a manual startup:
• Experion PKS Add Route (FTE)
• Experion PKS Configuration Studio Information Service
• Experion PKS Console Station Daemon
• Experion PKS Console Station Database
• Experion PKS Console Station Desktop
• Experion PKS Console Station Operator Management
• Experion PKS Console Station Replication
• Experion PKS Console Station System
• Experion PKS Control Data Access Server
• Experion PKS eNAP Server
• Experion PKS GCL server name
• Experion PKS Server Logger
• Experion PKS System Repository
• Experion PKS TPS Restart Service
Note: Note that the list of Experion PKS services mentioned here are only
applicable for R4XX releases.

295
12 ADMINISTERING EXPERION-TPS NODES

Task Done? Notes


Deactivate the HCI server Do the following steps:
components on the ES-T
1. Click Honeywell Experion PKS > System Management > Configuration
node.
Utility > HCI components.
2. Select Auto Start to “No” for the following local HCI components::
• Experion PKS Console (HciHsc.SysStatus)
• TPN Server (Hci.TPNServer)
Configure startup of Do the following steps:
applications during operator
1. Start Native Window in the logon script (C:\Program Files\Honeywell\TPS
log-on without the Experion
\Emulators\lcnwindow.exe).
station.
2. Ensure that the Experion Station.exe is not in the logon script.
Note: This step is only applicable if you are using the Logon script.
• With Experion R410, 64-bit OS is supported. All 32-bit components are
installed in C:\Program Files (x86). The default path for installation of TPS
components (T-Nodes) is C:\Program Files (x86)\Honeywell\TPS.
• The Custom Install Path (CIP) is supported in Experion R410. You can choose
any possible path for installation (e.g. D:\TEST\Honeywell\TPS).
Configure the LCNP4 To configure the LCNP4 board, use Honeywell Experion PKS > System
board. Management > Configuration Utility > Configure > Board0.
If IKB or OEP is present, Do the following steps:
enable annunciation by
1. Click Honeywell Experion PKS > System Management > Configuration
TPN in absence of Experion
Utility > Configure > Board0 > Native Window tab.
services.
2. In the IKB/OEP Annunciation field, select TPN - in absence of Experion.
Reboot the ES-T node.

12.5.2 Returning a Native-Window-Only Station to the Experion Environment


Tip
Honeywell recommends re-installing the ES-T node using the Experion installation media.

296 www.honeywell.com
13 Integrating TPS using only Server

297
13 INTEGRATING TPS USING ONLY SERVER

13.1 Managing an integrated system


This section provides an overview of how Experion manages an integrated TPS system.

13.1.1 Managing TPS points in an integrated system


In general, Experion manages TPS points in the same way as native Experion points. Experion supports flexible
points; a value of a flexible point parameter is read directly from the field when required. For example, you can
include TPS point data in displays and reports, and can access it through Experion's interfaces such as ODBC
and Microsoft Excel Data Exchange. Experion classifies TPS points as flexiblepoints; that is, the database
structure of TPS points is determined by TPS rather than by Experion. (For more information, see the “About
flexible points” section in the Server and Client Configuration Guide.)

Caching discovers TPS points


Experion uses a caching technique to “discover” TPS points when needed, without maintaining a mirrored
database. For example, Experion requests the TPS system for point data when an operator calls up a display that
references those point(s). “Point caching” means that you do not have to purchase a license for a larger database
size because the TPS points still reside in the TPS system. Point caching also greatly simplifies integration tasks
because you do not have to separately reconfigure TPS points in Experion.

Notes
Because TPS points are cached, they do not count against the Experion license for points. However, the total
number of points (licensed plus cached TPS) cannot exceed 250000. The individual limit on PSA (Point Server
Flexible) points is 300.
TPS points can be viewed in Experion R300 point detail displays, but not in releases prior to R300 where
Native Window point detail displays are used for TPS points.

298 www.honeywell.com
13 INTEGRATING TPS USING ONLY SERVER

13.2 Managing TPS alarms and events


In general, Experion manages TPS alarms and events in the same way as native Experion alarms and events. For
example, they are automatically included in the Alarm Summary, Event Summary and Message Summary
displays. Because of differences in classification and terminology, Experion automatically maps conditions/
events and alarm priorities to their Experion equivalents, as specified in the following tables.

Notes
Experion uses a TPN server to access TPS alarms and events. The TPN server converts TPS events from TPN
format to Experion format.
An ESVT auto-acknowledges conditions with journal-level alarms.
An ESVT server continues to receive alarms from TPS points even if they are TPS disabled. Such alarms are
automatically sent to the event log, even though their priority might be higher.
In TPS, the term “Disabled” means disabled alarms are sent only to the journal, whereas in Experion, the term
“Journal Only” is used to indicate the same.
In TPS, the term “Inhibit” is used to indicate there is no alarm/event generated, whereas in Experion, the term
“Disabled” is used to indicate the same.

Table 3: Mapping of TPS conditions and events

TPS Condition/Event Experion Experion Event Category


Event Type
ABORT, ADVDEV, BADINPUT, BADOC, BADPV, BADCTL, BADSV, Condition- Process alarm
CHNGOFST, CLEALM, CLFAIL, CLFALM, CLWARN, CMDDIS, related
CMDFAIL, CNFERR, COMPSHED, COUNTER, DEVHH, DEVHHH,
DEVHI, DEVLL, DEVLLL, DEVLO, FFDCFAILFFDISC, FLAG,
HOLD, INVALID, OFFNORM, OFFSET1, OFFSET2, OFFSET3,
OPENTHER, OPHI, OPLO, OVRDI0, OVRDI1, OVRDI2, OVRRUN,
PPPRESET, PRESET, PRPRESET, PVHH, PVHHH, PVHI, PVLL,
PVLLL, PVLO, PVROC, PVROCN, PVROCP, PVSGCH, S4LOGIC,
STEPAL, SVHH, SVHI, SWTALM1, SWTALM2, SWTALM3,
TIMEOUT, UNCEVT, UNREASBL
CHNGOFST, OFFNORM Sequence of events
SYSERROR, NODEERROR, NETERROR, NETREDERROR, System alarm
MANCOMPERROR, SYSCOMPERROR
DEVCOMMERROR OPC server error
OPERATOR MESSAGE Message
CONFIRMABLEMESSAGE Confirmable message
DEVICEFAILURE Simple Device failure
BATCH STATUS Batch status
SYSTEM MESSAGE System message
PROCESS CHANGE Tracking Operator process change
ACKNOWLEDGEMENT Acknowledgement
SYSTEM CONFIGURATION System configuration
ADVANCED CONTROL Advanced control

299
13 INTEGRATING TPS USING ONLY SERVER

Table 4: Mapping of TPS alarm priorities

Experion Alarm Priority


EMERGNCY Urgent
HIGH High
JNLPRINT Journal
JOURNAL Journal
LOW Low
NOACTION Not applicable
PRINTER Journal (Only applicable to an Experion-TPS Console Station)

13.2.1 Mapping TPS units


When you integrate your TPS system, you map TPS units to Experion assets, so that you can manage TPS data
and alarms/events in an appropriate manner. For example, you can configure a particular Station to only receive
notifications from specified TPS units.
With Experion R400, all the TPS alarms recovered with no timestamp are automatically acknowledged. The
recovered TPS alarms have a consistent acknowledgement state between the ES-Ts and the ESV-Ts.
Any occurrence of the non-timestamped TPS alarms or events are journalized in the alarm summary. The non-
timestamped TPS alarms are displayed with the text “Unknown” in the Date & Time column on the Experion
Alarm Summary.
Avoid the following scenarios to prevent getting alarms with unknown time stamps.
Changing the TPN area to a peerless area in the TPN console causes an alarm recovery for the TPN units. This
results in alarms with unknown timestamps. To avoid this scenario, have at least two ESTs in the same TPN
area/console.
Changing the Console Disable to Console Enable causes a unit alarm recovery for the Console Enabled unit.
This results in alarms with unknown timestamps.
Events may be lost when the Universal Station is unable to handle a large number of events over a relatively
short period. There is a target, Recover Lost Events target, on the Native Window alarm summary when lost
events occur. Selecting this target causes either an alarm recovery on every unit in the area or just the units
where alarms were lost, resulting in alarms with unknown timestamps.

Attention
Shelving alarms with “Unknown” timestamp is not supported.

Attention
While configuring the EHPM block (with EHPM Data Access parameter value set as “Peer to Peer and ExpServer”) in
Control Builder, ensure that all TPN units in which EHPM points reside, must have assets defined in the Experion
EMDB, and units mapped to Experion assets. If you fail to do so, these EHPM points cannot be historized through
CDA.
For more information, refer to the Control Building User’s Guide.

13.2.2 Change of alarm priorities


If a point is in alarm, the data owners will re-alarm the points when transition from EMER-> HIGH-> LOW.
• Experion will show new alarms in these transitions.
Transition from E/H/L to J/JP/P/N will result in INA/DIS alarm.

300 www.honeywell.com
13 INTEGRATING TPS USING ONLY SERVER

Tip
This behavior is different than the Native Window when an UNACK alarm is in play.
• Native Window AS removes the alarms even when UNACK.
• Experion does not remove CDA alarms, but does change them to DIS.

301
13 INTEGRATING TPS USING ONLY SERVER

302 www.honeywell.com
14 Managing TPS points

303
14 MANAGING TPS POINTS

14.1 Integrating TPS points into Experion


This section describes the following procedures for integrating TPS points into Experion:
• Configuring history collection for TPS points
• Configuring history offsets
• Adding TPS points to a trend
• Adding TPS points to a group
• Including TPS point data in custom displays
• Writing scripts for TPS points
• Attaching algorithms to TPS points
• Deleting, Moving or Cutting over TPS points to CDA
• Peer to Peer Communication between CEE and TPS Points

Prerequisites for integration


You are logged on to Station with ENGR or MNGR security level to perform this task.
You have installed the ESVT.
You have followed the procedures for configuring DSA as described in “Configuring Distributed System
Architecture” in the chapter “Servers” in the Server and Client Configuration Guide.
You have configured the TPS connection as described in “Configure TPS System Interface.”
(Optional) You have assigned TPS points to your Experion asset model set up. For guidelines on designing your
asset model, see the chapter “Enterprise models” in the Server and Client Planning Guide and for guidance on
setting up your asset model, see the Enterprise Model Builder User Guide.

304 www.honeywell.com
14 MANAGING TPS POINTS

14.2 Configuring history collection for TPS points


When configuring history collection for TPS point data you can assign a TPS point to standard, extended, fast,
and exception history collection. For detailed information about Experion's history collection capabilities, see
the chapter “History collection and archiving” in the Server and Client Configuration Guide. To set up history
collection for a TPS point in Experion, you can either:
Import data from the TPN History Module using the TPS History Configuration Import tool. For details of how
you use this tool, see “Importing TPN History Configuration”.
Configure TPS points to collect history in the same way as you do for native Experion points.

Attention
If you have assigned TPS point parameters to collect history in Experion, disable history collection of these point
parameters in the TPS history module to avoid repeated collection of history in TPS.

Attention
Starting with Experion R430, the EHPM points that are imported into ERDB can be optionally downloaded to the
Experion server so that standard history is collected through CDA.
For information on configuration of standard history support for the EHPM points, refer to the Control Building User’s
Guide.

Attention
If you make changes to the Self-Defining Enumeration (SDENUM) parameter for an EHPM point in the TPN server,
stop and restart the Experion OPC Server to reflect these changes in PHD.

For individual points you can use Station. For a large number of points, it is recommended that you use pntbld.
Both procedures are described below.

To configure individual TPS points for history collection using Station


1. On the System Configuration menu display click History Collection. This calls up the History Collection
display.
2. Click the appropriate tab for the type of history that you want to collect (for example, the Fast History tab
as shown below).

305
14 MANAGING TPS POINTS

3.

4. Click in the next empty Point ID box and type the point ID, such as FIC101.
5. Use the Parameter list to choose the parameter whose history you need to collect, such as PV.
6. (Optional) Use the History Gate Point fields if you want to control when history is collected (for example,
you may only want to collect history at certain times of the day).

To configure a large number of TPS points for history collection using pntbld
1. For every TPS point parameter that you wish to collect history for, create a new line in a text file using the
following formats:
For fast history: HISTFAST Point_ID parameter [gate_Point gate_param gate_state ] [/del] [/period=n] [/
PHDCOLLECT=Value]
For standard history: HISTSLOW Point_ID parameter [gate_Point gate_param gate_state] [/del] [/
group=n] [/period=n] [/PHDCOLLECT=Value]
For extended history: HISTEXTD Point_ID parameter [gate_Point gate_param gate_state] [/del] [/
PHDCOLLECT=Value]
For exception history: HISTEXCP Point_ID parameter [gate_Point gate_param gate_state] [/del] [/
group=n] [/period=n] [/PHDCOLLECT=Value]
Examples:
HISTFAST FIC101 PV /Period=5
HISTSLOW FIC101 PV /Period=60 /PHDCOLLECT=OVERRIDE
HISTEXTD FIC101 PV
HISTSLOW FIC101 SP /Period=60
HISTFAST FIC201 PV /Period=5
HISTEXTD FIC201 PV

306 www.honeywell.com
14 MANAGING TPS POINTS

HISTEXTD FIC301 PV
HISTEXTD FIC301 SP
2. Click File > Save to save the text file with the .pnt file extension, such as history.pnt.
3. On an LCN-connected Experion Server, click Start > Programs > Accessories > Command Prompt to
open a Command Prompt window.
4. At the Command Prompt type, “pntbld filename.”

The above example will result in the following history collection assignments:

Point Parameter History Assignment PHD Collection


FIC101 PV Fast/Std/Extd Standard
FIC101 SP Std Standard
FIC201 PV Fast/Extd Fast
FIC301 PV Extd Extended
FIC301 SP Extd Extended

For more information about the PHD collection, refer to the “PHD collection rule” section in the Hardware and
Point Build Reference.

To configure TPS points for history collection on an Experion cluster


Identify the TPS points that must be configured for history collection. You must configure history collection
only from a TPS point on an Experion cluster. The TPS point must belong to a TPN unit that is mapped to an
Experion asset on that cluster. Other Experion clusters on the TPN can access this history through the DSA.
As an example, assume the situation in the following table.

TPN Points belonging to the Asset the TPN unit was mapped to in Asset the TPN unit was mapped to in
unit TPN unit Cluster1 Cluster2
A1 TPS_A01 /Assets/A1 Not Mapped
B1 TPS_B01 Not Mapped /Assets/B1
C1 TPS_C01 Not Mapped Not Mapped

Then:
TPS_A01 can only be configured for history collection on Cluster1. Cluster2 can access this history through
DSA.
TPS_B02 can only be configured for history collection on Cluster2. Cluster1 can access this history through
DSA.
TPS_C01 cannot be configured for history collection on Cluster1 or Cluster2.

307
14 MANAGING TPS POINTS

14.3 Configuring history offsets


With standard history collection only, you can load balance history collection across controllers by assigning
individual point parameters to one of fifteen history offset groups. The history data for each configured group is
then collected at a specified time (offset) within the standard history collection cycle. Offset groups in Experion
can be compared with offsets in RDIs in PHD.

Attention
Although history collection can be staggered across the minute by assigning point parameters to an offset group, the
collected data is time-stamped to the minute.

To configure history offsets


1. On the System Configuration menu display, click History Collection to open the History Collection
display.
2. Click the History Offsets tab to open the History Offsets display.
3. On the History Offset display, create an offset group by typing offset values in the Group Offset boxes as
shown in the following example.

4. Click Start > Programs > Accessories > Notepad to open Notepad.
5. For every TPS point parameter that you wish to collect history for, create a new line in a text file using the
following format:
HISTSLOW point param [/group=n]
When configuring offset groups, ensure that history collection can finish within the standard history
collection cycle (typically 1 minute). For example, do not create a group that has thousands of parameters to
collect with an offset of 55 seconds. It is recommended that the largest offset time be 45 seconds.
Examples:

308 www.honeywell.com
14 MANAGING TPS POINTS

HISTSLOW FIC101 PV /group=1


HISTSLOW FIC101 SP /group=1
HISTSLOW FIC201 PV /group=2
HISTSLOW FIC201 SP /group=2
HISTSLOW FIC301 PV /group=3
HISTSLOW FIC301 SP /group=3
HISTSLOW FIC401 PV /group=4
HISTSLOW FIC401 SP /group=4
HISTSLOW FIC501 PV
HISTSLOW FIC501 SP

Tip
A default offset of 0 seconds is assumed for all point parameters not associated with a group.

1. Click File > Save to save the text file with the .pnt file extension, such as history.pnt.
2. On an LCN-connected Experion Server, click Start > Programs > Accessories > Command Prompt to
open a Command Prompt window.
3. At the Command Prompt, type “pntbld filename.”

The above example will result in the following history collection offsets:

Point Parameter Offset(Secs)


FIC101 PV 10
FIC101 SP 10
FIC201 PV 20
FIC201 SP 20
FIC301 PV 30
FIC301 SP 30
FIC401 PV 40
FIC401 SP 40
FIC501 PV 0
FIC501 SP 0

309
14 MANAGING TPS POINTS

14.4 Adding a TPS point to a trend


You add TPS points to trends in the same way as you add native Experion points. The following example
summarizes how to add the PV of a point called “HCI_ AE_A5APP_P01” to a trend. For detailed information
about configuring trends, see the Server and Client Configuration Guide.

Prerequisite for adding a TPS point to a trend


You must be logged on to Station with ENGR or MNGR security level to do this task.

To add a point to a trend


1. In the Configuration Explorer of Configuration Studio, click Trends and Groups.
2. Click the Configure trends task to open the Trend Configuration Summary display.
3. Choose a trend to modify or define.
4. In one of the Point ID fields, type “HCI_AE_A5APP_P01.”
5. Select PV from Parameter.
6. Add other points and configure the other properties as required.

310 www.honeywell.com
14 MANAGING TPS POINTS

14.5 Adding a TPS point to a group


You add TPS points to groups in the same way as you add native Experion points. The following example
summarizes how to add a point called “HCI_AE_ A5APP_P01” to a group.

Prerequisite for adding a TPS point to a group


You must be logged on to Station with ENGR or MNGR security level to do this task.

To add a point to a group


1. In the Configuration Explorer of Configuration Studio, click Trends and Groups.
2. Click the Configure groups task to open the Group Configuration Summary display.
3. Click on “-” in an empty row to call up the Group display.
4. In one of the Point ID fields, type “HCI_AE_A5APP_P01.”
5. From the drop-down list of parameters, select the parameter that you want shown in the group trend and
group numeric history for each point.
6. Add up to seven other points, and configure the other properties as required.

Notes
When using the configuration options of the TPS Connection display, note the following:
If you want to use Experion displays for TPS groups, ensure that the Use TPS groups check box on the
Configuration tab of the TPS Connection display is not selected. Note that this option only applies to the first
450 groups.
If you create Experion groups containing TPS points, it is recommended that you do not select the Use Classic
TPS faceplates option, otherwise you may experience display problems.

311
14 MANAGING TPS POINTS

14.6 Including TPS point data in custom displays


You include TPS point data in custom displays in the same way as you do for native Experion point data. The
following example summarizes the main steps involved in adding an alphanumeric to a custom display which
shows the PV value of a TPS point called “HCI_AE_A5APP_P01”. For detailed information about creating
custom displays, see HMIWeb Display Builder's help.
If you are creating an alphanumeric, when you set the Display as option on the Details tab, use either Numeric
or State Descriptor, do not use Text.

To create a custom display and configure an alphanumeric


1. Start HMIWeb Display Builder.
2. Click File > New > Display to open a blank display.
3. Click the (Alphanumeric) icon on the Toolbox toolbar and then drag the pointer on the display to define the
size, shape, and position of an alphanumeric.
4. Double-click the alphanumeric to open the Properties Window, which shows the alphanumeric's current
properties.
5. Click the Data tab and make sure that Point/Parameter is selected in Type of database link.
6. Type the name of the TPS point in Point, and select PV from Parameter.
7. Configure the alphanumeric's other properties as appropriate.
8. Repeat steps 3 to 7 for other items you want to include in the display.

312 www.honeywell.com
14 MANAGING TPS POINTS

14.7 Writing scripts for TPS points


The following instructions describe how to start writing a script. For detailed information about writing scripts,
see the Server Scripting Reference.

Prerequisite for writing scripts


You must be logged on to Station with ENGR or MNGR security level to do this task.

To write a script for a TPS point


1. Choose Configure > Server Scripting > Point Scripts to open the Server Scripting - Point Scripts
display.
2. Click the ellipsis [—] to open the Point Browser.
3. Search for and select the point and then click Apply to insert it in the Script Editor's Point field.
4. If the Script Editor's Draft tab is not at the front, click it to bring it to the front.
5. Select the event from Event and, if appropriate, the parameter from Parameter.
6. Click inside the editing area and start writing the script. Then, click Scripting Help to open the Server
Scripting Reference.
7. When you have finished, click Commit Draft to Online.

313
14 MANAGING TPS POINTS

14.8 Security level changes in HMIWeb graphics


In TPS it is possible to configure on a system wide basis the minimum security level required for particular
parameters, this affects all points which may have that parameter.
It is common however that there will be a subset of points with this parameter where the extra security level is
not required. To work around this GUS and NW graphics have allowed a method where by the security level
could be increased by scripts in the graphic, a control performed on the parameter and the security level
returned to the original level.
You can use the security level changes in HMIWeb graphics functionality to write to direct connect points i.e.
TPS and CDA, in a Console Station when the Server for the Cluster is unavailable to that Console Station.
Points from the cluster server will not be available for writing while the cluster server is unavailable.
The “Allow controls with modified security levels from Station scripts” check box on the Server-wide
Station Settings page, as shown below, enables this functionality. The selection is disabled by default.

With Experion R400, the Allow controls with “MNGR” security levels from Station scripts option appears
when the Allow controls with modified security levels from Station scripts" check box is selected.

Syntax examples
Two methods are supported:
• SetDataValueWithSecurityLevel
• SetDataValueSynchronuslyWithSecurityLevel
The list of access levels with numeric equivalent is defined as follows:

314 www.honeywell.com
14 MANAGING TPS POINTS

Access Level Numeric Equivalent


MNGR 5
ENGR 4
SUPV 3
OPER 2
ACK ONLY 1
VIEW ONLY 0

Using script data on an object called Rect001, the following code will set FIC101.SP to 42 using ENGR level
security, for an asynchronous control:
Rect001.SetDataValueWithSecurityLevel(“FIC101.SP”, 42, 4)
Using script data on an object called Rect001, the following code will set FIC101.SP to 42 using SUPV level
security. The following code will work for a synchronous control:
fResult=Rect001.SetDataValueSynchronouslyWithSecurityLevel (“FIC101.SP”, 42, 3)

Tip
Where possible, asynchronous calls should be used, as this allows the script to continue.

14.8.1 Scenarios

Migration from existing solution


While building schematics for the system the Engineer realizes that all the SPs of points on the LCN require
ENGR access level. However, a subset of the points the engineer is putting on the schematic need to be changed
by an OPER level user.
The engineer decides that by performing the control to these parameters from a script, he should be able to
increase the security level temporarily to allow the write before reverting to the original level.
The engineer has previously written such scripts on GUS displays and thinks that such functionality should also
be available in HMIWeb displays.

Lock down after security audit


Following a security audit of the system developed in the previous scenario, it is determined that all controls of
parameters requiring higher than OPER level security need to be performed by that level Operator and not rely
on underlying scripts, effective immediately.
The Engineer can disable this elevated security level option via a flag on the Server.
This will cause all future elevated controls to have the elevated security level ignored and the control attempted
at the security level currently in effect at the Station.
The Engineer can then gradually go through the affected displays and remove the “insecure” scripts.

315
14 MANAGING TPS POINTS

14.9 Referencing LCN Boolean parameters as enumerations


With R310, users can put LCN Boolean parameters in a combo box on HMIWeb displays, and via a drop down
list, see the selections “OFF” and “ON”.
The Boolean parameters need to be referenced using the .External" modifier (such as in “A100.Flag.External”)
and need to be shown on a display using “StateDescriptor.”

Attention
Pre-R310 HMI Web Displays that reference LCN Boolean parameters in a form “Point.Parameter.External” and which
are displayed as “Text” are to be changed, so that they are shown as “State Descriptor” in the HMIWeb Display
Builder. If this step is not completed, then the values are shown as “0” or “1”, instead of “OFF” and “ON.”

316 www.honeywell.com
14 MANAGING TPS POINTS

14.10 HMIWeb Display Script Device Read


This feature allows the display developers to get the very latest point parameter value from the controller,
bypassing all the client and server caches, with a new method called TriggerDataUpdate.
TriggerDataUpdate will take in the point and parameter details and the type of read to be performed (such as
whether the value is to be read from device or from the cache). This will trigger a data update. The user can read
the latest modification to the point parameter by attaching a script to the OnUpdate event.
Syntax
TriggerDataUpdate strPointParameter, intDeviceReadFlag
strPointParameter: Point parameter to trigger a data update for.
intDeviceReadFlag: 0 to execute a cache read, 1 to execute a device read.
Example
alpha001.TriggerDataUpdate “FIC123.MODE”, 1
The script device read functionality is available on a Console Station when the Server for the Cluster is
unavailable to that Console Station.

317
14 MANAGING TPS POINTS

14.11 Attaching algorithms toTPS points


You cannot directly attach an algorithm to a TPS point. However, you can indirectly attach an algorithm through
a derived point. A derived point is a standard point (such as an analog or status point) that is mapped to another
point; in this case, a TPS point.
Attaching an algorithm to a TPS point involves creating the derived point in Quick Builder, mapping it to the
appropriate TPS point parameter and then configuring the algorithm on the derived point. The following
procedure summarizes the required steps. For detailed instructions, see Quick Builder's help.

To create and configure a derived point


1 In the Configuration Explorer of Configuration Studio, expand the server of interest, and then click Control
Strategy.
2 Add a user scan task controller and channel and configure them as appropriate.
3 Add a point of the appropriate type (status, analog or accumulator).
4 Assign an appropriate Parent Asset.
5 Set the PV Scan Period to a suitable value, such as 60 seconds.
6 Click the button to the right of PV Source Address to open the Address Builder, and then:
• Set Address Type to Point.
• Type the name of the TPS point in Point Name.
• Type the name of the TPS parameter in Parameter.
• Select the user scan task controller from Controller Name.
• Click OK.
7 Select the algorithm from PV Algo or Action Algo, as appropriate to open an Algo tab.
8 Click the Algo tab and configure the algorithm.
9 Configure the point's remaining properties as appropriate.
10 Download the point to the server.

318 www.honeywell.com
14 MANAGING TPS POINTS

14.12 Deleting, Moving or Cutting over TPS points to CDA

Scenarios
Identify the applicable scenario and follow the steps.

Attention
All commands in the following procedures need to be run using an account that is a member of the Product
Administrators group.

Scenario Steps
Permanently delete TPS points: Have a list 1. Refer section “Permanently Delete TPS Points”
of points that need to be permanently deleted. 2. Refer section “Remove Deleted TPS Point References in Experion”
Find and delete TPS points in Experion that 1. Refer section “Find and Remove Deleted TPS points from Experion”.
no longer exist in the LCN: Some TPS points Keep the .pnt files generated by the dspprime commands on each
have been deleted from the LCN but do not ESVT and ES-T.
have a list of points that were deleted. 2. Refer section “Remove Deleted TPS Point References in Experion”.
Use the .pnt files generated in the previous step as a list of points that
were deleted. Note that there may be references in Experion to deleted
TPS points that are not in the .pnt files.
Delete TPS points and rebuild the same Refer section “Moving TPS Points Within the LCN”
points in a different unit: Have a list of
points that need to be rebuilt.
Delete TPS points and rebuild the TPS Refer section “Moving TPS Points Within the LCN”
points with the same name but with a
different point type: Have a list of points that
need to be rebuilt.
Delete TPS points and rebuild the TPS points Refer section “Moving TPS Points Within the LCN”
with the same name but belonging to a
different data owner. Have a list of points that
need to be rebuilt.
Delete TPS points and build C200/C300 1. Refer section “Backup TPS Point Configuration in Experion”
points with the same name (i.e. cut over 2. Refer section “Permanently Delete TPS Points”
TPS points to C200/C300 points): Have a list
3. Physically disconnect the point from the LCN controller and connect
of points that need to be cut over.
it to the CDA controller.
4. Configure and download the new CDA point using Control Builder.
5. Refer section “Restore TPS Point Configuration in Experion”
Move a TPS unit to a different Experion Refer section “Moving a TPS unit to a different Experion cluster”
cluster

14.12.1 Backing up the TPS point configuration in Experion


The following procedures should be executed, only if you are following a scenario from the preceding section.

To back up the TPS point configuration in Experion


1 Create a text file that contains one point name per line for all the TPS points you want to backup. Save this
file as TPSPoints.txt.
2 Create a batch file called BackupTPSPoints.bat:
@echo off
if not exist “%1” goto help
if “%2”==“” goto help

319
14 MANAGING TPS POINTS

if exist “%2” del “%2”


if exist temp.txt del temp.txt
bckbld -out bckbld.txt > nul 2>&1
for /f %%A in (%1) do @type bckbld.txt | find /i “%%A” >> temp.txt
for /f “tokens=1*” %%A in (temp.txt) do if “%%A”==“SCRIPT” (
echo %%A %%B >> “%2”
) else (
if “%%A”==“TREND” (
echo %%A %%B >> “%2”
) else (
if “%%A”==“GROUP” (
echo %%A %%B >> “%2”
) else (
if “%%A”==“HISTSLOW” (
echo %%A %%B >> “%2”
) else (
if “%%A”==“HISTFAST” (
echo %%A %%B >> “%2”
) else (
if “%%A”==“HISTEXTD” (
echo %%A %%B >> “%2”
) else (
if “%%A”==“HISTEXCP” (
echo %%A %%B >> “%2”
)))))))
del temp.txt
del bckbld.txt
goto end
:help
echo Usage: %0 InputFile OutputFile
:end
3 Backup trend, group, history and server script configuration
All commands in the following procedures need to be run using an account that is a member of the Product
Administrators group.
a At the command prompt, type:
BackupTPSPoints.bat TPSPoints.txt TPSPointsBackup.pnt
b Open the TPSPointsBackup.pnt file and check that the trend, group, history, and server script
configuration have been saved for the selected TPS points.
4 Backup history data
If you have TPS points assigned to history, initiate a history archive:
a In the Station navigate to Configure > History > History Archiving.
b Using the check boxes under History Types to Archive, select the history types you want to archive.
c Click the Archive All Now button.
d If required, backup the history archives (refer to applicable Experion documentation).
e If new points are added with the same point names but with a different parameter set, then it is important
that the history data is synced with your historian (for example. PHD) prior to the deletion of the points.

Attention
History data from PHD that is associated with no longer existent point parameters are still accessible in Experion.
History data from History Archives in Experion that is associated with no longer existent point parameters are not
accessible in Experion.
For example, if a TPS point is cut over to a C200/C300 point with different parameter names, the history collected
by PHD is accessible in Experion. However, the history stored in the History Archive is not accessible in
Experion.
It is possible to retrieve the history data stored in the History Archives for no longer existent point parameters, but
this is a manual process.

5 Backup operator keyboard LED configuration


Repeat the following steps for each Flex, Console Station, and Console:
a Navigate to the Operator Keyboard tab of the Stations configuration display.
b Record the LEDs that are linked to the selected TPS points.

320 www.honeywell.com
14 MANAGING TPS POINTS

6 Backup OPC Integrator


In the OPC Integrator configuration, record where the selected TPS points are used.
7 Backup Algorithms
In the algorithms attached to other points, record where the references to the selected TPS points are used
8 Backup ACE-T and OPC Gateway
In the ACE-T or OPC Gateway configuration, record where the references to the selected TPS points are
used

14.12.2 Restoring TPS point configurations in Experion


When the TPS points are deleted and the C200/C300 points are built to replace them, it is likely that the
parameter names would have changed. This procedure describes what needs to be updated with the new point
and/or parameter names.

Prerequisites
• The “Backup TPS Point Configuration in Experion” procedure has previously been completed.

To restore TPS point configurations in Experion


1 Update custom displays
If some point and/or parameter names have changed, update any displays that reference those point
parameters.
a Open HMIWeb Display Builder and select Tools > Display Builder Assistant.
b Select Create Display Report. In Display folder enter the folder where all your custom displays are
kept. Enter a report name and directory to save the report. Leave all checkboxes in the Include area
checked.
c Run the report.
d Search the report for references to the old point parameter names.
e Edit the displays with HMIWeb Display Builder and update them to reference the new point parameter
names.
Some sites use custom third party controls on their display pages. These controls can reference point
data. You must update the data bindings in these controls manually.
2 Restore trend, group, history and server script configuration
a If some point and/or parameter names have changed, edit the TPSPointsBackup.pnt and update the
changed point parameter names.
b On the primary ESVT log in using an account that is a member of the Product Administrators group. .
c At a command prompt, type:
pntbld TPSPointsBackup.pnt

If the point is now a CDA point, you must upload the assignment to the point configuration in the Control
Builder.
a Go to the Monitoring tab in the Control Builder and right click the new CDA point
b Select the Upload menu option.
c Select only the Upload Server Configuration Information check box, and select Continue.
d Right click the new CDA point in the Monitoring tab again,
e Click the Update to Project menu item, and then select Continue.
f Copy the server scripts attached to the point in TPSPointsBackup.pnt into Control Builder.
g Update the server scripts as required.
3 Restore history data

321
14 MANAGING TPS POINTS

a If required, restore the history archives (refer to applicable Experion documentation). Note that the
history data from the History Archives in Experion that is associated with no longer existent point
parameters is not accessible in Experion.
b To identify whether all the tags on the PHD-Experion link are retrieving history, ensure that all the tags
handled in the Tag Synchronization Acknowledgement tool are found in the PHD Configuration Tool.
c Select a few tags assigned to each history rate (for example. fast, standard, extended) and ensure that the
data values being collected are at the current time. This information can be found by running the
PHDMAN tool from the command line and using the command MON QUE <TAG NAME>.
4 Update server scripts
If some point and/or parameter names have changed, update the server scripts that reference those point
parameters.
a The Server\data\scripts directory on the Experion server contains xml files that include all the server
scripts. Search the xml files in this directory for references to the old point parameter names. Make a list
of the server scripts that refer to the old point parameter names. Do not edit the xml files directly.
b Update the server scripts to reference the new point parameter names.
5 Restore operator keyboard LED configuration
6 Repeat the following steps for each Flex, Console Station, and Console:
a Navigate to the Operator Keyboard tab of the Stations configuration display
b Restore the LED configuration as recorded in Backup TPS Point Configuration in Experion.
7 Restore OPC Integrator
Restore the OPC Integrator configuration as mentioned in the section Backup TPS Point Configuration in
Experion. If a point being cutover is assigned to an OPC Integrator group, then perform the following steps:
a Disable the OPCI group to which the point belongs.
b Reconfigure the point assignment in the OPCI group such that the new point and parameter are correctly
referenced.
c Revalidate the OPCI group.
d Re-enable the OPCI group.
8 Restore Algorithms
Restore the algorithm configuration as referred in the section “Backup TPS Point Configuration in
Experion”
9 Update Alarm groups
Redownload the alarm groups to the servers.
a Open the Configuration Studio and select the System node.
b Select Configure Alarm Groups for this system.
c If some point and/or parameter names have changed, update the alarm groups to reference the new point
parameter names.
d Select Tools > Load Entire Model
e Click OK .
10 Restore ACE-T and OPC Gateway
Restore the ACE-T and OPC Gateway configuration as referred in the section “Backup TPS Point
Configuration in Experion”. If the point is now a CDA point, OPC Gateway would no longer be used as the
C200/C300 points as they can be accessed directly.

14.12.3 Permanently deleting TPS points

Prerequisites
• All Experion servers are running and synchronized.

322 www.honeywell.com
14 MANAGING TPS POINTS

• All local and remote console stations are running.

To permanently delete TPS points


1 Create a text file that contains one point name per line for all the TPS points you want to delete. Save this
file as TPSPoints.txt.
2 Create a batch file called DelTPSPoints.bat:
@echo off
if not exist “%1” goto help
if exist Prime.txt del Prime.txt
if exist Delete.txt del Delete.txt
for /f %%A in (%1) do @echo %%A NAME >> Prime.txt
for /f %%A in (%1) do @echo DEL %%A >> Delete.txt
dspprime -f Prime.txt -v 3 > PrimeOutput.txt 2>&1
pntbld Delete.txt > DeleteOutput.txt 2>&1
goto end
:help
echo Usage: %0 InputFile
:end
3 In the Native Window, run Find Names command to locate all the places the points are used in the LCN.
Save this information for later use.
4 In the Native Window, set the TPS points to INACTIVE.
Note that the HG points do not have a PTEXECST parameter. Instead of setting the points to INACTIVE,
stop the HG points from processing:
a Take the boxes off FULL CONTROL (that is, back to BASIC control).
b For Hiway boxes that do have an IDLE state (Basic Controllers do NOT have this state), either put the
box in IDLE or on HOLD.
c For control points that have a MODE parameter, place the MODE into MAN.
5 In the Native Window alarm summary, acknowledge all alarms on the TPS points that are being deleted.
Make sure there are no alarms listed against the point in the Native Window alarm summary.

Attention
If there are multiple TPS consoles or “Area-Based Alarm Acknowledge” is configured, verify that alarms for all
points that you want to delete have been acknowledged in all alarm summaries displayed on all consoles and areas.

6 On the primary ESVT, run DelTPSPoints.bat TPSPoints.txt


The point is automatically deleted from the ES-Ts connected to the ESVT.
7 In the Native Window (for example, using the DEB engineering tool), delete the TPS point.
8 In the Native Window, perform a manual checkpoint of the node that the point is built on.
9 Perform the following steps on the primary and backup ESVT and each ES-T:
a Open a command prompt and type:
tpncache -DF TPSPoints.txt

This forces the deletion of the points in the list from the TPN Server cache.

Tip
Location of tpncache.exe tool is:
C:\Program Files (x86)\Honeywell\TPS\TPNServer\tpncache.exe

b On the System Management Display, select the TPN Server, right click and the select All Tasks >
Checkpoint.

323
14 MANAGING TPS POINTS

14.12.4 Removing deleted TPS point references in Experion


When the TPS points are deleted, they are automatically removed from the following configuration areas in
Experion:
• Trends and groups
• Operator keyboard LED configuration
The following configuration areas require manual steps to delete references to TPS points:

To remove deleted TPS point references in Experion


1 Update custom displays
Remove references to the deleted TPS points from all custom displays.
a Open HMIWeb Display Builder and select Tools > Display Builder Assistant.
b Select Create Display Report. In the Display folder enter the folder where all your custom displays are
kept. Enter a report name and directory to save the report to. Leave all checkboxes in the Include area
checked.
c Run the report.
d Search the report for references to the deleted TPS points.
e Edit the displays with HMIWeb Display Builder and remove references to the deleted TPS points.
Some sites use custom third party controls on their display pages. These controls can reference point data.
The data bindings in these controls need to be updated manually.
2 Update server scripts
Remove references to the deleted TPS points from all Point, Server, Report, Alert, Periodic, and Library
scripts.
a The Server\data\scripts directory on the Experion server contains xml files that include all the server
scripts. Search the xml files in this directory for the TPS points that are to be deleted. Make a list of the
server scripts that refer to the deleted TPS points. Do not edit the xml files directly.
b Update the server scripts to remove references to the deleted TPS points.
3 Update OPC Integrator
Remove references to the deleted TPS points from the OPC Integrator configuration. If you are using
deleted TPS points in OPC Integrator, the OPC Integrator group from which the point is deleted goes into a
marginal state indicating that there are read or write errors.
4 Update algorithms
Remove references to the deleted TPS points from algorithms attached to other points.
5 Update alarm groups
Deleted TPS points that were part of an alarm group are automatically removed from the alarm group in the
Experion server's real time database.. Configuration Studio, however,,still has the point in the alarm group.
Open the Configuration Studio and select Alarm Groups. Remove the deleted TPS points either manually
from the Alarm Groups or upload from the server.
6 Update ACE-T and OPC Gateway
If the deleted TPS points were used in ACE-T or OPC Gateway, remove the deleted TPS points from the
configuration.

14.12.5 Finding and removing deleted TPS points from Experion


When a TPS point is deleted in the Native Window (for example, using the DEB engineering tool), all instances
of the TPS point in Experion should also be deleted. Experion l automatically deletes the TPS points from the
Experion database if they have been deleted in the LCN. This automatic deletion may not occur at the same time
the point is deleted in the LCN, but at a later time when the point is accessed in Experion (for example, when a

324 www.honeywell.com
14 MANAGING TPS POINTS

display page referencing the point is called up in Experion or Experion attempts to collect history from the
point).
This procedure details how to force Experion to delete TPS points that are in the Experion database but are not
in the LCN. Follow this procedure if you have deleted some points in the LCN but are not sure if the points
have been deleted in Experion.

Prerequisites
• All data owners on the LCN are running. If a TPS point is discovered in Experion but is later deleted from
the LCN, then this procedure removes the point from the Experion. However, if the data owner on the LCN
that used to own the point is not running, then the Experion is not sure whether the point exists or not. In
such a scenario, the point remains in Experion.
• All Experion servers are running and synchronized.
• All local and remote console stations are running. When a TPS point is deleted from the ESVT, the deletion
is automatically replicated to all connected Experion servers and console stations.

To find and remove deleted TPS points from Experion


1 Ensure the ESVT is synchronized with its backup server.
2 Repeat the following steps on the primary ESVT and each ES-T. Note that it important to run these steps on
the primary ESVT and each ES-T as each ES-T may have discovered some TPS points that the ESVT has
not discovered.
a Log in using an account that is a member of the Product Administrators group.
b At the command prompt type:
dspprime -sd tpsdel_<machinename>.pnt

Replace <machinename> with the network name of the PC.


This creates a point build file with a list of all TPS points discovered on the ESVT or ES-T that no longer
exist in the LCN. Save the generated .pnt file for later use.
c At the command prompt, type:
pntbld tpsdel_<machinename>.pnt -del

Replace <machinename> with the network name of the PC.


This deletes all the TPS points found on the ESVT or ES-T that no longer exist on the LCN.
d Each ES-T discovers a different set of TPS points. So run both the dspprime and pntbld commands on
each ES-T. Repeat the above steps on the ESVT and each ES-T.

14.12.6 Moving TPS points within the LCN


When a TPS point is moved within the LCN (for example it is moved to a different unit) the internal ID of the
point changes in the LCN even though the name of the point has not changed. If this procedure is not followed
Experion perceives the moved TPS point as a new point, deletes the original point, and creates a new one with
the same name but a new point number. A consequence of this is that there may be a delay when accessing the
moved point for the first time after it is moved. In addition, the moved point is removed from any Experion
history, groups, or trends that it was assigned to.
The following procedure details how to move TPS points within the LCN and ensure that Experion does not
delete and recreate them.

To move TPS points within the LCN


1 If the TPS points to be moved are assigned to history, groups, or trends on the local server, perform the
following steps on the primary ESVT:
a Ensure the ESVT is synchronized with its backup server.
b Log in using an account that is a member of the Product Administrators group.

325
14 MANAGING TPS POINTS

c At the command prompt, type:


bckbld -np -tag PSA -out ESVTConfig.pnt

This creates an ESVTConfig.pnt point build file with a list of the Experion group, trend, and history
configuration for TPS points.
d Save the ESVTConfig.pnt in a safe place. If for some reason you lose the group, trend, or history
configuration for your TPS points you can restore it with this file.

Tip
Not all points output are TPS points.

2 If the TPS points to be moved are assigned to groups or trends on remote servers, perform the following
steps on each remote server (ESV or ESVT):
a Ensure the remote server is synchronized with its backup server.
b Log in using an account that is a member of the Product Administrators group
c At the command prompt, type (Z is a number):
bckbld -np -tag RDA -out ESVConfig Z.pnt

This creates a ESVConfigZ.pnt point build file with a list of the Experion group and trend configuration
for DSA points, some of these may be TPS points.
d Save the ESVConfigZ.pnt in a safe place. If for some reason you lose the group, trend, or history
configuration for your TPS points you can restore it with this file.

Attention
If you have problems during the TPS point move procedure, you should contact TAC. You will need the
ESVTConfig.pnt and ESVConfigZ.pnt files.

Tip
Not all points output are TPS points.

3 If the TPS points to be moved are used in an ACE-T, disable all CMs that reference the TPS points in the
ACE-T. The TPN server on the ACE-T rediscovers the TPS points once they have been moved.
4 In the Station of the primary ESVT, do the following steps:
a Click Configure > System Hardware > System Interfaces.
b Select the TPS system interface.
c On the Configuration tab of the TPS system interface select the Disable automatic deletion of TPS
points check box. Selecting this option ensures that the Experion server and console stations do not
delete TPS points from the their databases even if the TPN server notifies the Experion server that the
points no longer exist on the LCN.

Attention
If you access points that are being moved, their status may show as bad and no value is available until this
option is cleared.

5 Move the points in the LCN.


6 After the move is complete, do the following steps on the primary ESVT:
a Create a text file called TPSMovedPoints.txt with each line containing the name of a TPS point that has
been moved followed by PTDESC. For example, for points FIC102, FIC115, and FIC150, the file would
look like:
FIC102 PTDESC
FIC115 PTDESC
FIC150 PTDESC
b Create a text file called TPNCacheMovedPoints.txt with each line containing the name of a TPS point
that has been moved. For example, for points FIC102, FIC115, and FIC150, the file would look like:
FIC102

326 www.honeywell.com
14 MANAGING TPS POINTS

FIC115
FIC150
c At the command prompt, type:
tpncache -DF TPNCacheMovedPoints.txt

This forces the deletion of the points in the list from the TPN Server cache.

Tip
Location of tpncache.exe tool:
C:\Program Files (x86)\Honeywell\TPS\TPNServer\tpncache.exe
d At the command prompt, type:
dspprime -f TPSMovedPoints.txt -validate

This forces the Experion to validate the points and change the asset they are built in based on the unit
name the point has in the LCN and the unit mapping configured on the TPS system interface page in
Experion. It also primes the TPN server cache with the new internal ID.
e On the system management display, select the TPN Server, right click and select All Tasks >
Checkpoint.
7 Copy the updated TPN server cache to the backup ESVT:
a On the backup ESVT, open the System Management Display and stop the TPN Server that is running
on the backup server.
b On the backup ESVT, open the Task Manager and end the tpndss.exe process only if it is still running.
c Copy the TPN Server checkpoint file (.HCI file) from the primary server (ESVT) to the same location on
the backup server:
C:\ProgramData\Honeywell\Checkpoints
d On the backup ESVT, move the existing TPN Server checkpoint file to a backup directory, and then
rename the TPN Server checkpoint file that you just copied to the same name as the moved file.
e Use the System Management Display to start the TPN server.
8 Repeat the following steps on each ES-T to prime the TPN server cache on each ES-T with the new internal
ID:
a At the command prompt, type:
tpncache -DF TPNCacheMovedPoints.txt
b At the command prompt, type:
dspprime -f TPSMovedPoints.txt -r
c On the System Management Display, select the TPN Server, right click and the select All Tasks >
Checkpoint.
9 For EAPP and ACE-T nodes only - not for ES-T or ESVT
a At the command prompt,type:
tpncache -RF TPNCacheMovedPoints.txt
b On the System Management Display, select the TPN Server, right click and the select All Tasks >
Checkpoint.
10 In the Station, do the following steps:
a Click Configure > System Hardware > System Interfaces.
b Select the TPS system interface.
c On the Configuration tab of the TPS system interface, clear the Disable automatic deletion of TPS
points check box. Any TPS points that were moved (in step 4) and were being accessed in Experion
Stations and/or other Experion subsystems is now re-subscribed to.

327
14 MANAGING TPS POINTS

Attention
The Disable automatic deletion of TPS points option should only be enabled for short periods of time when
moving points. If it is permanently enabled the system may get into a state where the point exists and is
working fine on the LCN but is showing as bad in Experion.

14.12.7 Moving a TPS unit to a different Experion cluster


Use the following procedure to move a TPS unit to a different Experion cluster. This procedure is applicable,
only if you are using Multiple Experion clusters on one TPN (LCN).

To move a TPS unit if DSA is enabled between the Experion clusters


1 Un-map the TPS unit on the original ESVT.
Any RDA points on the ESVT that are moved to the unmapped TPS unit are automatically deleted.
2 Map the TPS unit on the new ESVT.

To move a TPS unit if DSA is disabled between the Experion clusters


1 On the ESVT where the unit to be moved is currently mapped, run the following command in a command
prompt:
chkem /tpspointslist /outfile tpspoints.txt
You are prompted to enter the TPS unit that is being moved.
This command creates a pntbld file named as, tpspoints.txt, in the current directory from where the chkem
command is run. The command creates the tpspoints.txt with the DEL command on TPS points from the
specified TPS units.
2 Copy the tpspoints.txt file over to the ESVT that the unit is being moved to and run the following command
in a command prompt:
pntbld tpspoints.txt -DEL
This command deletes the unwanted RDA points from the ESVT that the unit is being moved to.
3 Un-map the TPS unit on the original ESVT.
4 Map the TPS unit on the new ESVT.

328 www.honeywell.com
14 MANAGING TPS POINTS

14.13 Peer to Peer Communication between CEE and TPS Points


With R410, native peer-to-peer communication is supported between CEE-controllers and SCADA points
which include TPS points. This communication happens through the Experion Server over an FTE network. The
Experion Server supports data access to TPS points and makes this data available to the CEEs.
This feature provides the ability to configure the control schemes on a redundant platform which reads from/
writes to any point in the system; CEE, SCADA, all TPS points and DSA. Note that TPS points must be primed
before referencing it for peer-to-peer communication. Array parameter of the TPS point must be configured
before configuring the peer-to-peer configuration to the array parameter of the TPS point in the Experion
Controllers (Example: C300, C200E or ACE).
Peer-to-peer can be configured to point-parameter data from anywhere in the namespace of the Experion Server.
This includes SCADA, TPS, OPC (including OPC Advanced Client), DSA and Point Server points.
When you write the expressions using the TPS point's parameter references, ensure that the TPS reference
parameter is configured using the parentheses “()”to specify array index.
Starting with Experion R430, peer-to-peer communication is supported between the ACE/C300 Controller and
the EHPM Controller.
For information on establishing peer-to-peer communication between the ACE/C300 Controller and the EHPM
Controller, refer to the Control Building User’s Guide.

Attention
For better round trip time and parameter throughput in CEE-TPN points communication, the syntax
TAG.PARAMETER.INTERNAL should be used in CMs/SCMs while referring TPN Point parameters.

Refer to the Control Builder Components Theory for more information.

329
14 MANAGING TPS POINTS

330 www.honeywell.com
15 Troubleshooting Experion-TPS nodes

331
15 TROUBLESHOOTING EXPERION-TPS NODES

15.1 Troubleshooting Approach


Identify the symptom from the following table and refer to the subsections for suggested actions.

Error symptom Refer to


Display data access problems “Station and Server do not provide TPN data to Experion displays” on
page 337
“TPS faceplate cannot get data, Native Window schematic access from
Experion fails” on page 339
“Cannot change TPN data from Experion or TPN Server will not write to
TPN” on page 340
“HMIWeb display shows TPS/LCN data as "-----"” on page 341
“HMIWeb display shows TPS/LCN data as "?????"” on page 342
Node or TPN Server status problems “Slow display or faceplate call up with TPS data” on page 343
“TPN Server will not start” on page 344
“TPN Server in Warning state” on page 345
“Experion-TPS Node has Native Window WARNING Status” on page 347
“TPS System Alarm indication out of synch” on page 349
“ES-T appears as UNVL in Native Window” on page 351
“ESVT appears as APP in Native Window” on page 352
“ESVT appears as AM in Native Window” on page 353
“ES-T or ESVT node will not load its personality” on page 354
“ES-T or ESVT TDC Emulators Service has been shutdown” on page 356
“Verifying TPS/LCN Installation and Version” on page 357
“Verifying Configuration of Board 0 Data Access Configuration and TPN
Server Channels” on page 359
Troubleshooting multiple Experion “Getting duplicate TPS alarms” on page 362
clusters on single LCN
“Getting an “Error Synching Tags from [RemoteServer]” alarm” on page 363
“System event journaling and silence synchronization not working” on
page 364
“Multiple TPN System Alarms” on page 365
“Cannot access data or receive alarms from a TPS point” on page 366
“Data from a TPS point owned by another Experion cluster is still accessible
from the local cluster even though the remote cluster is unavailable” on
page 367
“Cannot call up the TPS points that are moved after adding an ESVT to the
same TPN” on page 368

Related topics
“Troubleshooting displays” on page 332

15.1.1 Troubleshooting displays


Techniques for successfully troubleshooting Experion-TPS node problems begin with using the standard
displays your system provides. Generally this includes using the following displays in the following manner:
LCNP Status Display to determine health of the node's LCNP interface (see the LCNP Status User's Guide).

332 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

Native Window node status displays to determine TPS/LCN health.


TPS System Interface display to view the status of the TPS interface.
System Management Display to determine the TPN Server component status (see the TPN Server User's
Guide).
Experion System Status Display to view system alarms.
Displays are available to identify versions and revision of software (see “Verifying TPS/LCN Installation and
Version” on page 357).
Refer to the Server and Client Configuration Guide for troubleshooting Server and Station.

Native Window node status displays


On Native Window status displays, the Node Type indications should be ES-T and ESVT. Status should be
OK with no WARNING messages. The following figure shows an example node status.

TPS System Interface display


Six green lights should appear in Experion System Interfaces display for the TPS interface. The following figure
shows an example display.

333
15 TROUBLESHOOTING EXPERION-TPS NODES

System Management Display


The System Management Display (shown in the following figure) provides a hierarchical view of Windows
domains, TPS Domains, Computers, and HCI Component Status, including the TPN Server. To open this
display, click Start > Programs > Honeywell Experion PKS > System Management > System Management
Display.

334 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

Experion System Status Display


The Experion System Alarm Summary (shown in the following figure) shows the Experion system alarms. To
access the display, click the annunciated System button on the Status bar of the Station application.
The alarms in the Experion System Status Display are from the Windows-resident components and system
alarms from the TPS/LCN.

335
15 TROUBLESHOOTING EXPERION-TPS NODES

Experion Console Station status display


Determine Console Station status from the Experion System Status display. The following figure shows an
example Console Station status display. Click Show Details to view additional indicators.

336 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.2 Station and Server do not provide TPN data to Experion displays

Cause
TPN Server is not running

Solution
Attempt to start the TPN Server from System Management display.

Cause
LCNP is not loaded with node's personality

Solution
Experion-TPS nodes, if LCNP Auto Restart has been enabled for the node, reset its LCNP through the LCNP
Status application and the node will automatically reload.
You can load an ES-T from its Native Window. Select W as source during load.
You can load an ESVT from the TPS/LCN Node Status display. Select AUTOLOAD NET.

Cause
Station has lost connection or is not connected

Solution
View TPS Connection status from System Status > System Interfaces > Status tab.
• Verify that Notifications is enabled.
• All status indications should appear green/OK/Running. Statuses not appearing green/OK/Running can be
investigated further.
In the Console Station display, determine if an IP address is displayed. If no IP address appears, examine the
HOSTS/LMHOSTS files for correct entries at all nodes, including the Domain Controller.
All Experion-TPS nodes will need to have the hosts file configured correctly and identically. The hosts file is
located in the folder, C:\WINNT\system32\drivers\etc and is named “hosts.” Use Notepad to view this file, or
access the Host Files Verification tool in Configuration Studio's Analysis Tools.
Review for other possible IP address conflicts using standard Windows approaches (for example, using ping and
ipconfig commands from the command prompt).

Cause
Station inadvertently configured as Rotary or Static

Solution
From the Station's Connection Properties dialog, verify that the station is configured as “Console Station,” and
not Rotary or Static.

Cause
The Server component residing in ES-T is not running

Solution
Click Start > Programs > Honeywell Experion PKS > Console Station > Start/Stop Experion PKS
Console Station.

337
15 TROUBLESHOOTING EXPERION-TPS NODES

Cause
Local LCN Connection Type not enabled

Solution
Verify that the Local LCN connection type is enabled for the TPS System Interface from the Experion System
Configuration > System Interfaces display.

Cause
The TPN Units are not available as Experion Assets

Solution
This may occur if a customer skipped the task on creating Assets form TPN units or as a result of a software
upgrade. Use Configuration Studio to create/recreate the TPN units as Assets or rebuild with the
appropriate .xml file describing the TPN units as Assets. You may also need to configure the specific assets as
available to the given operator/login.

Cause
SY is not mapped to retrieve PSDP data

Solution
You must map the SY system unit to an Asset. You build assets, including an SY Asset if necessary, using
Enterprise Model Builder. See “SY Unit mapping to Assets”.

338 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.3 TPS faceplate cannot get data, Native Window schematic access
from Experion fails

Cause
LCNP board was restarted without restarting the ES-T

Solution
Log off of the ES-T and then log back on as a Windows user. Shutdown and restart the computer if the symptom
persists.

339
15 TROUBLESHOOTING EXPERION-TPS NODES

15.4 Cannot change TPN data from Experion or TPN Server will not write
to TPN

Cause
Workstation security Link Domain Groups command not executed

Solution
Attention
The following procedure only applies to Experion-TPS nodes in a Windows domain environment.

Click Start Menu > All Programs > Honeywell Experion PKS > System Management > Link Domain
Groups.

340 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.5 HMIWeb display shows TPS/LCN data as "-----"

Cause
TPS/LCN unit not configured (assigned to Assets)

Solution
Configure a TPS/LCN Unit in the Experion Area configuration page (Configuration Studio - Configure Assets).

341
15 TROUBLESHOOTING EXPERION-TPS NODES

15.6 HMIWeb display shows TPS/LCN data as "?????"

Cause
Data format

Solution
The default data format may not be appropriate for the object. Check the details for the object in the HMIWeb
Display Builder.

Cause
Exceeds limits on data objects

Solution
Use the Display Performance Analysis tool to check a display's performance indicators, which include the
number of objects and number of scripts. See the HMIWeb Display Building Guide.

342 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.7 Slow display or faceplate call up with TPS data

Cause
Invalid parameters on a custom display

Solution
Password of the LocalComServer account is not the same on all nodes in the ESVT cluster.
Check for invalid parameters on a custom display as they can increase display call up time.

Cause
Performance guidelines exceeded for using TPS data

Solution
Reference the TPS display guidelines document that describes how to build fast TPS custom displays.

343
15 TROUBLESHOOTING EXPERION-TPS NODES

15.8 TPN Server will not start


In all the cases, right-click the node of interest from the System Management display and click Display Events
from the context menu to invoke its Event Summary. Review the following:
Summary display for errors reported against the TPN Server to determine possible cause.
TPN Server log (C:\ProgramData\Honeywell\TPNServer)

Attention
With the Custom Install Path (CIP) being supported in Experion R410, you can change the default path of installation
(C:\ProgramData\Honeywell) to any possible path.

Cause
User does not have permission to start

Solution
If the user does not have necessary permissions to start the TPN Server fails, it fails the user identity and
password check. The TPN Server requires an account to run the application. For an Experion-TPS node, the
account is LocalComServer. The account is added as part of the package installation.
From Computer Management, reset the password of the user account LocalComServer, and then do the
following steps to use the Honeywell password tool (svrpass.exe) to synchronize the Windows and DCOM
services associated with the newly entered password for the LocalComServer account.
1. Click Start > Programs > Honeywell Experion PKS > System Management > Windows Services &
DCOM Servers Log on tool.
2. Select LocalComServer from the drop down list of accounts.
3. Enter the password of the account, and then click Apply New Account.
Result: A message appears upon successful synchronization.

344 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.9 TPN Server in Warning state


Normally, a TPN Server component in the Warning state indicates a related status with the LCNP.
Determine if the node's LCNP is running with WARNING messages:
View the Experion-TPS node status from the Native Window Console Status display.
View the ESVT or ACE-T node status from Native Window AM Node Status display.
View Device Status and Device Information text in the System Management-TPN Server Component.

Cause
Exceeded the allocated event memory buffer

Solution
In the case of extreme LCN alarm and event traffic for an extended period of time, the load module may exceed
the internally allocated event memory buffers. In this case, the TPN Server's component state will be set into
Warning and a system alarm will be sent to the Experion System Alarm Summary Display notifying the
operator.
The LCN alarm and event load should be decreased to a nominal level.
The TPN Server has some auto-recovery capabilities and may return to a Running state on its own.
If the TPN Server component remains in a Warning state, you may need to stop and restart it from the System
Management Display to re-establish communications with the LCN and load module.

Cause
LCNP was reset

Solution
If the TPN Server has lost its connection to the LCNP because the LCNP was reset, reload the node with its
personality from the Native Window System Status display.

Cause
LCNP is being loaded

Solution
If the LCNP is being loaded, it may not have yet transitioned to a running state. Verify that the node's status
from Native Window Console Status display or Node Status display is OK and that the node appears as the
correct node type.

Cause
Load Module is not configured in the NCF for the node

Solution
Check the node's NCF LCN Nodes configuration. ES-T.LO or ESVT.LO should be listed.

Cause
LCN cable is in Suspect State

Solution
Check the Native Window screen to see if the network cable indicator is indicating a fault.

345
15 TROUBLESHOOTING EXPERION-TPS NODES

Cause
LCN node in ISOLATED State

Solution
If the LCN cables have been disconnected or severed for more than two minutes, the node goes to the
ISOLATED state.
The only way to recover from this condition is to
Re-connect the cables;
Re-start the TDC emulators;
Re-load the LCNP.

WARNING
The steps detailed above are the ONLY way to recover.
The TPN Server, LCN, and Experion will NEVER recover by themselves if the LCN node is ISOLATED.

346 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.10 Experion-TPS Node has Native Window WARNING Status


Invoke the node's Auxiliary Status to view the WARNING message:
• For Server or ACE-T, go to the Native Window System Status or Node Status display, select the node, and
then select Status Detail.
• For ES-T, go to the Native Window Console Status display, select the node, and then select Status Detail.

Cause
Auxiliary Status message "Linking Errors"

Solution
The Auxiliary Status message of “Linking Errors” means that the Experion-TPS load module did not load
properly.
If the ES-T is loaded with the Universal Station personality, it appears, as UNVL in the Native Window's
Console Status display and the node will be in a WARNING state.
If the ESVT is loaded with the Application Module personality, it appears as AM in the Native Window's Node
Status display and the node will be in a WARNING state.
Reset the LCNP and re-load the node with the correct personality.
If manually reloading the ES-T, select W when the LOAD prompt appears.

Cause
Auxiliary Status message "Communication Errors"

Solution
This Auxiliary Status message appears:
“WARNING Communication” Errors. May need to Restart TPN Server”.
In this case, the TPN Server's component state appears as Warning and a system alarm has been sent to the
Experion System Alarm Summary Display notifying the operator.
The TPN Server has some auto-recovery capabilities and may return to a Running state on its own. This will
cause the Load Module to return to the OK state. However, if the TPN Server component remains in a Warning
state, you may need to stop and restart it from the System Management Display to re-establish communications
with the LCN and load module.

Cause
Auxiliary Status message "Event Memory Full. Possible Lost Events"

Solution
This Auxiliary Status message appears:
“WARNING. Event Memory Full. Possible Lost Events. Restart TPN Server.”
In the case of an extreme LCN alarm and event traffic for an extended period of time, the Experion-TPS node's
load module may exceed its internally allocated event memory buffers. In this case, the TPN Server's
component state will be set into Warning and a System Alarm will be sent to the Experion System Alarm
Summary Display notifying the operator.
The LCN alarm and event load should be decreased to a nominal level.
The TPN Server has some auto-recovery capabilities and may return to a Running state on its own. This will
cause the Load Module to return to the OK state. However, if the TPN Server component remains in a Warning

347
15 TROUBLESHOOTING EXPERION-TPS NODES

state, you may need to stop and restart it from the System Management Display to re-establish communications
with the LCN and load module.

Cause
Auxiliary Status message "Had Extended Comm Errors & Exited"

Solution
This Auxiliary Status message appears:
“WARNING. Had Extended Comm Errors & Exited. Restart TPN Server.”
If the ES-T.LO or ESVT.LO load module does not hear from either the TPN Server or any LCN events for over
40 seconds, then it determines that extended communication errors have occurred and the load module will exit.
When the load module exits in this manner, it sets the node state into WARNING and reports the above
auxiliary node message. In this case, the TPN Server's component state will be set into Warning and a system
alarm will be sent to the Experion System Alarm Summary Display notifying the operator.
The TPN Server should be stopped and restarted from the System Management Display to re-establish
communications with the LCN and load module.
If the TPN Server component stays in the Test state, the LCNP board may have to be reset and the personality
reloaded. In addition, the TDC Emulators service may need to be stopped and restarted.

348 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.11 TPS System Alarm indication out of synch

Cause
This is the first ES-T being commissioned in your system

Solution
TPS System Alarm indication will be out of synch until a new TPS System Alarm arises on the TPN while the
ES-T is online.

349
15 TROUBLESHOOTING EXPERION-TPS NODES

15.12 ES-T appears as GUS in Native Window

Cause
TPN Server has not been started

Solution
Start the TPN Server from the System Management display.

350 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.13 ES-T appears as UNVL in Native Window

Cause
Universal Station personality was loaded

Solution
Reset the LCNP and re-load the node with the correct personality.
If manually reloading, select W when the LOAD prompt appears.

351
15 TROUBLESHOOTING EXPERION-TPS NODES

15.14 ESVT appears as APP in Native Window

Cause
The TPN Server is not running

Solution
Start the TPN Server from the System Management display.

352 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.15 ESVT appears as AM in Native Window

Cause
The Application Module personality was loaded

Solution
Reset the LCNP and re-load the node with the correct personality.
If manually reloading, select AUTOLOAD NET from the Native Window.

353
15 TROUBLESHOOTING EXPERION-TPS NODES

15.16 ES-T or ESVT node will not load its personality


If the TPN Server is configured to Autostart, the node will transition directly to the Station or Server node type;
however, if the TPN Server is not configured to Autostart, you may see transitory node types, such as APP (for
Server) or GUS (for Station) until you start the TPN Server.
Click Start > Programs > TPS Applications > LCNP Status to invoke the node's LCNP Status display to
determine if the node is in a loadable state. An example LCNP status appears in the following figure.

Check the LCNP Status display to see if 001c appears in the area shown below. The indication must be 001c in
order for the node to load.

• If 0004 appears, the node will NOT load as a GUS, ES-T, APP, or ESVT.
• If 0004 appears, you need to stop and restart the TDC Emulators service.
For more information about the LCNP display, see the Determining LCNP Status User's Guide.

Cause
Node's personality files are missing or inaccessible

Solution
Refer to the configuration procedures for copying the personality files to storage media if manually attempting
an ES-T load and the load fails with a “W” prompt.
If attempting an ESVT load, determine if system HM is running.

354 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

Determine if alternate media are available such as Fast Load cartridges or emulated disks whereby you can load
from removable media.

Cause
LCNP is not ready to accept a personality load

Solution
From the LCNP Status, reset the LCNP and determine if the LCNP can go to a PWR_ON or QUALIF state. In
those states, an LCNP can accept a personality load.
The LCNP Status LEDs button should indicate the node's address. Common reasons for the node address not
appearing can include that the node's LCNP board has not been configured from the Configuration Utility; in
which case, NOTCONFG appears in the LEDs button.
NCF revision mismatches can also cause error codes to appear in the LEDs button.

355
15 TROUBLESHOOTING EXPERION-TPS NODES

15.17 ES-T or ESVT TDC Emulators Service has been shutdown

Cause
Board0 has not been configured correctly

Solution
A message indicates that the TDC Emulators Service has been shut down by the node.

356 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.18 Verifying TPS/LCN Installation and Version


The Native Window CBREV schematic and System Maintenance Control Console (SMCC) provide installation
and software revision data for the TPS/LCN components.

15.18.1 Verification of Load Module installation: CBREV Schematic


Once the node's NCF configuration has been installed and the proper node personality loaded, from a Native
Window or Universal Station, invoke the schematic CBREV.
Select the SELECT & SPECIFY NODE target and type the TPS/LCN node number for the Experion-TPS
node. The resulting display shows the node's load module configuration.

15.18.2 Verification of TPS/LCN release


The TPS/LCN release loaded into a node can be verified from the Native Window SMCC, accessed from the
Engineering Main Menu. The following figure illustrates the steps to access the node information.
Refer to the Experion PKS General Release Software Change Notice (SCN) for the media version that is
appropriate for respective Experion releases (recommended).

357
15 TROUBLESHOOTING EXPERION-TPS NODES

15.18.3 Verification of TPS/LCN personality files on local drive


The version of the TPS/LCN personality files that have been placed on the node's local hard drive can be
verified through the following text files (See the ATTENTION box below):
For Server: C:\Program Files\Honeywell\TPS\Emulators\Personalities\AM\version.txt Example file content:
AXM Personality 64.12
For ES-T: C:\Program Files\Honeywell\TPS\Emulators\Personalities\US\version.txt Example file content: UXS
Personality 64.12

Attention
• With Experion R410, 64-bit OS is supported. All 32-bit components are installed in C:\Program Files (x86). The
default path for installation of TPS components (T-Nodes) is C:\Program Files (x86)\Honeywell\TPS.
• The Custom Install Path (CIP) is supported in Experion R410. You can choose any possible path for installation
(for example, D:\TEST\Honeywell\TPS).
• TPN personalities prior to TPN R683 must be installed in the old path, C:\Program Files\Honeywell\TPS
\Emulators\Personalities\<AM/US>, in 64-bit OS support. From TPN R683 onwards, both the GUS and the APP
personalities support 64-bit OS and CIP.

358 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.19 Verifying Configuration of Board 0 Data Access Configuration and


TPN Server Channels
To prevent system (performance/reliability) problems caused by incorrect configuration of Board 0 Data Access
Configuration and TPN Server Channels on ESVT, ACE-T, Experion APP, and ES-T nodes, follow these
instructions to check and verify the configuration settings.

WARNING
The default Honeywell installation of the various node types will set the appropriate configuration for TPN Server
Channels and Board 0 Data Access Configuration.
DO NOT CHANGE THE DEFAULT CONFIGURATION unless advised to do so by the appropriate
Honeywell support organization.
Improper changes can severely impact node performance.

Attention
Honeywell recommends that you check all existing LCN-connected Experion nodes and verify that they have the
correct default configuration. The configuration may have been modified improperly, or a different configuration may
remain from a previous release.

To verify the configuration of TPN Server Channels


1 Click Start > Programs > Honeywell Experion PKS > System Management > Configuration Utility.
2 Select Configure > HCI Component.
3 On the HCI Component configuration page, select TPNServer_<computername> from the Component
Name pull-down list.
4 Click Enter/Edit Server Specific Configuration.
5 Click Yes on the dialog box that appears.
6 On the Channels tab shown below, verify that the values are correct as shown in the following table of
default values:

TPN Server Channels ESVT ACE-T ES-T E-APP


Channels to be Allocated 14 10 10 10
High Priority Channels 5 5 2 2

Note: Honeywell recommends a value of 100 for Outstanding Requests.

359
15 TROUBLESHOOTING EXPERION-TPS NODES

7 If necessary, correct the values and then click OK.


8 Close the Configuration Utility.
9 If you changed the values, stop and restart the TPN Server component.

To verify the configuration of Board 0 Data Access Configuration


1 Click Programs > Honeywell Experion PKS > System Management > Configuration Utility.
2 Select Configure > [LCNP board name], where [LCNP board name] is “Board 0” (the default name) or a
customized name.
3 Click the Data Access Configuration tab.
4 On the Data Access Configuration tab shown below, verify that the values are correct as shown in the
following table of default values:

Board 0 Data Access Configuration ESVT ACE-T ES-T E-APP


High Priority Channels 5 5 0 10
High Priority Servers 2 4 0 4

360 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

5 If necessary, correct the values, and then click OK.


6 Close the Configuration Utility.
7 If you changed the values, reload the LCNP.

361
15 TROUBLESHOOTING EXPERION-TPS NODES

15.20 Getting duplicate TPS alarms

Cause
A TPN unit is mapped to more than one Experion cluster

Solution
Run the chkem /tpsmappings command in a command prompt on the ESVT of each Experion cluster where
you see the duplicate TPS alarms. This identifies all the TPN units mapped on the local cluster that are also
mapped on another Experion cluster.
Remove the unit mapping on clusters that must not have the TPN unit mapped according to the plan mentioned
in “TPS Connection - Tuning properties”. To remove a unit mapping on a cluster, perform the following steps.
1. Clear the Notifications checkbox in the Status tab of the TPS Connection Status display in Experion.
2. In the Unit Mapping tab of the TPS Connection display, identify the TPN units to be removed.
3. Set the mapping of that unit to “Not Mapped”.
The message about deleting the TPS points in the asset from the Experion point database appears.
4. Click Yes.
5. Select the Notifications checkbox in the Status tab of the TPS Connection display in Experion.

362 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.21 Getting an “Error Synching Tags from [RemoteServer]” alarm

Cause
A TPN unit is mapped to the same asset on two Experion clusters

Solution
Run the chkem /tpsmappings command in a command prompt on the ESVT in each Experion cluster where you
see the “Error Synching Tags from [RemoteServer]” alarm. This identifies all the TPN units mapped on the
local cluster that are also mapped on another Experion cluster. With the special case of the SY unit which needs
to be mapped on each Experion cluster, the tool will indicate if it has also been mapped to the same asset on
another Experion cluster.
Remove the unit mapping on clusters that are not meant to have the TPN unit mapped according to the plan as
mentioned in “TPS Connection - Tuning properties”. To remove a unit mapping on a cluster, perform the
following steps.
1. Clear the Notifications checkbox in the Status tab of the TPS Connection display in Experion.
2. In the Unit Mapping tab of the TPS Connection display, identify the TPN unit to be removed.
3. Set the mapping of that unit to “Not Mapped”.
The message about deleting the TPS points in the asset from the Experion point database appears. Click Yes.
4. Select the Notifications checkbox in the Status tab of the TPS Connection display in Experion.
On each Experion cluster where the “Error Synching Tags” alarm appears.
a. Go to the System Status Display in Experion and find the alarm from the local server in the System
Components tree.
b. Double-click on this alarm. The Distributed Server Status display for [RemoteServer] screen appears.
c. Click Manual Update. Wait until the message Tag Statistics Updated appears in the message zone in
Station.
d. The “Error Synching Tags” alarm returns to normal.

363
15 TROUBLESHOOTING EXPERION-TPS NODES

15.22 System event journaling and silence synchronization not working

Cause
SY unit is not mapped to an Experion asset

Solution
Run the chkem /tpsmappings command in a command prompt on the Experion cluster where there is a problem.
An error appears if the SY unit is not mapped on the Experion cluster. To map the SY unit to an Experion asset
on the Experion cluster, perform the following steps.
1. Clear the Notifications checkbox in the Status tab of the TPS Connection display in Experion.
2. In the Unit Mapping tab of the TPS Connection display in Experion, identify the SY unit in the list and map
it to an appropriate asset as mentioned in “TPS Connection - Tuning properties”.
3. Select the Notifications checkbox in the Status tab of the TPS Connection display in Experion.

364 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.23 Multiple TPN System Alarms

Cause
Incorrect configuration of the TPN System Alarm

Solution

If… Then…
Only one Experion cluster is configured in the system to Ensure that only one Experion cluster is responsible for
report the TPN System Alarm publishing the TPN System Alarm. For every other
Experion clusters on the same TPN, you must disable the
TPN System Alarm on all ESTs in those clusters. For more
information, see “Add Experion servers to EMDB”.
The subscriptions to the network tree alarm between all the Ensure to disable the network tree alarm subscriptions
clusters is disabled in the system between all the clusters in the system. For more information,
see “Configure DSA”.

365
15 TROUBLESHOOTING EXPERION-TPS NODES

15.24 Cannot access data or receive alarms from a TPS point

Cause
The TPN unit of the TPS point is not mapped to an assignable asset on any of the Experion clusters

Solution
Call up the point detail for the TPS point in the Native Window and find out the TPN unit it is in. Review the
TPN unit mapping configuration plan as mentioned in “TPS Connection - Tuning properties” to see which
Experion cluster this TPN unit is supposed to be mapped. On the identified Experion cluster, map the TPN unit
to an assignable asset. To map a TPN unit to an assignable asset, perform the following steps.
1. Clear the Notifications checkbox in the Status tab of the TPS Connection display in Experion.
2. In the Unit Mapping tab of the TPS Connection display in Experion, identify the TPN unit in the list. Set
the mapping of that unit to the assignable asset.
3. Select the Notifications checkbox in the Status tab of the TPS Connection display in Experion.

366 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.25 Data from a TPS point owned by another Experion cluster is still
accessible from the local cluster even though the remote cluster is
unavailable

Cause
The TPS point has been built with an incorrect point type

Solution
Run the chkem /tpspoints command in a command prompt on all ES-T and ESVT nodes of both the local and
the remote cluster. This verifies if a TPS point is built with the incorrect point types corresponding to whether
they are owned by the local or a remote cluster.
Follow the recommendations output by the tool which may involve deleting some of the TPS points with
incorrect point types and/or correcting TPS unit mapping configuration.

367
15 TROUBLESHOOTING EXPERION-TPS NODES

15.26 Cannot call up the TPS points that are moved after adding an ESVT
to the same TPN

Cause
ESVT added to the TPN was originally accessing the same points from the existing ESVT

Solution
Calling up the TPS point the first time will try and get data from the original ESVT which no longer has the
point. The point representing the remote data will be deleted and Experion will indicate that the point doesn't
exist. The next time the point is called up, it will be discovered on the local TPS interface and should work
correctly from then on. You can avoid the above scenario by following these steps:
1. On the existing ESVT where the TPN units were unmapped, run the following commands.
bckbld -out bckbld.txt -tag rda
findstr /R “^DEL” bckbld.txt > findstr.txt
for /f “tokens=2” %A in (findstr.txt) do @echo %A.NAME >> rda.txt
dspprime -f rda.txt -validate
2. First time call up of TPS points that have been moved to the new cluster should now work.

368 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.27 Unable to write to TPS points using an OPC client connected to the
ESVT OPC server

Cause
The Default Access Level for TPN Server might not be set correctly

Solution
With Experion R311.2 and earlier, all TPS point parameter writes performed from the OPC clients using the
ESVT OPC Server were performed at the “Program” access level. With Experion R311.2 and later, the default
Access Level setting on the TPN server will be used by the ESVT as the security level for the writes from the
OPC clients connected to the Experion OPC server.
Perform the following steps on both the primary and backup ESVT to set correct default access level for the
TPN Server.
1. On the ESVT node, choose Start > All Programs > Honeywell > Experion PKS > System Management
> Configuration Utility.
2. Choose Configure > HCI Component.
3. From the HCI Configure Component page, click Enter/Edit Server Specific Configuration.
4. Click the Default Access and Priority Levels Page tab.
5. Select the access level from the Access Level drop-down list that you want OPC clients connected to the
Experion OPC server to use when writing to the TPS points.

369
15 TROUBLESHOOTING EXPERION-TPS NODES

15.28 Cannot access data or alarms from TPS points over DSA

Cause
TPS unit mapping was moved from one ESVT cluster to another ESVT cluster

Solution
Perform the following steps
1. On the local Experion cluster (DSA subscriber), navigate to the Configuration tab of the Distributed
Server display for the remote Experion cluster (DSA publisher). Select Disable both Alarm and Data from
the Alarms and Data Subscriptions drop-down list.
2. On the local Experion cluster (DSA subscriber), click Update in the Configuration tab of the TPS
Connection display in Experion.
3. On the remote Experion cluster (DSA publisher), click Update in the Configuration tab of the TPS
Connection display in Experion.
4. On the local Experion cluster (DSA subscriber), navigate to the Configuration tab of the Distributed
Server display for the remote Experion cluster (DSA publisher). Select Enable both Alarm and Data from
Alarms and Data Subscriptions drop-down list.
5. On the local Experion cluster (DSA subscriber), click Manual Update in the Status tab of the Distributed
Server display for the remote Experion cluster (DSA publisher). Wait until the message Tag Statistics
Updated appears in the message zone.

370 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.29 Annunciator is activated for a few seconds when a TPS alarm that
has been shelved goes back into alarm

Cause
When an alarm from a TPN point that was shelved on an ES-T re-alarms, if TPN has been configured to control
the annunciator via the NCF, TPN will activate the annunciator

Solution
Refer to section “4.11 Configure Audible Annunciation” that describes the topologies that support alarm
shelving and what node the annunciator needs to be connected to.

371
15 TROUBLESHOOTING EXPERION-TPS NODES

15.30 Annunciator is silenced without operator interaction

Cause
If the annunciator has been activated and a shelved alarm from a TPN point re-alarms, TPN will silence the
annunciator

Solution
Refer to section “4.11 Configure Audible Annunciation” that describes the topologies that support alarm
shelving and what node the annunciator needs to be connected to.

372 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.31 'S' and 'C' indicators don't appear in the Station status bar on an
ES-T

Cause
The TPS system interface hasn't been created in Experion

Solution
Experion will only show the ‘S’ and ‘C’ in the Station status bar of an ES-T that has the TPS system interface
created. The steps in section “2.3 Post Installation Tasks for ES-T/ESVT/ACE-T” describe how to create and
configure the TPS system interface in Experion.

373
15 TROUBLESHOOTING EXPERION-TPS NODES

15.32 There are blank boxes where the 'S' and 'C' indicators should be on
the Station status bar

Cause
The TPS system interface connection is not OK

Solution
In Experion Station navigate to: View > System Status > System Interfaces > TPS. Ensure all the status
indicators are green. If they are not all green, check that the TPN server is running and the LCNP Status is OK.

Cause
The SY Unit is not mapped or is disabled

Solution
Ensure the SY unit is mapped. Refer to section “4.6 Map TPS Units to Experion Assets”.
In Experion Station navigate to: Configure > Alarm & Event Management > Alarms. Ensure the Asset that
the TPS SY unit is mapped to is enabled

Cause
Notifications from TPS are disabled

Solution
In Experion Station navigate to: View > System Status > System Interfaces > TPS. Ensure the “Notifications
Enabled” checkbox is checked.

Cause
Alarms are disabled server wide

Solution
In Experion Station navigate to: Configure > Alarm & Event Management > Alarms > Alarm Processing.
Ensure the “Alarms enabled server-wide” checkbox is checked.

374 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.33 'S' and 'C' indicators in Experion Station don't match the 'S' and 'C'
indicators in Native Window

Cause
ES-T load module needs to be updated

Solution
If the ‘S’ and ‘C’ indicators in Experion Station always show OK state, even when Native Window ‘S’ and ‘C’
indicators show a problem, it may mean that the ES-T load module version needs to be updated. Refer to section
“3.1 Copy Load Modules to HM”
Refer to the Experion PKS General Release Software Change Notice (SCN) for the ES-T load module version
that is required for the 'S' and 'C' indicators to function.

Cause
An old tps.xml mapping file is being used

Solution
Some additional entries were added to the tps.xml mapping file to support showing the ‘S’ and ‘C’ indicators in
Experion Station. During a migration the tps.xml mapping file should be automatically updated to the new
version. However if the migration instructions were not followed correctly the old tps.xml file may be being
used.
Check whether your tps.xml mapping file includes the following lines (default location is C:\ProgramData
\Honeywell\Experion PKS\Server\data\mapping\tps.xml):
<category name=“TPN System Sts Alarm” type=“Condition” mapto=“System Alarm” hscfunction=“true”>
</category>
<category name=“TPN Console Sts Alarm” type=“Condition” mapto=“System Alarm” hscfunction=“true”>
</category>
If these lines are missing from your tps.xml mapping file then you will need to update your tps.xml file with the
latest version.

375
15 TROUBLESHOOTING EXPERION-TPS NODES

15.34 CEE-TPS peer-to-peer points are not getting historized after adding
them in server history table in Control Builder

Cause
Configuring history collection for CEE-TPS points (through C200/C300 controllers) results in unnecessary
traffic and overload, and these points cannot be historized even after adding them in server history table in
Control Builder.

Solution
CEE-TPS points must be historized through history assignment on ESVT nodes.

376 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.35 CDA display call up is slow on a flex station

Cause
EHPM standard history collection at the start of a specified time is impacting the CDA display call up

Solution
Ensure history offsets are used to distribute the standard history load over the entire minute.

377
15 TROUBLESHOOTING EXPERION-TPS NODES

15.36 Standard history not collected for an EHPM

Cause
FTE network communication problems

Solution
Perform the following steps
1. Check FTE status display to diagnose network.
2. Check EHPM IP address on LED front panel if it is identical with the server BOOTP configuration.

Cause
CDA server components are not running or they have failed

Solution
Check the status of the CDA service in Control Panel. Restart if needed.

Cause
TPN Server has not been started

Solution
Start the TPN Server from the System Management display.

378 www.honeywell.com
15 TROUBLESHOOTING EXPERION-TPS NODES

15.37 Cannot build C200/C300 CDA points even though the TPS point
with the same name is deleted from the LCN

Cause
TPN Server browse cache still has a reference to the TPS points that are deleted from the LCN

Solution
When a point is deleted from the LCN, an LCN event is generated in the TPN Server. The TPN Server monitors
the LCN for such events and removes the point from its browse cache. In rare circumstances, the TPN server
may still have a reference to a TPS point in its browse cache that is deleted from the LCN.
To delete references to TPS points (that are deleted from the LCN) in the TPN Server browse cache, perform the
following procedure.
1. Refresh the browse cache in the TPN Server by stopping and restarting the TPN Server.
2. On the TPS configuration page in Experion, click the "Update" button.

379
15 TROUBLESHOOTING EXPERION-TPS NODES

380 www.honeywell.com
16 TPS PRIMMOD and Experion Aggregate Alarming

381
16 TPS PRIMMOD AND EXPERION AGGREGATE ALARMING

16.1 About aggregate alarming


Operating displays are often organized hierarchically to support the required overview and task oriented
displays for the operator. Aggregate alarming provides infrastructure to greatly simplify the configuration and
use of the aggregated alarm information required to support the navigation between these hierarchically
organized displays.
For more information about aggregate alarming, see the “Configuring Aggregate Alarming” section in the
Server and Client Configuration Guide.

382 www.honeywell.com
16 TPS PRIMMOD AND EXPERION AGGREGATE ALARMING

16.2 Importing TPS PRIMMOD groups


If you use PRIMMOD groups in your TPS system, you can import them into Experion as alarm groups. To do
this, you first use the TPSPrimmodImport tool to create an XML file that contains data related to your
PRIMMOD groups. After you have created the XML file, you import this file into Enterprise Model Builder to
create alarm groups. The TPSPrimmodImport tool runs from a command prompt.

16.2.1 Prerequisite for importing


TPN server is running.

To create the XML file


1. On the Experion server computer, open a command prompt and change the directory to C:\Program Files
\Honeywell\Experion PKS\Server\Run.

Attention
• With Experion R410, 64-bit OS is supported. All 32-bit components are installed in C:\Program Files (x86). The
default path for installation of Experion PKS is C:\Program Files (x86)\Honeywell\Experion PKS.
• The Custom Install Path (CIP) is supported in Experion R410. You can choose any possible path for installation
(for example, D:\TEST\Honeywell\Experion PKS).

1. Type “TPSPrimmodImport.exe” for instructions on how to use the import tool.


2. Create an XML file according to the instructions obtained in step 2.

To import the XML file into Enterprise Model Builder


1. In Configuration Studio, connect to the system into which you want to import PRIMMOD groups.

383
16 TPS PRIMMOD AND EXPERION AGGREGATE ALARMING

2. In Configuration Explorer, click the name of your system.


3. Click the Configure Alarm Groups for this system task to start Enterprise Model Builder.
4. In Enterprise Model Builder, click File > Import.
5. Browse to the location of the XML file and then click Import.

384 www.honeywell.com
17 Appendix

385
17 APPENDIX

17.1 Processing custom defined IKB OEP keys on an ES-T


A programmable key on an IKB or OEP will be processed by the Experion station if this key has been assigned
an action in the current station .stb file. If a key does not exist in the .stb file, then it will be processed by the
Native Window, following its configuration in the current LCN area button file.
The supplementary .stb files that are delivered only with the ES-T nodes ( for example, ikb-ES-T.stb) are the
original versions of the Experion .stb files with the programmable keys removed. For example, the ikb-ES-T.stb
is the same as the ikb.ES-T, but the programmable keys (RFKP 1-85) have been deleted.
When a programmable key is sent to the Native Window, Native Window will automatically get activated and
obtain input focus. The activation of the Native Window is needed when a particular key is invoked for
example, a schematic inside the Native Window.

17.1.1 System Registry key assignments


This special key behavior is controlled on a global and on a key-by-key basis and can be controlled differently
across different areas, i.e. a key-in-area basis. Control is provided via the System Registry as outlined below.

Tip
These registry values do not assign keys for processing in the Native Window. The assignment is accomplished by
the presence or absence of a particular key in the Experion .stb file.
These registry settings are used only to override the activation of the Native Window, for the keys to be processed in
the Native Window. The Native Window application must be running and should have a SafeView placeholder
assigned.
If the TPS key is not available then you must manually create the key and the subkeys.

Registry Key Value Comments


HKEY_LOCAL_MACHINE\SOFTWARE\ DWORD Activate_Default = 0 Default activation of the
Native Window is disabled.
Honeywell\TPS\RFKPKeys\
NWActivation
DWORD Activate_Default = 1 As default Native Window will
activate (also, if the value does not
exist).
DWORD RFKP_n (n: 1 - 85)= 0 Activation of the Native Window is
disabled for a key in any area.
DWORD RFKP_n (n: 1 - 85)= 1 Native Window will activate for this
key.
HKEY_LOCAL_MACHINE\SOFTWARE\ DWORD RFKP_n (n: 1 - 85)= 0 Activation of the Native
Window is disabled for a
Honeywell\TPS\RFKPKeys\
key when node is in LCN
NWActivation\Area_x (x: 1 - 10) area x.
DWORD RFKP_n (n: 1 - 85)= 1 Native Window will activate for a
key when in area x.

Native Window System Registry key example


Most of the programmable keys need to be processed without activating the Native Window. However, the
key RFKP_1 has been assigned a native window schematic and should always activate Native Window.
Additionally, the key RFKP_85 has been assigned a special LCN schematic that needs the activation of
Native Window as well, but only if the node is in the LCN area 3.
The following table shows how the registry keys should be set for this example.

386 www.honeywell.com
17 APPENDIX

Registry Key Value


HKEY_LOCAL_MACHINE\SOFTWARE\Honeywell\TPS\RFKPKeys\NWActivation Activate_Default=0
RFKP_1=1
HKEY_LOCAL_MACHINE\SOFTWARE\Honeywell\TPS\RFKPKeys\NWActivation RFKP_85=1
\Area_3

Attention
The numbering scheme used when defining registry overrides follows the Experion convention and not the
convention used in the LCN button file editor. For example, the key RFKP_1 is the key # 7 in the LCN button
file editor. The key RFKP_80 is the key # 1 in the button file editor.
It is possible to use the Experion station key editor dialog to determine the Experion index for a particular key
(Station/Connection Properties/Toolbars/Customize/Keyboard Shortcuts).

Example OEP

387
17 APPENDIX

17.2 ACE-T Guidelines


As shown in the following illustration, a prefetch request from the ACE-T node is sent through the Control Data
Access (CDA) to the OPC gateway. The OPC gateway forwards the request to Total Plant Network (TPN) OPC
server (TPNServer), using the OPC interface. The TPN OPC server forwards the request to the intended node,
which could be owned by the HPM module through NIM as illustrated in below figure. The node responds to
the requests to the TPN server and the TPN server forwards the request to the OPC gateway. The OPC gateway
sends the response through the CDA to the blocks running in the ACE-T node.

For information about ACE-T, see the Application Control Environment User's Guide.

17.2.1 ACE-T capacity and performance


Existing specifications already documented for ACE, OPC Gateway, and TPN Server also apply to the ACE-T
node, which includes a direct LCN connection. In addition, the specifications in this section are specific to
ACE-T.

Attention
Note that it will be possible to comply with all ACE-T specifications and still create capacity or performance problems
on the TPS system to which the ACE-T is connected.
Users need to carefully consider the impact of an ACE-T on the underlying LCN, HGs, Hiways, CBs, NIMs, UCNs,
xPMs, and so on.

17.2.2 ACE-T configuration options


With Experion R311.2, the capability to prefetch data from the LCN using an OPC gateway reduces load on the
LCN and the ultimate data owners. In addition, the current values are delivered to the requesting control
strategy.

388 www.honeywell.com
17 APPENDIX

The following table lists the configuration options and the control processing specifications to utilize the
prefetch feature.

ACE-T Configuration options


Maximum Number of OPC Gateways 3
Recommended Number of OPC Gateways connected to TPN Server1 1
Minimum ACE-T Prefetch Anticipation Time for Prefetch communications with 3 seconds
TPN Server
Control Module Execution Periods for which Prefetch is recommended2 5 seconds and slower
Control Module Execution Periods for which Publish/Subscribe (not Prefetch) is 0.5 sec, 1 sec, 2 sec
recommended2
1. One OPC Gateway connection to the local TPN Server is recommended to minimize the number of data access
transactions through TPN Server as compared to having connections from multiple OPC Gateways. The single OPC
Gateway can be used for both prefetch and publish/subscribe communications. The OPC Gateway Subscription Period
should be set as appropriate for publish/subscribe communications, however a 2 second subscription period will allow
for better prefetch performance as compared to a 1 second subscription period.
2. Note 2 - Choice of prefetch or publish/subscribe is configured on each Control Module. Control Modules using
prefetch should only contain peer references to the OPC Gateway connected to TPN Server.

17.2.3 ACE-T control processing


The term “LCN Control Cascade” refers to a Regulatory Control (RegCtl) strategy that utilizes a HiwayOut or
UcnOut function block in the ACE-T for interfacing an Experion RegCtl block to a TPS RegCtl point. The
Level 1 controller RegCtl block is normally in a Data Hiway controller or UCN controller.

ACE-T Control Processing


Maximum Values per second from LCN (includes both reads and writes)1 1200
Maximum Number of group requests per minute processed by TPN Server (read and write 240
together)2
Maximum Number of subscribed parameters to TPN Server from the OPC Gateway 1000
Maximum Number of prefetch parameters requested per every other CEE execution phase 500
(alternate CEE execution phases should have no prefetch parameters requested; odd or even
phases should be used for prefetch)
Maximum Number of prefetch parameters per second from LCN 500 PPS3
Fastest LCN Control Cascade (Execution Period of CM): 5 sec4
Maximum Number of Fast LCN Control Cascades (CM Execution Periods of 5, 10, and 20 120
sec)
Maximum Number of Slow LCN Control Cascades (CM Execution Periods of 30 sec and 120
slower)
Minimum Shedtime for Level 1 controller RegCtl point (in Hiway or UCN controller) of ACE-T CM Execution
LCN Control Cascade Period + 5 sec
Maximum non-Control Cascade Push/Store Request Rate to the LCN (from CAB, Push, and 20-50 PPS5
SCM blocks)
Maximum non-control cascade Push/Store burst to the LCN accommodated (from CAB, 1200 parameters over 4
push, and SCM blocks) seconds - maximum store
completion time of 8
seconds6

389
17 APPENDIX

ACE-T Control Processing


Note 1 - The TPN Server auxiliary diagnostics display provides an on-line measurement that corresponds to this
specification.
Note 2 - See the ACE TPN Server worksheet section for details of how to calculate the number of group requests
processed by TPN Server.
Note 3 - CEE parameters PFREQAVG and PFREQMAX provide the corresponding on-line measurements.
Note 4 - An LCN Control Cascade between ACE-T and a Hiway/UCN controller executing any faster than a 5 sec period
in ACE-T is not realistic for reliable control, given the multiple communication layers in existence between the ACE-T
and the ultimate IO connections to the process.
Note 5 - The limit is 20 PPS when 120 Fast LCN control cascades are present. The limit is 50 PPS when no Fast LCN
control cascades are present. The formula limit = 20 + (30 * ((120 - #FastLcnControlCascades) / 120)) defines the limit for
the number of Fast LCN control cascades between 0 and 120.
Note 6 - It is assumed that the stores are requested at most once per second due to the result of assigned CM/SCM
execution phase (For more information, see the ACE-T TPN server group writes section).

The following configurations and control capacities have been qualified for ACE-T:
120 Fast LCN Control Cascades + 120 Slow LCN Control Cascades + 20 non-Control Cascade LCN stores per
second; 2 OPC Gateways configured.
• OPC Gateways configured for Subscription Periods of 1 sec and 15 sec.
• 120 Fast LCN Control Cascades with 5 sec Execution Period via 1 sec OPC Gateway; Level 1 RegCtl points
Shedtime of 10 secs.
• 60 Slow LCN Control Cascades with 30 sec Execution Period via 15 sec OPC Gateway; Level 1 RegCtl
points Shedtime of 35 secs.
• 60 Slow LCN Control Cascades with 60 sec Execution Period via 15 sec OPC Gateway; Level 1 RegCtl
points Shedtime of 65 secs.
120 Fast LCN Control Cascades + 120 LCN Slow Control Cascades + 20 non-Control Cascades LCN stores per
second; 3 OPC Gateways configure.
• OPC Gateways configured for Subscription Periods of 1 sec, 5 sec, and 30 sec.
• 120 Fast LCN Control Cascades with 5 sec Execution Period via 1 sec OPC Gateway; Level 1 RegCtl points
Shedtime of 10 secs.
• 60 Slow LCN Control Cascades with 30 sec Execution Period via 5 sec OPC Gateway; Level 1 RegCtl
points Shedtime of 35 secs.
• 60 Slow LCN Control Cascades with 60 sec Execution Period via 30 sec OPC Gateway; Level 1 RegCtl
points Shedtime of 65 secs.

CEE hold breath


An ACE-T CEE hold breath is when execution of scheduled function blocks is stopped because peer pre-fetch
data is not available. For ACE-Ts configured within the above specifications, under steady state conditions, hold
breaths do not occur. However, it is possible that hold breaths might happen under certain scenarios that cause
the delivery of data to ACE-T to be delayed.

17.2.4 ACE-T TPN server group writes


The LCNP card of the ACE-T node has a limited number of LCN data access servers available for the TPN
Server to use, which in turn limits the number of group writes to LCN transactions that TPN Server is capable
of.
Users can minimize/optimize the number of TPN Server group writes by the phasing of the ACE-T strategies
(CMs/SCMs) that store data to the LCN and/or lower level TPS components. ACE-T strategies can be phased
across 0-119 half-second execution cycles using the CM/SCM PERIOD, PHASE, PHASEMIN, and
PHASEHOUR configuration parameters. As a minimum, the default value of PHASE (-1) should be overridden
with a specific phase number to avoid the automatic load balancing of CMs/SCMs, which may result in too

390 www.honeywell.com
17 APPENDIX

many prefetch requests in a phase and/or write requests executed every half-second, potentially overloading the
TPN server. For more information about phasing for prefetch and stores, see “Detailed ACE-T Control Strategy
Phasing Guidelines” on page 391.
A major consideration for how many stores to group together is the subsequent impact on the underlying LCN,
HG, NIM, and ultimate data owners. The ACE-T phasing should be set up to achieve an agreeable compromise
between TPN Server capability and the capabilities of the TPS system components.

17.2.5 Detailed ACE-T Control Strategy Phasing Guidelines

CEE Phasing
Optimal ACE-T performance can only be achieved when CEE CM and SCM strategies are properly phased in
the CEE schedule. CMs/SCMs are phased through configuration of the PERIOD, PHASE, PHASEMIN, and
PHASEHOUR parameters.
The following are the important guidelines for CEE phasing.
Prefetch from LCN
• – Spread prefetch parameters across alternate CEE phases.
– Choose odd or even phases to contain no more than 500 prefetch parameters each and the other (even or
odd) to contain no prefetch parameters.
• Stores to LCN
– Consolidate RegCtl cascade stores (using ContinuousControl access level) into the fewest number of
phases practical.
– Consolidate SCM/Push block stores (via Program access level) into the fewest number of phases
practical, preferably different from the phases used for RegCtl cascade stores.
RegCtl cascades (and possibly some other CMs) provide a unique challenge, because they both prefetch from
LCN and store to LCN.
• The phasing guidelines above suggest that these CMs should be both spread out and consolidated at the
same time, which seems like contradictory guidelines. However, both guidelines can be satisfied until the
limit of 300 prefetch parameters per phase is reached.
The following table of example CMs illustrates how the CEE phasing can be accomplished. For just these 5
CMs, phases 0 and 60 contain 30 prefetch parameters, and phase 2 contains 10 prefetch parameters. This
process is continued for all CMs and the number of prefetch parameters is totaled for all phases to check that the
limit of 500 is not exceeded in alternating phases.

PERIOD PHASE PHASEMIN PHASEHO COMMENTS


UR
CM1 5 sec 0 N/A N/A CM executes in phases 0, 10, 20, …, 100,
110. Adds 10 prefetch parameters to these
(10 prefetch
phases.
params)
CM2 30 sec 0 N/A N/A CM executes in phases 0 and 60. Adds 20
prefetch parameters to these phases.
(20 prefetch
params)
CM3 1 min 2 N/A N/A CM executes in phase 2. Adds 10 prefetch
parameters to this phase.
(10 prefetch
params)
CM4 10 min 10 9 N/A CM executes in phase 10 once every 10
minutes. Adds 20 prefetch parameters to
(20 prefetch
this phase.
params)

391
17 APPENDIX

PERIOD PHASE PHASEMIN PHASEHO COMMENTS


UR
CM5 4 hour 62 0 3 CM executes in phase 62 once every 4
hours. Adds 5 prefetch parameters to this
(5 prefetch
phase.
params)

ACE TPN Server worksheet


Usually, OPC Gateway issues write requests to the TPN server following the execution of a CEE phase. CEE
phases are scheduled every 0.5 seconds.
Depending on the type of the writing to the CEE block, the operation may execute with one of the following
two access levels: CONTINOUS CONTROL or PROGRAM (For example, the UCNOUT executes with the
CONTINOUS CONTROL access level and the Push block executes with the PROGRAM access level).
Different access level writes are not combined into the same OPC writing group. Therefore, if a particular phase
writes at both the access levels, this phase generates two separate group writes.
Prefetch must be enabled on a per CM basis for both LCN Control Cascades and other CMs that read from LCN
whose execution period is >= 5 seconds.
For the purpose of ACE CEE, only one OPC gateway must access a TPN Server, and no other clients must
access this TPN Server.

Establish number of DA servers that are available for write


Number of DA servers that are available for writing can be approximated based on number and collection rates
of the OPC gateways connected to the particular TPN server.
Given:
Number of 1 second OPC gateways that are connected to the TPN server = Nread1
Number of 2 second OPC gateways that are connected to the TPN server = Nread2
Are there OPC gateways 5 sec or slower connected to the TPN server? = 1 if yes, 0 if none
Number of DA servers that are available for write:
DAwrite = 6 - Nread1 - Nread2 - 1 (if slow OPC Gateways are present)

Example 1
Three OPC gateways connect to the TPN server, with rates: 2 secs, 5 secs and 10 secs.
DAwrite = 4 ( = 6 - 0 - 1 - 1)

Example 2
Two local and two remote OPC gateways connect to the TPN server; local OPC gateway rates are 2 sec and
5 sec; remote OPC gateway rates are 2 sec and 10 sec.
DAwrite = 3 (= 6 - 0 - 2 - 1 )

Determine total number of (group) writes to LCN during a minute


This value can be approximated by the number of executions of the LCN-writing phases in CEE during a
minute.

392 www.honeywell.com
17 APPENDIX

Attention
An execution phase may be shared among multiple CMs that may also be running at different CM rates. All writes
issued during this phase are combined together and result in a single (or two, if at mixed access levels) group write
requests to the TPN server.

An execution phase may be shared among multiple CMs that may also be running at different CM rates. All
writes issued during this phase are combined together and result in a single (or two, if at mixed access levels)
group write requests to the TPN server.
In the following examples, NW60 denotes number of distinct group writes per minute (= 60 seconds). Number
of particular items in a group is of lesser importance for TPN Server; in the examples below assumed that a
single CM writes to a single parameter.

Example 1
A: 100 cascade CMs running at 5 seconds all CMs are in phase 0.
NW60 = 12 (60 secs/5 secs) Phase 0 executes every 5 seconds, writing group of 100 items 12 times every
minute.
B: 100 cascade CMs running at 5 seconds of which 50 CMs are in phase 0, and 50 CMS are in phase 6.
NW60 = 24 ( 60/5 + 60/5, for each writing phase) .
Phases 0 and 6 execute once every 5 secs, each writing group of 50 items 12 times per minute.
C: 40 cascade CMs running at 5 seconds CMs have default phase assignment of -1.
NW60 = 120 (60/0.5)
Since CMs are split evenly among phases (4 CMs per phase, because there are 10 distinct phases in the 5 sec
CM) , every 0.5 sec phase will generate a write of a group containing 4 items , resulting in total 120 group
writes per minute.

Example 2
A: 100 cascade CMs running at 5 seconds of which 50 CMs are in phase 0, and 50 CMs are in phase 6.
NW60 = 24 ( 60/5 + 60/5, for each writing phase)
100 pushblock CMs running at 5 sec of which 50 CMs are in phase 0, and 50 CMs are in phase 6.
NW60 = 24 ( 60/5 + 60/5, for each writing phase) <counted separately because different access level than
cascade>.
100 cascade CMs running at 15 seconds of which 50 CMs are in phase 2, and 50 CMs are in phase 12
NW60 = 8 ( 60/15 + 60/15, for each writing phase)
100 cascade & pushblock CMs running at 30 seconds of which 50 CMs are in phase 4, and 50 CMs are in
phase 14
NW60 = 8 ( 60/30 + 60/30, for each writing phase; *2 access levels)
For A: total # of group writes per minute NW60 = 24+24+8 +8 = 64
B: All CMs as in case A, and additionally:10 pushblock CMs running at 2 sec (using dedicated 1 sec OPC
gateway) CMs have default phase assignment ( so that every .5 sec phase will generate a write).
NW60 = 120 ( 60/0.5)
For B: total # of group writes per minute NW60 = 64 ( case A) + 120 = 184

393
17 APPENDIX

Verify TPN server writing throughput


Number of group writes per minute must fit into the available DA server capability.
Given the number of DA servers that are available for write, the following condition must be met:
Number of writes < number of DA servers * DA server write throughput
Or, based on the values determined above:
NW60 < DAwrite * 60/ Tw
NW60 is total number of group writes to the TPN per minute step 2)
DAwrite is the number of DA servers available for write (step 1)
60/ Tw is a DA server write throughput per minute. As observed in testing, majority of group writes issued from
ACE, on medium size groups, fall between 0.5 - 1.5 secs. Therefore, will assume Tw secs = 1.5 and the single
DA server write throughput is 60/1.5 = 40.
For the example 2A in step 2:
NW60 = 64
DAwrite = 4 (assuming 2 OPC gateways are present - 2 sec and 5 sec) and the total TPN server throughput is
OK
64 < 160 ( = 4 * 40)
For the example 2B in step 2:
NW60 = 184
DAwrite = 3 (assuming 3 OPC gateways are present - 1 sec, 2 sec and 5 sec) and the total TPN server
throughput is not OK
184 > 120 ( = 3 * 40)
Here TPN server may not be able to maintain required write frequencies . The recommendation would be to
decrease the number of OPC gateways and/or implement phasing for the fast pushblock CMs.

17.2.6 TPN server data access transactions


TPN server reads and writes to LCN using groups of items. The allocation of particular LCN point parameters
(items) into groups is controlled by the data access clients of the TPN server and by the HCI periodic
collections, for subscribed data.

394 www.honeywell.com
17 APPENDIX

LCNP has fixed number (6) of data access DA servers. If total time to execute a single data access transaction
(group read or write) through the TPN Server is Trw secs, TPN server will support total N60 transactions per
minute:
N60 = 6 * 60/ Tda
Assuming Tda = 1.5 secs, TPN server can service max N60 = 6* 60/1.5 = 240 group requests per minute.
In reality, time to perform group read or write will vary depending on current conditions on the LCN, data
owner busy conditions, large groups accessing multiple data owners and so on.
The value Tda = 1.5 second that is given above would represent the high limit of the average data access time.
Most of data access requests execute in well under 1.5 seconds. Under certain conditions, some data access
times may take longer.
During pending multiple concurrent read/write requests, totaling more than 6, some of the requests will be
queued waiting for the next available data access DA server. The time to service such requests may increase
significantly by the amount of time needed to empty the queue (i.e. to service earlier requests). To assure
predictable behavior of the write requests, care should be taken to limit number of concurrent requests that may
be pending. In case of ACE, this can be achieved by scheduling the LCN-writing CMs to execute only on
selected CEE phases.

Attention
• Groups larger than 1000 items are split internally within TPN Server into multiple groups of max 1000 items each,
serviced in parallel (and consuming multiple DA servers).
• Single item writes are performed fastest (< 0.5 sec) due to optimized data access path.
• For small (number of items > 1) and medium sized groups, the time to perform a read or write, for practical
reasons, can be considered independent on the size of the group.
• On the LCN, writes to a particular data owner (such as Hiway gateway) are performed in groups of max 200 items.
A single DA server can service multiple requests 200 items each simultaneously.

395
17 APPENDIX

17.3 Dspprime description and syntax


The dspprime utility extracts point parameter references from HMIWeb displays or from a user supplied text
file. It uses this data to create point parameter structures in Experion representing data from a device specific
server that supports point parameter discovery (for example, TPS). The utility also primes the cache in the
device specific server if applicable (for example, TPN Server). This facilitates fast initial call-up of displays
with discovered point parameter data.

Attention
With Experion R400.1 and later, the autopriming option is available on ES-T, ESVT and ACE-T nodes. Autoprime
removes the need for local manual priming. For more information, see “Automatic priming of TPS points on
Experion”.

17.3.1 Syntax
You can run Dspprime in one of two modes:
• Prime based on a set of displays:
dspprime [-d display.htm] [-m modhours] [-p path] [-v n] [-r] [-fp] [-pd] [-validate] [-fragdelay n] [-fragsize n]
• Prime based on a file with a list of point parameters:
dspprime -f primefile.txt [-v n] [-r] [-fp] [-pd] [-validate] [-fragdelay n] [-fragsize n]

17.3.2 Dspprime argument description

Argument Description
None Extract all point parameter references from displays in the displays search path. Use these references to
create point parameter structures in Experion and, if applicable, cache entries in the device specific server
from which they originate (for example, TPN server cache).
-d display.htm Only prime the single display “display.htm.”
This option supports the use of wildcards (* and ?) to prime displays matching a certain criteria. For
example, the following command would prime all displays starting with the letter a in the c:\displays
directory: dspprime: d c:\displays\a*.htm

396 www.honeywell.com
17 APPENDIX

Argument Description
-f primefile.txt If this option is used, dspprime will not prime displays, but instead will read its list of point parameters to
prime from the “primefile.txt” specified. The format of “primefile.txt” is “point.parameter” or “point
param1 param2 param3 …” on each line, as shown below:
FIC123.PV
FIC123.SP
FIC123.OP
FID207 PV MODE
FIC500.PV
FIC500.NAME
FIC500.EUDESC
FID200 PV SP OP MODE
If you are priming points in order to show the faceplate and/or point detail display, you may want to
consider always priming the PointDetailDisplay parameter. For example,
FIC123 PointDetailDisplay PV OP SP
FIC500 PointDetailDisplay
FID207 PointDetailDisplay PV
If this option is used, the options related to priming displays will be ignored (i.e. -d, -m, -p).
-fp For each point found on a display or in the primefile, also prime the parameters of the point required to
call up the faceplate. Only the standard faceplates delivered with Experion will be primed. If you have
some displays that use the “Popup” behavior on alphanumerics, the popup file will not be primed by
dspprime. If using this option with TPS points, you must turn off the “Use classic faceplates” option on
the TPS configuration page in Experion.
Dspprime will read the PointDetailDisplay parameter of each point to figure out the name of the faceplate
to prime. It will then read the faceplate display file to determine the list of parameters that need to be
primed for this point and prime these.
-fragdelay n The delay in milliseconds between each request to the TPN server. Default is 1000 milliseconds.
-fragsize n The maximum number of point.parameter items to ask the TPN server for in a single request. Default is
50.
-m modhours Only prime displays that were modified in the last “modhours” hours. Replace “modhours” with the
number of hours
-p path Directory to search. Use multiple -p for multiple directories. If not specified, the directories configured in
the displays search path will be searched. The displays search path can be configured in the Experion
Server Configuration Panel.
-pd For each point found on a display or in the primefile, also prime the parameters of the point required to
call up the point detail display. Note that if a point detail display consists of tabs that each call up a
different display file, this option will only prime the parameters on the display file that is initially called
up when executing a point detail command. If using this option with TPS points, you must turn off the
“Use classic faceplates” option on the TPS configuration page in Experion.
Dspprime will read the PointDetailDisplay parameter of each point to figure out the name of the point
detail display to prime. It will then read the point detail display file to determine the list of parameters
that need to be primed for this point and prime these.
-r Also perform a read of each point parameter value. Use this option if some points are built in Experion
PKS but are not in the device specific server cache. Note that this option will slow down the priming.
Should not be used for TPS points as this may cause an unnecessary load on the LCN. Dspprime
will always connect directly to the TPN server to prime TPS points and will not cause LCN traffic if it
finds they are already in the TPN server cache. Also perform a read of each point parameter value. Use
this option if some points are built in Experion but are not in the device specific server cache. Note that
this option will slow down the priming.

397
17 APPENDIX

Argument Description
-sd tpsdel.pnt Search the Experion database for TPS points that have been previously discovered but are no longer in
the LCN. Output a list of these points to the “tpsdel.pnt” file. (You can replace “tpsdel.pnt” with another
filename that you want to store the deleted point names in) The “tpsdel.pnt” will have lines similar to the
following:
DEL SRVALIAS:TPSPNT1
DEL SRVALIAS:TPSPNT2
DEL SRVALIAS:TPSPNT3
After dspprime has created the “tpsdel.pnt” file, it can be used to delete the TPS points it found by
running: pntbld tpsdel.pnt -del.
These commands should be run on the primary ESVT and each ES-T.
If this option is used, the options related to priming will be ignored (i.e. -d, -m, -p, -f).
-tpnsrvonly Only prime the TPN Server. Do not prime Experion.
Used to move points in the LCN (for example, to a different unit) and not lose how those points are
already configured in Experion (for example, history, groups, trends, and so on.).
-validate Force a revalidate of points to ensure they are built in the correct asset.
-v n Verbose output. Replace n with one of the following values:
0 lists files containing errors (default)
1 lists all files processed
2 lists all files and points processed
3 lists all files, points and parameters processed

398 www.honeywell.com
17 APPENDIX

17.4 TPN interface channels


TPN interface channels are the resource for accessing data, alarms, and files from the TPN. A maximum
number of these channels can be allocated on any given TPS node connected to the TPN. The following table
gives the ranges and recommended defaults for the software components that use TPN interface channels (these
are configurable for some components). Only software components that have ranges are configurable. Ensure
that the maximum channels are not exceeded on any given node.

Software Components Range


TPN Interface Channels (32 Max)
ESVT APP ACE ES-T
Reserved 3 3 3 3
TPN Server * 1-29 1-29 1-29 1-15
CL/NT Application Server NA 2 NA NA
Synchronize Windows NT time using NA NA NA NA
TPN time,
GUS LCN File Service, GUS Alarm
Summary1,
TPSDDE Server
File Transfer2 3 3 3 3
HOPC3 NA NA NA 14
TPN RDI for PHD NA 1-29 NA NA
1 per RDI
TPN Journaling to PHD NA 1 NA NA
Classic TPN Faceplates/Group Display4 NA NA NA NA
TPN Communications Service 1 1 1 1
GUS Remote Displays Server5 NA NA NA 17
Other TPS System Applications See App Spec and See App Spec NA See App Spec and
Tech document and Tech Tech document
document
OM&S Series 50 User Interface (does NA NA NA 5-6
not include GUS Display usage)
BPC Application Server (dedicated App NA 10-12 NA NA
Server)
PFM Application Server (dedicated App NA 10-12 NA NA
Server)

*Defaults per node type. Eleven channels are recommended on the ES-T nodes. Out of the 11 channels on the
ES-T, 1 channel is fixed and the other channels are configurable (installation default = 10).
1The GUS Alarm Summary is not supported on Experion nodes.
2Optional application.
30 channels if GUS Remote Displays Server is enabled.
4These are included in HOPC and GUS Remote Displays Server totals.
5GUS Remote Displays Server is available on the ES-T nodes only. It has a maximum of 17 channels and
depends on number of external GUS Remote Display clients connected per formula: Total = 8 + n*3 (n = 0, 1,
2, 3) where n = number of external clients.

399
17 APPENDIX

Example channel calculation: An ES-T supports GUS Remote Displays and 2 GUS Remote Display clients and
File Transfer. It will use 31 channels based on ((8 + 2x3 remote displays) + 11 recommended for TPN Server +
3 File Transfer + 3 Reserved).

400 www.honeywell.com
18 Notices

Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of Honeywell
International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.

Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intention
of trademark infringement.

Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The third party
materials may be subject to licenses, notices, restrictions and obligations imposed by the licensor. The licenses,
notices, restrictions and obligations, if any, may be found in the materials accompanying the product, in the
documents or files accompanying such third party materials, in a file named third_party_licenses on the media
containing the product, or at http://www.honeywell.com/ps/thirdpartylicenses.

401
18 NOTICES

18.1 Documentation feedback


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

402 www.honeywell.com
18 NOTICES

18.2 How to report a security vulnerability


For the purpose of submission, a security vulnerability is defined as a software defect or weakness that can be
exploited to reduce the operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services.
To report a potential security vulnerability against any Honeywell product, please follow the instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:
• Send an email to security@honeywell.com.
or
• Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical
Assistance Center (TAC) listed in the “Support and other contacts” section of this document.

403
18 NOTICES

18.3 Support and other contacts


For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC).

North America
Country Phone Facsimile Email
Canada and United States 800-822-7673 973-455-5000 askssc@honeywell.com

Northern Europe
Country Local Time Phone Facsimile Email
Business
Hours
Denmark 07:00 – 18:00 80–252165 +45 6980 2349 hpscustomersupport@honeywell.com
Finland 08:00 – 19:00 0800–9–15938 +358 (0)9 2319 4396 hpscustomersupport@honeywell.com
Ireland 06:00 – 17:00 1800939488 +353 (0)1 686 4905 hpscustomersupport@honeywell.com
Netherlands 07:00 – 18:00 0800 020 3498 +31 (0)20 524 1609 hpscustomersupport@honeywell.com
Norway 07:00 – 18:00 800–11478 47–852–287–16 hpscustomersupport@honeywell.com
Sweden 07:00 – 18:00 0200883167 +46 (0)8 509 097 84 hpscustomersupport@honeywell.com
United 06:00 – 17:00 08002797226 +44 (0)20 3031 1064 hpscustomersupport@honeywell.com
Kingdom

Southern Europe
Country Local Time Phone Facsimile Email
Business
Hours
Belgium 07:00 – 18:00 080048580 +32 (0)2 791 96 02 hpscustomersupport@honeywell.com
France 07:00 – 18:00 0805100041 +33 (0)1 72 74 33 44 hpscustomersupport@honeywell.com
Luxembourg 07:00 – 18:00 8002–8524 +352 24611292 hpscustomersupport@honeywell.com
Spain 07:00 – 18:00 800099804 +34 91 791 56 25 hpscustomersupport@honeywell.com
Portugal 06:00 – 17:00 800–8–55994 +34 91 791 56 25 hpscustomersupport@honeywell.com

Eastern Europe
Country Local Time Phone Facsimile Email
Business
Hours
Bulgaria 08:00 – 19:00 700 20771 +359 (0)2 489 7384 hpscustomersupport@honeywell.com
Croatia 07:00 – 18:00 0800 80 6392 +420 227 204 957 hpscustomersupport@honeywell.com
Czech 07:00 – 18:00 800 142 784 +420 227 204 957 hpscustomersupport@honeywell.com
Republic
Hungary 07:00 – 18:00 06 800 20 699 +36 (06) 1 577 7371 hpscustomersupport@honeywell.com
Poland 07:00 – 18:00 00 800 121 50 46 +48 22 485 35 10 hpscustomersupport@honeywell.com
Romania 08:00 – 19:00 0 800 800 178 +40 (0)31 710 7590 hpscustomersupport@honeywell.com
Russia 09:00 – 20:00 8.10.80 02-412 50 11 +7 495 796 98 94 hpscustomersupport@honeywell.com
Federation

404 www.honeywell.com
18 NOTICES

Country Local Time Phone Facsimile Email


Business
Hours
Slovakia 07:00 – 18:00 0800 002 340 +421 (0)2 3301 0376 hpscustomersupport@honeywell.com

Central Europe
Country Local Time Phone Facsimile Email
Business
Hours
Austria 07:00 – 18:00 0800 006438 +43 (0)1 253 6722 hpscustomersupport@honeywell.com
4904
Germany 07:00 – 18:00 0800 7239098 +49 (0)30 6908 8463 hpscustomersupport@honeywell.com
Greece 08:00 – 19:00 00800 12 9493 +30 21 1 268 6973 hpscustomersupport@honeywell.com
Israel 08:00 – 19:00 1 809 407 309 +972 (0)2 591 6148 hpscustomersupport@honeywell.com
Italy 07:00 – 18:00 8000 35205 +39 06 96681356 hpscustomersupport@honeywell.com
Switzerland 07:00 – 18:00 00 080 035 +41 (0)31 560 41 60 hpscustomersupport@honeywell.com

Middle East and South Africa


Country Local Time Business Hours Phone Email
Bahrain 08:00 – 19:00 8008 1343 hpscustomersupport@honeywell.com
Oman 08:00 – 19:00 8007 7595 hpscustomersupport@honeywell.com
Qatar 08:00 – 19:00 800 5460 hpscustomersupport@honeywell.com
Saudi Arabia 08:00 – 19:00 800 844 5309 hpscustomersupport@honeywell.com
South Africa 07:00 – 18:00 0800 983 634 hpscustomersupport@honeywell.com
Turkey 08:00 – 19:00 00800 448823587 hpscustomersupport@honeywell.com
United Arab 09:00 – 20:00 8000 444 0300 hpscustomersupport@honeywell.com
Emirates

Other regions
In other regions, contact your local Honeywell Technical Assistance Center (TAC) for support.
Region Phone Facsimile Email
Pacific 1300-364-822 (toll free +61-8-9362-9564 GTAC@honeywell.com
within Australia)
+61-8-9362-9559 (outside
Australia)
India +91-20-6603-2718 / 19 +91-20-6603-9800 Global-TAC-India@honeywell.com
1800-233-5051
Korea +82-80-782-2255 (toll free +82-2-792-9015 Global-TAC-Korea@honeywell.com
within Korea)
People’s Republic +86-21-2219-6888 Global-TAC-China@honeywell.com
of China
800-820-0237
400-820-0386
Singapore +65-6823-2215 +65-6445-3033 GTAC-SEA@honeywell.com
Japan +81-3-6730-7228 Global-TAC-
JapanJA25@honeywell.com

405
18 NOTICES

World Wide Web


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

Elsewhere
Contact your nearest Honeywell office.

406 www.honeywell.com
18 NOTICES

18.4 Training classes


Honeywell holds technical training classes on Experion PKS. These classes are taught by experts in the field of
process control systems. For more information about these classes, contact your Honeywell representative, or
see http://www.automationcollege.com.

407
18 NOTICES

408 www.honeywell.com