ep-dsx223-210 system integration overview and planning guide
DESCRIPTION
Honeywell Experion PKSTRANSCRIPT
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 1/38
Experion
System Integration Overview and
Planning Guide
EP-DSX223
R110
12/02
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 2/38
ii System Integration Overview and Planning Guide R110Honeywell 12/02
Notices and Trademarks
Copyright 2002 by Honeywell International Inc.Release 110 December 12, 2002
While this information is presented in good faith and believed to be accurate, Honeywell disclaimsthe implied warranties of merchantability and fitness for a particular purpose and makes noexpress warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. Theinformation and specifications in this document are subject to change without notice.
Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of HoneywellInternational Inc.
Other brand or product names are trademarks of their respective owners.
Honeywell International
Industry Solutions
16404 North Black Canyon Hiway
Phoenix, AZ 85053
1-800 343-0228
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 3/38
R110 System Integration Overview and Planning Guide iii12/02 Honeywell
About This Document
This document describes system integration,TPN server alarm and event architecture, and
mapping of TPN alarms to Experion PKS.
Release Information
Document Name DocumentID
ReleaseNumber
PublicationDate
System Integration Overview and Planning Guide- EX21
EP-DSX223 110 12/02
References
The following list identifies all documents that may be sources of reference for material discussed
in this publication.
Document Title Doc ID
TPN Server User’s Guide TP11W
System Management Configuration Guide EX08
System Management Operations Guide EX07
TPS System Implementation Guide TP10W
TPS System Configuration Utilities User’s Guide TP20
TPS System Administration Guide TP06W
TPS Integration Guide
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 4/38
iv System Integration Overview and Planning Guide R110Honeywell 12/02
Contacts
World Wide Web
The following Honeywell web sites may be of interest to Industry Solution customers.
Honeywell Organization WWW Address (URL)
Corporate http://www.honeywell.com
Industry Solutions http://www.acs.honeywell.com
International http://content.honeywell.com/global/
Telephone
Contact us by telephone at the numbers listed below.
Organization Phone Number
United Statesand Canada
Honeywell Inc.Industry Solutions
1-800-343-0228 Sales1-800-525-7439 Service1-800-822-7673 Tech.
Support
Asia Pacific Honeywell Asia Pacific Inc.Hong Kong
(852) 23 31 9133
Europe Honeywell PACEBrussels, Belgium
[32-2] 728-2711
Latin America Honeywell International Inc.Sunrise, Florida U.S.A.
(954) 845-2600
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 5/38
R110 System Integration Overview and Planning Guide v12/02 Honeywell
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol Definition
ATTENTION: Identifies information that requires special consideration.
TIP: Identifies advice or hints for the user, often in terms of performing a task.
REFERENCE -EXTERNAL: Identifies an additional source of informationoutside of the bookset.
REFERENCE - INTERNAL: Identifies an additional source of informationwithin the bookset.
CAUTION Indicates a situation which, if not avoided, may result in equipment or work(data) on the system being damaged or lost, or may result in the inability toproperly operate the process.
CAUTION: Indicates a potentially hazardous situation, which if not avoided,
may result in minor or moderate injury. It may also be used to alert againstunsafe practices.
CAUTION symbol on the equipment refers the user to the product manual foradditional information. The symbol appears next to required information in themanual.
WARNING: Indicates a potentially hazardous situation, which if not avoided,could result in serious injury or death.
WARNING symbol on the equipment refers the user to the product manualfor additional information. The symbol appears next to required information inthe manual.
WARNING, Risk of electrical shock: Potential shock hazard where
HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or 60 VDCmay be accessible.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 6/38
vi System Integration Overview and Planning Guide R110Honeywell 12/02
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 7/38
R110 System Integration Overview and Planning Guide vii12/02 Honeywell
Contents
1. Introduction to System Integration ................................................11
1.1 What does System Integration Represent? ....................................................11 Introduction ..........................................................................................................................11 What is an Integration Node?...............................................................................................11 Experion PKS viewing of TPS alarms ..................................................................................11
Experion PKS viewing of TPS data ......................................................................................12 What this document describes .............................................................................................12 What does an Integration Node require? .............................................................................13
2. Integration Preconditions ..............................................................15
2.1 Precondition Summary.................................................................................... 15 Summary of preconditions....................................................................................................15
2.2 Implementing an Integration Node as a TPS Node ........................................ 16 Implement Integration Node using new TPS node procedures ............................................16
2.3 Connectivity to the TPS Network through an Integration Node ...................... 16 Connectivity requires using an Integration Node..................................................................16
2.4 Installing the R630.2 Release of TPN Software.............................................. 17 R630.2 or later release required...........................................................................................17
2.5 Copying OPC_AE Load Module to History Module ........................................ 18 OPC_AE module required in the Integration Node...............................................................18 Procedure to copy OPC_AE to History Module....................................................................18
2.6 Installing the Honeywell Systems Integration Package ..................................19 System Integration Package installation procedure .............................................................19
2.7 Configuring the Integration Node to Receive Alarm and Events .................... 22 Network Configuration File (NCF) requires several load modules........................................22 Restart TPN Server after online NCF change ......................................................................23
Application Module (AM) point processing and CL not allowed............................................23 Load only the APP personality to an Integration Node.........................................................23
2.8 Adding Accounts to the Nodes........................................................................24 Add Experion PKS Server and Integration node accounts...................................................24
2.9 Implementing a TPN Server............................................................................ 24 Prerequisite user skills .........................................................................................................24
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 8/38
Contents
viii System Integration Overview and Planning Guide R110Honeywell 12/02
2.10 Configuring TPN Server from a System Management Display....................25 Accessing a TPN Server’s configuration ............................................................................. 25 Viewing additional TPN Server information ......................................................................... 26
Additional references........................................................................................................... 27
3. TPN Server - Alarm and Event Architecture................................. 29
3.1 Architecture Overview......................................................................................29 TPN Server supporting alarm and events installed only on Integration Node ..................... 29 TPN Server as HCI Event server......................................................................................... 29 Delivery of events approach................................................................................................ 29
3.2 Applying Experion PKS Terminology to the TPN ............................................30 Correlation of OPC and TPN terms..................................................................................... 30
4. Mapping TPN Events to Experion PKS ........................................ 33
4.1 Event types, Event categories, and Conditions...............................................33 Background......................................................................................................................... 33 Priorities .............................................................................................................................. 34
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 9/38
Contents
R110 System Integration Overview and Planning Guide ix12/02 Honeywell
FiguresFigure 1-1 Viewing TPS Alarms ....................................................................................11 Figure 1-2 Viewing TPS Data ........................................................................................ 12 Figure 2-1 OPC_AE Added to List of Load Modules.....................................................22 Figure 2-2 System Management Display ...................................................................... 25 Figure 2-3 TPN Server Auxiliary Status Display............................................................ 26
TablesTable 2-1 Additional References ...................................................................................27
Table 3-1 Experion PKS and TPN Terminology Correlation ......................................... 30 Table 4-1 Event Type Mapping ..................................................................................... 33 Table 4-2 Alarm Priority Mapping ..................................................................................34
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 10/38
Contents
x System Integration Overview and Planning Guide R110Honeywell 12/02
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 11/38
R110 System Integration Overview and Planning Guide 1112/02 Honeywell
1. Introduction to System Integration
1.1 What does System Integration Represent?
Introduction
System integration is supported in this release through the use of an Integration Node and
HCI components that allow data to be viewed on TPS and Experion PKS systems.
What is an Integration Node?
An Integration Node allows the TPS and the Experion PKS systems to integrate DataAccess, Alarms, and Events. The node is dedicated to serve the single purpose of
integrating TPS with an Experion PKS Server .
Experion PKS viewing of TPS alarms
Integration as shown in the following figure is supported through the use of an
Integration Node’s TPN Server that publishes HCI alarms to the Experion PKS system.
The Experion PKS system in turn displays the alarms on its HMIWeb stations.
Figure 1-1 Viewing TPS Alarms
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 12/38
1. Introduct ion to System Integration1.1. What does System Integration Represent?
12 System Integration Overview and Planning Guide R110Honeywell 12/02
Experion PKS viewing of TPS data
The same Integration Node publishes HCI data to the Experion PKS system. TheExperion PKS system in turn displays the data on its HMIWeb stations.
Figure 1-2 Viewing TPS Data
What this document describes
This document primarily describes how the Integration Node’s TPN Server providesalarms and data to the Experion PKS system, as shown in Figure 1-1 and Figure 1-2.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 13/38
1. Introduct ion to System Integration1.1. What does System Integration Represent?
R110 System Integration Overview and Planning Guide 1312/02 Honeywell
What does an Integration Node require?
An Integration Node consists of an LCN connected PC loaded with the Honeywell
Systems Integration pack. The PC used can be a server or workstation platform and musthave an LCNP4 or later board operating on TPN Release R630.2 or later. The
Honeywell Systems Integration pack consists of a TPN Server with both Data Access and
Alarm and Events (TPN DAE Server) installed on a node using APP BASE software
provided in the Integration Pack. Additionally, the Experion PKS system requires the
Experion PKS Server TPS Integration Option.
REFERENCE - INTERNAL
For information describing the integration of the Experion PKS server with aTPN system, refer to the Experion PKS document TPS Integration Guide.
For information describing how to provide data access using the TPN Server,refer to the section Accessing TPN Data Using TPN Server in the TPN ServerUser’s Guide.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 14/38
1. Introduct ion to System Integration1.1. What does System Integration Represent?
14 System Integration Overview and Planning Guide R110Honeywell 12/02
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 15/38
R110 System Integration Overview and Planning Guide 1512/02 Honeywell
2. Integration Precondit ions
2.1 Precondition Summary
Summary of preconditions
Integrating TPN alarm and events with Experion PKS clients requires the following:
• Implementing an Integration Node as a TPS node
• Connectivity to the TPS Network through an Integration Node
• Installing the R630.2 or later release of TPN software
• Copying the OPC_AE load module to the History Module
• Installing the Honeywell Systems Integration Package
• Configuring the Integration Node to receive alarm and events
• Adding Accounts to Nodes
• Implementing a TPN Server
• Configuring TPN Server from a System Management Display
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 16/38
2. Integration Preconditions2.2. Implementing an Integration Node as a TPS Node
16 System Integration Overview and Planning Guide R110Honeywell 12/02
2.2 Implementing an Integration Node as a TPS Node
Implement Integration Node us ing new TPS node procedures
You initially implement an Integration Node using the TPS node procedures for an APP(Application Processing Platform) node as described in the TP08W TPS System
Implementation Guide.
REFERENCE - INTERNAL
For information describing how to implement the Integration Node, refer toSection 1 Getting Started and Section 2.3 New TPS Node Implementation
Checklist in the TP08W TPS System Implementation Guide.
Note also that an Integration Node, because it is a specialized APP node, requires a
Windows Domain Controller. If your system requires a domain controller, refer to theTPS System Implementation Guide.
REFERENCE - INTERNAL
For information describing how to implement a domain controller, refer toSection 2.2 New Domain Controller Implementation Checklist in the TP08WTPS System Implementation Guide.
2.3 Connectivity to the TPS Network through anIntegration Node
Connectivity requires using an Integration Node
A connection to the TPS Network is necessary in order for the TPN Server to access theTPS network data. In order for this connection to occur, the APP node representing an
Integration Node must be loaded with an APP personality using a current R630.2 or laterLCN release.
When this connection has not been established (that is, the node’s personality is notloaded), or is broken (for example, its personality failed or its LCNP board is in a reset
state), the TPN Server appears in a warning state where it rejects all requests and client
connections. Upon re-establishing a connection to the TPS Network, the TPN Servertransitions from the warning state to the idle or running state where it allows client
connections and requests. The TPN Server states are viewable from the System
Management Display, as shown in Figure 2-2.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 17/38
2. Integration Preconditions2.4. Installing the R630.2 Release of TPN Software
R110 System Integration Overview and Planning Guide 1712/02 Honeywell
2.4 Installing the R630.2 Release of TPN Software
R630.2 or later release requi red
The TPN Server that supports alarm and events requires installing the current R630.2 orlater release of TPN Software. Refer to the Software Change Notice that accompanies the
software and the TPS System Implementation Guide for installing the software release
into the node. The Integration Node requires amw Personality (PERS_AM) 63.8 or later,and OPC_AE.LO 63.4 or later.
REFERENCE - INTERNAL
For more information about installing a release, refer to the New TPS NodeImplementation Checklist in the TPS System Implementation Guide.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 18/38
2. Integration Preconditions2.5. Copying OPC_AE Load Module to History Module
18 System Integration Overview and Planning Guide R110Honeywell 12/02
2.5 Copying OPC_AE Load Module to History Module
OPC_AE module required in the Integration Node
In order to have the ability to receive TPN alarm and events through the TPN Server, youmust copy the OPC_AE.LO load module to the History Module. This load module is
only for the APP personality and is installed as part of the node’s NCF. Copy the
OPC_AE load module using the TPS System Software CD and referencing &Z12.lcn.
Procedure to copy OPC_AE to History Module
ATTENTIONFor Integration Node configuration, follow the steps for APP nodeconfiguration. Refer to the section Getting Started in the TPS SystemImplementation Guide then return to this procedure.
Step Action
1 Log on to a GUS node as the local Administrator.
2 Insert the TPS System Sof tware CD.
3 Select Programs > Honeywell TPS > Native Window .
4 Select Access > Mount/Dismount Emulated Disks.
5 Mount the following LCN system file found on the TPS System Software CD into the left or the right emulated drive: DISK_&Z12.LCN
6 Select Engineering > Menu.
7 Select the Command Processor target.
8 Copy the load module file from the TPS System Software CD using thefollowing commands (replace "$Fx" with "$F1" for the left emulated drive or"$F2" for the right emulated drive):
UNPT NET>&CUS>OPC_AE.LO
CP $Fx>OPC_AE.LO NET>&CUS>= -D
9Dismount the emulated drive and remove the TPS System Software CD.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 19/38
2. Integration Preconditions2.6. Installing the Honeywell Systems Integration Package
R110 System Integration Overview and Planning Guide 1912/02 Honeywell
2.6 Installing the Honeywell Systems Integration Package
System Integration Package installation procedure
Follow these steps to install the Honeywell System Integration Pack on an Integration Node.
Step Action
1 Install the Microsoft Redistributable Libraries from the TPS System SoftwareInstallation CD.
2 Select TPS Application Software Packages from the TPS System SoftwareInstallation CD.
3 Review the information about installing software, license agreements, andthird party compatibility on the next several screens. Click Next to continue.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 20/38
2. Integration Preconditions2.6. Installing the Honeywell Systems Integration Package
20 System Integration Overview and Planning Guide R110Honeywell 12/02
Step Action
4 Enter the license and authorization numbers. Click Next to continue.
5 Select Honeywell Systems Integration Pack.
Note: If Honeywell Systems Integration Pack does not appear, verify that thelicensing and authorization numbers are correct.
6
Click Install Package.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 21/38
2. Integration Preconditions2.6. Installing the Honeywell Systems Integration Package
R110 System Integration Overview and Planning Guide 2112/02 Honeywell
Step Action
7 Verify that these are the components you wish to install. The TPN DAEServer component provides the alarm and event capability. Click OK.
Result: The installation process occurs.
8 After a successful installation, the screen in the previous step appears. ClickExit and OK to end the installation process.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 22/38
2. Integration Preconditions2.7. Configuring the Integration Node to Receive Alarm and Events
22 System Integration Overview and Planning Guide R110Honeywell 12/02
2.7 Configuring the Integration Node to Receive Alarmand Events
Network Configuration File (NCF) requires several load modules
An NCF for the Integration Node requires the OPC_AE load module in addition to the
standard APP node load modules (AMCL06_2, XACCES, XOPTN). The OPC_AE loadmodule requires that the AMCL06_2, XACCES, and XOPTN load modules appear in the
load module listing before the OPC_AE load module. The OPC_AE load module must
be the last load module configured. The following figure provides an example NCF load
module configuration page.
Figure 2-1 OPC_AE Added to List of Load Modules
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 23/38
2. Integration Preconditions2.7. Configuring the Integration Node to Receive Alarm and Events
R110 System Integration Overview and Planning Guide 2312/02 Honeywell
Restart TPN Server after on line NCF change
If an online NCF change is installed in an Integration Node, any previously configured
TPN Server operating in an Integration Node will need to be stopped in the SystemManagement Display. The Integration Node appears as an APP node; it will need to be
reset and re-loaded from the Native Window’s System Status Display. The TPN Server
can then be re-started once the Integration Node transitions to the OK state and the LCN
node status appears as “APP”.
Appl ication Module (AM) po int processing and CL not allowed
ATTENTION
Due to the critical nature of alarms, an Integration Node is not allowed to haveany AM points, point processing, or CL/AM deployments. The reason for thisrestriction is that the Integration Node’s dedicated purpose is to integrate TPSwith an Experion PKS system.
Load only the APP personality to an Integration Node
CAUTIONWhen a TPN Server is configured to provide Alarm and Events, it canonly be installed on an Integration Node using an APP personality. Ifthe Integration Node configured with an OPC_AE load module isinadvertently loaded with an AM personality, it will cause a warningstate to appear with a status of “Linking Errors”. Resolve this state witha reboot of the node and then reload the APP personality.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 24/38
2. Integration Preconditions2.8. Adding Accounts to the Nodes
24 System Integration Overview and Planning Guide R110Honeywell 12/02
2.8 Adding Accounts to the Nodes
Adding the mngr and the TPSServers callback accounts
It’s necessary to add a mngr account to the Integration Node and the TPSServers callbackaccount to the Experion PKS Server to support the integration of TPS and Experion PKS
systems.
ATTENTION
For information describing how to add these accounts, refer to the ExperionPKS TPS Integration Guide.
2.9 Implementing a TPN Server
Prerequisite user skills
This document assumes that the user is familiar with TPN Server implementation interms of HCI component configuration and accessing TPN data with client applications.
REFERENCE - INTERNAL
For information describing how to configure the TPN Server as an HCIcomponent, refer to the section Configuring the TPN Server in the TPNServer User’s Guide.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 25/38
2. Integration Preconditions2.10. Configuring TPN Server from a System Management Display
R110 System Integration Overview and Planning Guide 2512/02 Honeywell
2.10 Configuring TPN Server from a System ManagementDisplay
Accessing a TPN Server’s conf iguration
The TPN Server is considered an HCI managed component and, as a result, appears in
the System Management Display. From the System Management Display, you canconfigure the TPN Server when you right-click the APP node representing the
Integration Node and select Configure>HCI Component from the context menu that
appears. References for configuring the TPN Server are provided later in this section.
Figure 2-2 System Management Disp lay
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 26/38
2. Integration Preconditions2.10. Configuring TPN Server from a System Management Display
26 System Integration Overview and Planning Guide R110Honeywell 12/02
Viewing additional TPN Server information
The TPN Server provides an Auxiliary Status Display that displays configuration,
performance, and diagnostic information.
Figure 2-3 TPN Server Auxiliary Status Display
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 27/38
2. Integration Preconditions2.10. Configuring TPN Server from a System Management Display
R110 System Integration Overview and Planning Guide 2712/02 Honeywell
Addi tional references
The documents listed in the following table provide additional references for using the
TPN Server from a System Management Display.
Table 2-1 Addit ional References
If you need to … Then …
Configure the TPN Server as an HCIcomponent
Refer to the section Configuring the TPNServer in the TPN Server User’s Guide.
Start or stop the TPN server Refer to the section Monitoring TPNServer Statusin the TPN Server User’sGuide
Manage component operations Refer to the section HCI ManagedComponent Operations in the SystemManagement Operations Guide.
Use the TPN Server’s Auxiliary StatusDisplay
Refer to the section Auxiliary StatusDisplay - TPN Server in the TPN ServerUser’s Guide.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 28/38
2. Integration Preconditions2.10. Configuring TPN Server from a System Management Display
28 System Integration Overview and Planning Guide R110Honeywell 12/02
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 29/38
R110 System Integration Overview and Planning Guide 2912/02 Honeywell
3. TPN Server - Alarm and Event Architecture
3.1 Architecture Overview
TPN Server supporting alarm and events installed only on Integration Node
ATTENTION
When a TPN Server is configured to provide Alarm and Events in addition toData Access, it can only be installed on an Integration Node. TPN Serverssupporting only Data Access can be installed on either GUS or APP nodes.
TPN Server as HCI Event server
When the TPN Server supports alarm and events, it is considered an HCI Event server.This requires an Integration Node to deliver TPN events to the TPN Server on Windows2000. The TPN Server is able to receive events for all configured process units as well as
the system unit on the connected TPN System. Experion PKS clients use OPC
subscription mechanisms to filter event notifications according to their needs.
ATTENTION
When a TPN Server is configured to provide Alarm and Events to Experion
PKS clients, it also can provide Data Access to those same Experion PKSclients.
Delivery of events approach
The OPC_AE.LO load module on the TPN side consumes events from the TPN data
owners. The load module prepares an event packet for the Windows side, decoding the
events from their TPN proprietary format to a form suitable for the Experion PKS clients
on the Windows side.
Once TPN events are available for the Experion PKS clients on the Windows side, the
TPN Server maps the fields of the events into the OnEvent structure as defined by the
HCI specification. The OnEvent structure is then passed to the generic portion of the
server and to Experion PKS subscribed event clients.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 30/38
3. TPN Server - Alarm and Event Architecture3.2. Applying Experion PKS Terminology to the TPN
30 System Integration Overview and Planning Guide R110Honeywell 12/02
3.2 Applying Experion PKS Terminology to the TPN
Correlation of OPC and TPN terms
Experion PKS utilizes OPC conventions in its alarm and event implementation. Thefollowing table correlates OPC and TPN conventions. The OPC specification uses its
specific lexicon to describe events and scenarios relating to events. The TPN also has its
lexicon to describe similar concepts. The following table serves as an approximate cross-reference for terms and synonyms between the two lexicons.
Table 3-1 Experion PKS and TPN Terminology Correlation
OPCLexicon
TPN Lexicon
Source A process point also known as tag or entity. On the TPN, a point is acollection of parameters and sometimes algorithms associated withthose parameters. A point has a 1 to 16-character name that issometimes prefixed with a 2- character network name and a 1-character delimiter. It has an associated handle. Some points haveparameters that set alarm limits, priorities, and behaviors. Violations ofthese alarm limits trigger TPN process event behaviors.
Area A process unit approximates the definition of an OPC area. The TPNhas 102 units. On the TPN, a unit has a 2-character name and anassociated handle. This unit handle is simply the index of the unitname in the TPN unit name table. This index is included as one of thefields of the process point handle. The customer sets the unit namesand their descriptions when they configure the TPN and by choosingthe unit name order and placement, the unit ‘handle’ is set by default.Two units are preset and reserved, the null unit named ‘—‘ with anordinal of zero. And, the system unit named ‘SY’ with and ordinal of101. On the TPN a point can be in one and only one unit. Furthermore,events are always associated with a unit. The unit of an event is fixedto the unit that contains the point that is experiencing the event. Eventsnot associated with a point, such as a node failure, are associated withthe system unit.
EventCategory(forexample,deviation)
Although the TPN has events that relate to the OPC definition of EventCategory, the TPN does not organize them in the way OPC envisions.The organizational relationship is provided in Windows by the DeviceSpecific Server (DSS) using a cross-reference.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 31/38
3. TPN Server - Alarm and Event Architecture3.2. Applying Experion PKS Terminology to the TPN
R110 System Integration Overview and Planning Guide 3112/02 Honeywell
OPCLexicon
TPN Lexicon
Event Attributes(associatedwith aneventcategory)
Although the TPN has parameters that relate to the OPC definition ofEvent Attributes, the TPN does not organize them in the way OPCenvisions. The organizational relationship is provided in Windows bythe Device Specific Server (DSS) using a cross-reference.
Active/inactiveconditions
The OPC definition of an “active” alarm approximates the TPN conceptof a point that is currently experiencing an alarm condition. While theOPC definition of an “inactive” alarm approximates to the TPN concept
of a point that is not currently experiencing an alarm or a point that hasreturned to normal.
Enabled/disabledalarms (bysource orarea)
The OPC definition of an ‘enabled’ alarm (either by source or area)approximates the TPN concept of an enabled alarm. That is, the alarmcondition is reported without restriction when it’s enabled. The OPCconcept of a disabled source maps to the TPN concept of an “inhibited’point. That is, alarm conditions on an inhibited point are completelysuppressed as if the alarm conditions were not even being detected.This is done right at the event ‘data owner’, not as a filter in the alarmreceivers. The OPC concept of a disabled area approximates the TPNconcept of an inhibited unit. When a TPN unit is inhibited, alarms fromall points contained in the unit are suppressed as if they were not evenbeing detected. This has an exception, however. After a unit on theTPN has been set to inhibited, individual points can be set to enabled
(or disabled) thus overriding the unit inhibit on a point by point basis.Overridden points can still send alarms even if the unit is inhibited. Inaddition, the TPN has an additional state coincidentally named‘disabled’. A point whose alarms are disabled continues to reportalarms to the disk history, its alarm parameter indicates that the pointis in alarm, and alarm associated actions (such as Event InitiatedProcessing EIP) continue to take place. Disabled alarms are not sentto monitors or their associated journal printers. A TPN unit can bedisabled also. When a TPN unit has its alarms disabled, alarms fromall points contained in the unit exhibit their disabled behavior. After aTPN unit has been disabled, individual points in the unit can be set toenabled or inhibited thus overriding the unit setting
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 32/38
3. TPN Server - Alarm and Event Architecture3.2. Applying Experion PKS Terminology to the TPN
32 System Integration Overview and Planning Guide R110Honeywell 12/02
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 33/38
33 System Integration Overview and Planning Guide R110Honeywell 12/02
4. Mapping TPN Events to Experion PKS
4.1 Event types, Event categories, and Conditions
Background
The TPN Server using the integration package translates TPN conditions to Experion PKS event
types and Experion PKS event categories. Experion PKS uses the OPC standard for alarm andevent implementation. A summary of this translation is shown in the following table.
Table 4-1 Event Type Mapping
Experion PKSEvent Type
Experion PKSEvent Category
Conditions/Events
ConditionRelated
Process Alarm ABORT, ADVDEV, BADINPUT, BADOC,BADPV, BADCTL, BADSV, CHNGOFST,CLEALM, CLFAIL, CLFALM, CLWARN,CMDDIS, 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
Sequence ofEvents
CHNGOFST, OFFNORM
System Alarm SYSERROR, NODEERROR, NETERROR,NETREDERROR, MANCOMPERROR,SYSCOMPERROR
OPC Server Error DEVCOMMERROR
Message OPERATOR MESSAGE
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 34/38
4. Mapping TPN Events to Experion PKS4.1. Event types, Event categories, and Conditions
34 System Integration Overview and Planning Guide R110Honeywell 12/02
Experion PKSEvent Type
Experion PKSEvent Category
Conditions/Events
ConfirmableMessage
CONFIRMABLEMESSAGE
Simple Device Failure DEVICEFAILURE
Batch Status BATCH STATUS
System Message SYSTEM MESSAGE
Tracking Operator ProcessChange
PROCESS CHANGE
Acknowledgement ACKNOWLEDGEMENT
SystemConfiguration
SYSTEM CONFIGURATION
Advanced Control ADVANCED CONTROL
Priorities
Experion PKS calls for alarm priority levels that are in the range of 0 to 1000. The TPN
has a more limited set of alarm priorities. The OPC standards accommodate this
limitation in a DSS by allowing the DSS to ‘spread’ its priorities over the range of 0 to1000. The TPN Server maps the TPN alarm priorities to OPC alarm priorities using a
cross-reference table.
The following table defines the mapping of alarm priorities.
Table 4-2 Alarm Priority Mapping
TPN Alarm Priori ty OPC Alarm Priori ty
NOACTION NA
JOURNAL 101
LOW 401
HIGH 601
EMERGNCY 801
PRINTER NA
JNLPRINT 301
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 35/38
4. Mapping TPN Events to Experion PKS4.1. Event types, Event categories, and Conditions
R110 System Integration Overview and Planning Guide 3512/02 Honeywell
The destination of a TPN event is not necessarily related to the alarm’s priority although
it often appears as such. For example, if a TPN point is set to disabled (in the TPN notOPC sense of the term), the alarm detector only sends its alarms to the alarm journal.
This is done even if the alarm priority is set to emergency. In that example, an alarm
could be transmitted to the journal with a priority of emergency.
ATTENTION
The Integration Node continues to receive and transmit alarms from pointswhose Alarm Enable State, ALENBST, parameter is set to disabled.
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 36/38
4. Mapping TPN Events to Experion PKS4.1. Event types, Event categories, and Conditions
36 System Integration Overview and Planning Guide R110Honeywell 12/02
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 37/38
7/17/2019 EP-DSX223-210 System Integration Overview and Planning Guide
http://slidepdf.com/reader/full/ep-dsx223-210-system-integration-overview-and-planning-guide 38/38
Honeywell International
Industry Solutions
2500 West Union Hills Drive
Phoenix, AZ 85027