Professional Documents
Culture Documents
Experion
EP-DSX223
R110
12/02
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell International
Industry Solutions
16404 North Black Canyon Hiway
Phoenix, AZ 85053
1-800 343-0228
References
The following list identifies all documents that may be sources of reference for material discussed
in this publication.
Contacts
World Wide Web
The following Honeywell web sites may be of interest to Industry Solution customers.
Corporate http://www.honeywell.com
International http://content.honeywell.com/global/
Telephone
Contact us by telephone at the numbers listed below.
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol Definition
TIP: Identifies advice or hints for the user, often in terms of performing a task.
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 to
properly operate the process.
CAUTION symbol on the equipment refers the user to the product manual for
additional information. The symbol appears next to required information in the
manual.
WARNING symbol on the equipment refers the user to the product manual
for additional information. The symbol appears next to required information in
the manual.
Contents
Contents
Contents
Figures
Figure 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
Tables
Table 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
Contents
REFERENCE - INTERNAL
For information describing the integration of the Experion PKS server with a
TPN 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 Server
User’s Guide.
2. Integration Preconditions
2. Integration Preconditions
2.2. Implementing an Integration Node as a TPS Node
REFERENCE - INTERNAL
For information describing how to implement the Integration Node, refer to
Section 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 the
TPS System Implementation Guide.
REFERENCE - INTERNAL
For information describing how to implement a domain controller, refer to
Section 2.2 New Domain Controller Implementation Checklist in the TP08W
TPS System Implementation Guide.
When this connection has not been established (that is, the node’s personality is not
loaded), 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 Server
transitions 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.
2. Integration Preconditions
2.4. Installing the R630.2 Release of TPN Software
REFERENCE - INTERNAL
For more information about installing a release, refer to the New TPS Node
Implementation Checklist in the TPS System Implementation Guide .
2. Integration Preconditions
2.5. Copying OPC_AE Load Module to History Module
ATTENTION
For Integration Node configuration, follow the steps for APP node
configuration. Refer to the section Getting Started in the TPS System
Implementation Guide then return to this procedure.
Step Action
UNPT NET>&CUS>OPC_AE.LO
2. Integration Preconditions
2.6. Installing the Honeywell Systems Integration Package
Step Action
1 Install the Microsoft Redistributable Libraries from the TPS System Software
Installation CD.
2 Select TPS Application Software Packages from the TPS System Software
Installation CD.
3 Review the information about installing software, license agreements, and
third party compatibility on the next several screens. Click Next to continue.
2. Integration Preconditions
2.6. Installing the Honeywell Systems Integration Package
Step Action
4 Enter the license and authorization numbers. Click Next to continue.
Note: If Honeywell Systems Integration Pack does not appear, verify that the
licensing and authorization numbers are correct.
6
2. Integration Preconditions
2.6. Installing the Honeywell Systems Integration Package
Step Action
7 Verify that these are the components you wish to install. The TPN DAE
Server component provides the alarm and event capability. Click OK .
2. Integration Preconditions
2.7. Configuring the Integration Node to Receive Alarm and Events
2. Integration Preconditions
2.7. Configuring the Integration Node to Receive Alarm and Events
Ap plic ation Mod ule (AM) po in t proces sing and CL not allow ed
ATTENTION
Due to the critical nature of alarms, an Integration Node is not allowed to have
any AM points, point processing, or CL/AM deployments. The reason for this
restriction is that the Integration Node’s dedicated purpose is to integrate TPS
with an Experion PKS system.
2. Integration Preconditions
2.8. Adding Accounts to the Nodes
ATTENTION
For information describing how to add these accounts, refer to the Experion
PKS TPS Integration Guide.
REFERENCE - INTERNAL
For information describing how to configure the TPN Server as an HCI
component, refer to the section Configuring the TPN Server in the TPN
Server User’s Guide.
2. Integration Preconditions
2.10. Configuring TPN Server from a System Management Display
2. Integration Preconditions
2.10. Configuring TPN Server from a System Management Display
2. Integration Preconditions
2.10. Configuring TPN Server from a System Management Display
Configure the TPN Server as an HCI Refer to the section Configuring the TPN
component Server in the TPN Server User’s Guide.
Start or stop the TPN server Refer to the section Monitoring TPN
Server Statusin the TPN Server User’s
Guide
Use the TPN Server’s Auxiliary Status Refer to the section Auxiliary Status
Display Display - TPN Server in the TPN Server
User’s Guide.
2. Integration Preconditio ns
2.10. Configuring TPN Server from a System Management Display
ATTENTION
When a TPN Server is configured to provide Alarm and Events in addition to
Data Access, it can only be installed on an Integration Node. TPN Servers
supporting only Data Access can be installed on either GUS or APP nodes.
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 PKS
clients.
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.
Source A process point also known as tag or entity. On the TPN, a point is a
collection of parameters and sometimes algorithms associated with
those parameters. A point has a 1 to 16-character name that is
sometimes prefixed with a 2- character network name and a 1-
character delimiter. It has an associated handle. Some points have
parameters that set alarm limits, priorities, and behaviors. Violations of
these alarm limits trigger TPN process event behaviors.
Area A process unit approximates the definition of an OPC area. The TPN
has 102 units. On the TPN, a unit has a 2-character name and an
associated handle. This unit handle is simply the index of the unit
name in the TPN unit name table. This index is included as one of the
fields of the process point handle. The customer sets the unit names
and their descriptions when they configure the TPN and by choosing
the unit name order and placement, the unit ‘handle’ is set by default.
Two units are preset and reserved, the null unit named ‘—‘ with an
ordinal of zero. And, the system unit named ‘SY’ with and ordinal of
101. 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 fixed
to the unit that contains the point that is experiencing the event. Events
not associated with a point, such as a node failure, are associated with
the system unit.
Event Although the TPN has events that relate to the OPC definition of Event
Category Category, the TPN does not organize them in the way OPC envisions.
(for The organizational relationship is provided in Windows by the Device
example, Specific Server (DSS) using a cross-reference.
deviation)
Event Although the TPN has parameters that relate to the OPC definition of
Attributes Event Attributes, the TPN does not organize them in the way OPC
(associated envisions. The organizational relationship is provided in Windows by
with an the Device Specific Server (DSS) using a cross-reference.
event
category)
Active/ The OPC definition of an “active” alarm approximates the TPN concept
inactive of a point that is currently experiencing an alarm condition. While the
conditions OPC definition of an “inactive” alarm approximates to the TPN concept
of a point that is not currently experiencing an alarm or a point that has
returned to normal.
Confirmable CONFIRMABLEMESSAGE
Message
Acknowledgement ACKNOWLEDGEMENT
System SYSTEM CONFIGURATION
Configuration
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 to
1000. The TPN Server maps the TPN alarm priorities to OPC alarm priorities using a
cross-reference table.
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 not
OPC 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 points
whose Alarm Enable State, ALENBST, parameter is set to disabled.
Honeywell International
Industry Solutions
2500 West Union Hills Drive
Phoenix, AZ 85027