Experion Process Knowledge System (PKS) : Experion Server Specifications and Technical Data
Experion Process Knowledge System (PKS) : Experion Server Specifications and Technical Data
System (PKS)
EP03-200-210
Release R210
Revision Date: May, 2005
Version 1.1
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
-i-
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
OPC Integrator........................................................................................................................ 19
Redirection Manager .............................................................................................................. 20
SCADA Interfaces ...................................................................................................................... 20
Open Data Access ..................................................................................................................... 21
ODBC Driver ........................................................................................................................... 21
Network Server ....................................................................................................................... 22
21 CFR Part 11 .......................................................................................................................... 23
Electronic Signature Option .................................................................................................... 23
Application Enablers................................................................................................................... 23
Batch Reporting ...................................................................................................................... 23
Recipe Management............................................................................................................... 23
Point Control Scheduler.......................................................................................................... 23
Alarm Pager ............................................................................................................................ 23
ODBC Data Exchange............................................................................................................ 24
Application Toolkit ...................................................................................................................... 24
Specifications and Sizing ............................................................................................................... 25
Server PC ................................................................................................................................... 25
Redundancy Performance.......................................................................................................... 26
Database Sizing ......................................................................................................................... 26
History Collection ....................................................................................................................... 27
History Sizing.............................................................................................................................. 28
Real Time Database SCADA Point Structures .......................................................................... 29
Data Access Performance.......................................................................................................... 30
Notification Performance ............................................................................................................ 30
Distributed Systems Architecture ............................................................................................... 31
DSA Publishing Server Communications Performance ......................................................... 31
DSA Subscribing Server Communications Performance ....................................................... 31
Miscellaneous DSA Specifications ......................................................................................... 31
Alarm Pager................................................................................................................................ 32
Model Numbers.............................................................................................................................. 33
Server Hardware ........................................................................................................................ 33
Server Database ........................................................................................................................ 33
Server Redundancy.................................................................................................................... 33
Distributed System Architecture ................................................................................................. 34
Additional Honeywell Device Integration.................................................................................... 34
SCADA Interfaces ...................................................................................................................... 34
Application Enablers................................................................................................................... 35
Application Toolkit ...................................................................................................................... 35
Open Data Access ..................................................................................................................... 35
OPC............................................................................................................................................ 35
Engineering Tools ...................................................................................................................... 35
On-Process Migration................................................................................................................. 35
21 CFR Part 11 Option............................................................................................................... 35
Glossary ......................................................................................................................................... 36
- ii -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Revision History
- iii -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Introduction
.
Figure 1. Experion PKS Overview Architecture Diagram
Architecture Overview
Experion comprises many different integrated hardware and software solutions depending upon
the needs of the installation. Figure 1 is a representation of the many possible nodes that can be
utilized in the flexible and highly scalable Experion architecture.
-4-
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Server Overview
This document describes the specifications For more information about Experion, please
and technical data for the Experion Server refer to:
hardware and software. The Server is a • EP03-100-210 Experion Process
required component of Experion. All the System Overview
functionality described in this document, • EP03-210-210 Experion Station
including the options, are core functionality. Specification and Technical Data
That is, it is developed as a system and • EP-3-300-210 Experion Platform
licensed as options to allow users to simply CEE-based Controller Specifications
purchase what is necessary. and Technical Data
• EP03-310-210 Experion Application
Options can be purchased at any time and Control Environment
added to a system with a simple license key. • EP03-400-210 Experion Chassis
Most options do not even require an I/O Modules - Series A Specification
additional software installation. These and Technical Data
include functions such as: • EP03-410-210 Experion Rail I/O
• Server Redundancy – an on-line Modules - Series A Specification
synchronized backup provides high and Technical Data
availability to your process. • EP03-420-210 Experion
• Distributed Systems Architecture Galvanically Isolated/Intrinsically
(DSA) – DSA brings multiple Safe Rail I/O Modules - Series H
“systems” together in a seamless Specification and Technical Data
manner. • EP03-430-210 Experion PM I/O
• Honeywell System Integration – Specifications and Technical Data
Honeywell Systems such as TDC • EP03-440-210 Experion DeviceNet
2000, TDC 3000, TPS, and FSC are Specification and Technical Data
comprehensively integrated into • EP03-450-210 Experion PROFIBUS
Experion. DP Specification and Technical
• OPC Connectivity Options – the Data
Experion Server can serve data and • EP03-500-210 Honeywell Fault
alarms and events to OPC clients or Tolerant Ethernet Specification and
it can act as a client to other OPC Technical Data
servers.
• SCADA Interfaces –multiple
interfaces to RTUs, PLCs, and other
devices to integrate these devices
into your control system.
• 21 CFR Part 11 Functions –
Experion provides the necessary
functions, such as Electronic
Signature support, for regulated
industries.
• Alarm Pager – send alarms directly
to your maintenance crew’s pagers,
e-mail, and more.
• Open Data Access – Whenever
you need to get Experion data into a
spreadsheet or database, for
example, Open Data Access is
required.
• On-process Migration – migrate
the Server software from a current
release to the next available release
without taking Experion off-line.
-5-
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Executive
Executive Data acquisition and control for
SCADA devices is also handled by
Configuration
Configuration
User Interface
User Interface this subsystem. When points are
downloaded to the server using Quick
Builder, scan tables are built that
define how data will be acquired. The
Redundancy
Real
RealTime
Time Acquisition
Acquisition&&
server polls the devices (RTUs, PLCs,
Redundancy
Database Control
Control etc.) at periodic rates. Depending on
Database the interface, report by exception and
other scanning mechanisms are
supported.
History
History
Report
Report Collection
Collection
Alarm
Alarm&&
Event
Event
-6-
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
-7-
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
-8-
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
consistent definition of all the data in the provide “DCS network” functionality. FTE
plant or mill, ranging from a high-end provides a robust and high availability
business view down to individual points. The network infrastructure for communicating to
enterprise model goes well beyond Experion Stations, C200 controllers, ACE
Distributed Control System capabilities by Nodes, etc. Refer to page 13 for more
providing a unified framework for decision information about FTE. An FTE software
and diagnostic support that is used by license is bundled with the Server base
engineers, operators, and applications. software. FTE hardware can be added to
implement the solution.
Two unique components form the base of
the enterprise model: the asset model and Ethernet
alarm groups. Details of the implementation Experion Servers also support an Ethernet
and use of asset model and alarm groups network to communicate to nodes
are given in the sections below. throughout the system.
Asset Model ControlNet
The asset model represents the hierarchical As an option, ControlNet can be used to
organization of items in the enterprise, for communicate with C200 controllers. For
example process units, individual pieces of more information, please refer to document
equipment or facilities etc. EP03-300-200, Experion Controller
Specification & Technical Data.
The operator navigates and manages the
process from this intuitive hierarchical
representation. Alarms are grouped and Server Scripting
visualized using the asset model and Server Scripting encompasses two features.
similarly, when configuring an operator or The first provides scripting support to allow
station scope of responsibility, the engineer the behavior of the Server-resident
has the ability to manage this from the same subsystems and its run time objects to be
hierarchical representation. extended. Examples of server objects are:
• Server
Assets and the asset model form the core of • Points and Parameters (described in the
the Experion Enterprise Model and replace section titled Point Scripting)
the flat area structure that was available in • Reports
previous releases of Experion. • Assets
• Tasks (Application Programs)
The user configures these scripts to be run
Alarm groups by the server either periodically or when a
The alarm group functionality provides a specified event occurs. In addition, standard
mechanism to aggregate and indicate alarm displays are supplied to allow the user to
status for a disparate collection of points. monitor the status of running scripts.
For example, points contained by several
different assets may be in use on a single Example scenarios of when to use server
graphic. If the operator needs to have this scripts include:
graphic linked to an operator keyboard • Raising an Urgent Alarm when
button, the Alarm Group can be used to Related Points Go into Alarm
represent the LED alarm states for all the • Changing the Ranges of Related
points in use on the graphic. Points
• Checking a Point's Value after It has
Gone into Alarm
Networking • Using Auxiliary Parameters to Store
and Display Data
Fault Tolerant Ethernet • Reading Data from a Text File
• Checking a Value at Regular
Honeywell’s patented Fault Tolerant
Intervals
Ethernet (FTE) network utilizes off-the-shelf
networking hardware to allow Ethernet to
-9-
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 10 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 11 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 12 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Options
Screen Updates
Server Redundancy
The Experion Server is optionally redundant.
The redundancy subsystem provides a high Database
availability platform by enabling a pair of Checkpoints
similarly configured servers to support each
other in a primary/backup fashion. Should Flex
Primary Backup Station
the Primary fail, a fully functioning Backup Server
Server
assumes the Primary role. Primary refers to
the specific server that is actively acquiring
data from the controllers/RTUs and serving
data to the clients. The Primary propagates
all database transactions to the Backup over
a redundant network so that both databases Data Acquisition
remain in complete synchronization.
- 13 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Central
Control
Room
WAN/Plant/
Site A
Site/Inter-plant
Network
Site B Site C
- 14 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 15 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 16 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 17 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 18 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
source OPC Alarm & Event Server into OPC Data Access Server
Experion’s alarm attributes. The OPC Data Access Server functionality
allows OPC Data Access Clients to view
OPC Advanced Data Client Experion Point data for control, plant-wide
The Experion OPC Advanced Data Client is historization, etc.
primarily designed for integrating complex
subsystems, such as distributed control The OPC Data Access specification’s
systems. Such systems typically have point- optional point browse section has been
like structures that are defined as complex implemented, allowing OPC Data Access
data structures. Clients to view the hierarchical
Asset.Point.Parameter structure of the
Experion Server.
OPC items are mapped to OPC advanced
points. OPC advanced points are built in OPC Alarm & Event Server
Configuration Studio and licensed as
SCADA points. The OPC advanced point The OPC Alarm & Event Server is designed
supports creating arbitrary point parameter to expose Experion’s Alarm & Event data in
names to reference OPC items. an open manner to applications that require
this information.
After the OPC advanced points are built,
OPC Integrator
they can be added to trends, custom
displays, group displays, similar to other OPC Integrator is an open method allowing
point types in Experion. bi-directional data transfer between two or
more systems for the purpose of supervisory
monitoring, alarming and control. This type
OPC Display Data Client
of interface is commonly called an OPC
The OPC Display Data Client is standard Double Headed Client.
functionality in Experion and allows the user
to insert OPC Data into a display without the OPC Integrator is valuable in the following
need to build points (the user is not required scenarios:
to purchase points for when accessing OPC
data using this client). This is ideal for data
• A system provides an OPC data
that just needs to be visualized by the
access server, but not an OPC
operator and does not need to be alarmed,
client. The system needs to retrieve
historized, etc. OPC Data that is acquired in
data from Experion.
this fashion supports both reads and writes.
• Experion data needs to be
OPC data items can be added directly to transferred to a third-party OPC
custom displays without having to build server whenever it changes,
points in Configuration Studio. irrespective of the reason for the
change (including when the data is
OPC Client Interface changed by an operator).
• A system includes Experion process
The Experion OPC Client Interface is controllers and needs to transfer
primarily designed to integrate low- data efficiently between those
complexity subsystems, such as PLCs, controllers and some SCADA
RTUs, single loop controllers etc. interfaces at the supervisory control
Configuration involves individually mapping layer.
OPC items to Experion SCADA points
(analog, status and so on). If alarming is
required, configure the associated point's OPC Integrator has many built-in features
alarm properties. to ensure robust communication between
OPC Servers. OPC Integrator supports
This interface should be used whenever redundant Experion Servers and is
there is a requirement for Alarming and therefore itself redundant. OPC Integrator
there is no OPC Alarm & Event Server also supports redundant third party OPC
present. Servers natively. While OPC Integrator
supports redundant OPC Servers natively,
- 19 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 20 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Open Data Access Data Access are the ODBC Driver and the
Whenever another application requires data Network Server.
from the Experion database, Open Data
Access is required. For example, Open ODBC Driver
Data Access is required when: ODBC is a standard set of function calls for
• Reading data into a Microsoft Excel accessing data in a database. These calls
Spreadsheet enable utilizing Structured Query Language
• Running a query on the database (SQL) queries on the database. ODBC can
from Microsoft Access be used in any client/server architecture,
• A user written application is regardless of whether the database and
accessing the database client application are resident on the same
Each is considered a ‘user’ of Open Data computer, separated by a network, or even if
Access. The two main components to Open
- 21 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
they are on different computers using ODBC Client can run on the server or on
different operating systems. any other computer on the network. Figure
8 shows a basic Experion ODBC driver
The ODBC Driver allows the Server configuration.
database to be queried using SQL
commands from ODBC client applications, Network Server
such as Microsoft Access. Additionally, The Network Server provides extremely
custom application written in Visual Basic or efficient, access to the Experion database
C++ can also access the server database for network based applications such as
via the ODBC Driver. The Server database Microsoft Excel Data Exchange and Network
is exposed as a number of read-only ODBC API options.
tables including Points, Event History and • Microsoft Excel Data Exchange
Process History. Driver features include: allows Microsoft Excel to obtain
• Open read-only access to plant real- real-time and historical data from
time and historical data the Experion system. This option
• Throttling to prevent performance provides read and write access to
impact data in one or more Experion
• Redundancy of data storage Databases, providing a powerful
• Fully functional examples for data consolidation and reporting
productivity improvements tool. Wizards for Microsoft Excel
It is optimized for Microsoft Access and are included to help set up the data
other ODBC ad hoc query/report to be collected.
applications. • Applications executing on other
network-connected platforms may
The Experion ODBC driver has two parts: easily access Experion real-time
the ODBC Server and the ODBC Client. data over the network using the
The ODBC Client handles the ODBC call Network API. The API provides
made by a client application and passes it to high-level subroutine calls in Visual
the ODBC Server. The ODBC Server C/C++ or Visual Basic to allow
processes the ODBC calls, queries the read/write access to Experion data
Experion server database and returns the in a networked environment.
information to the client application.
The ODBC Server always runs on the
Experion server computer. The Experion
Data Requested
Data Sent
Data Sent
Data Requested
Experion PKS ODBC Experion PKS ODBC
Experion PKS ODBC Experion PKS ODBC
Client Server
Client Server
Data Sent
- 22 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 23 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 24 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Server PC
A PC must meet the following specifications to be used as an Experion Server. These guidelines
are intended to provide a minimum baseline. Honeywell-supplied platforms will meet these
specifications but may not necessarily be the example platforms listed below. PCs purchased
directly through Honeywell carry full support as a qualified offering.
Minimum System
This is the minimum hardware necessary to run the Experion components. It should be
used for small configurations that may consist of 1 non-redundant Experion Server with 1
Station or 1 Redundant Experion Server pair with 1 Station. The system typically only
includes passive monitoring and occasional report generation from a single screen.
Standard System
Configurations will consist of non-redundant Experion Server and multiple Stations or a
Redundant Experion Server pair with up to 1 DSA Server. A non-redundant Server can
support up 10-12 Stations or a Redundant Server can support 6-8 Stations. This type of
system includes 1 or 2 Stations with a single or dual screen actively monitoring and
occasional report generation.
Performance System
An advanced configuration may consist of a Redundant Experion Server pair, multiple
DSA Servers, and greater than 12 Stations with single, dual, or quad screen
configurations. This system typically includes active monitoring from multiple Stations
and random report generation.
Typical
Minimum Server/eServer/Remote
System Server/eServer Engineering and Station Performance
Configuration Server
Processor Dual 2 GHz Xeon or Dual 2.4 GHz Xeon or Dual 3 GHz Xeon or
Faster Faster Faster
1
RAM 1 GB 2 GB 2 GB
- 25 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Redundancy Performance
The Experion Server redundancy option is an extremely robust and mature subsystem designed
to provide the highest possible availability with the following specifications:
Specification
Checkpoint Period Default setting is 300 seconds (5 minutes)
1
User-defined File Backup Period Default setting is 60 minutes
Note 1 – This is the file backup for user-defined files. This is not to be confused with the automatic synchronizing of
database files between the primary and backup servers.
Database Sizing
The Experion Server database is sized per the following specifications:
Database Item Default Size Maximum Size
1
Point Count 50 → 20,000 Process Points Process Points + SCADA Points ≤
50 → 65,000 SCADA Points 65,000 Points
2
Experion Station – Flex 1 Æ 40 40
Connections
Experion Station – Console 0Æ 10 103
Connections
- 26 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Note 1 – The Experion database can be comprised of a mix of SCADA and Process Points in increments of 100
Points.
Note 2 – When a system includes Process Points, the number of Stations connections may need to be limited to keep
the data access performance within specified limits (see the Data Access Performance table). Servers with
large numbers of Process Points may be limited to supporting a maximum of 20 Station connections.
Note 3 – The total number of Stations connected to one Experion Server is limited to 40. Stations counting toward
this limit include both ES-F, ES-C nodes and ES-CE nodes. Total of ES-C and ES-CE nodes combined
cannot exceed 20. No more than 10 ES-C nodes are supported within the server.
Note 4 – The asset model represents the hierarchical organization of items in the enterprise, for example process
units, individual pieces of equipment or facilities etc. This specification is a limit for a system that could be
comprised of multiple servers.
Note 5 – Assignable assets provide a way to assign assets to an operator's scope of responsibility. An assigned asset
includes all asset children of the assigned asset including any points associated with those assets or any
alarm groups that have been designated by that asset for scope of responsibility purposes.
Note 6 – This specification is a limit for a system that could be comprised of multiple servers.
Note 7 – This is a server limitation only. The actual amount of data that can be retrieved depends on the data source.
History Collection
The on-board history collection system of the Experion server is composed of three history
classes. To support daylight savings and time zones, all collected data is historized in Universal
Coordinate Time (UCT) time stamp.
Fast History • Stores snapshots at regular intervals — called the fast history
interval. This user selected interval can be 1, 2, 3, 4, 5 (default),
10, 15, or 30 second snapshot
- 27 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
History Sizing
The Experion Server history subsystem meets the following specifications:
Maximum
Default Number Maximum Number of
Default Duration of Samples Duration Samples
Standard History
1 minute snapshot 24 hours 1442 69 days 100,000
1
6 minute average 7 days 1682 416 days 100,000
1
1 hour average 1 month 746 11.4 years 100,000
1
8 hour average 3 months 281 91.2 years 100,000
1
24 hour average 1 year 368 273.8 years 100,000
Extended History
1 hour snapshot 3 months 2233 11.4 years 100,000
8 hour snapshot 1 year 1099 91.2 years 100,000
24 hour snapshot 3 years 1831 273.8 years 100,000
2
Fast History
1 second snapshot 2 hours 7262 27.8 hours 100,000
2 second snapshot 4 hours 7262 55.6 hours 100,000
3 second snapshot 6 hours 7262 3.5 days 100,000
4 second snapshot 8 hours 7262 4.6 days 100,000
5 second snapshot 10 hours 7262 5.8 days 100,000
10 second snapshot 20 hours 7262 11.6 days 100,000
15 second snapshot 30 hours 7262 17.4 days 100,000
30 second snapshot 60 hours 7262 34.7 days 100,000
Note 1 – The averages are calculated using the 1-minute base interval. That is, 6-minute averages are calculated on
six 1-minute values.
Note 2 – Only one of the Fast History intervals can be configured per server. The 5-second snapshot is the default
Fast History interval.
- 28 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 29 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Maximum PPS from all ACE nodes (Ethernet and FTE) 2000 PPS
Maximum DSA PPS from each remote DSA Server 1000 PPS
2
Maximum OPC PPS from all configured OPC Servers 1000 PPS
Maximum number of remote OPC Data Access Servers subscribed to by the 15
Experion PKS Server (OPC Data Access Client)
3
Maximum OPC PPS published to all OPC Clients 2000 PPS
Maximum number of remote OPC Data Access Clients supported by the 5
Experion PKS Server (OPC Data Access Server)
OPC Display Data Client: Maximum number of data values per display 40
OPC Display Data Client: Total number of data values per OPC server 1000
2
Notification Performance
The following specifications apply to the Alarm & Event subsystem of the Experion Server:
Specification
1
Maximum number of events (burst condition) 1000 events
Maximum number of sustained events/second 40/sec
2
Maximum number of sustained alarms/second 20/sec
3
Maximum number of remote OPC A&E Servers subscribed to by the Experion 5
Server
Maximum number of remote OPC A&E Clients supported by the Experion OPC 15
A&E Server
Note 1 – The Experion Server Alarm System will handle an event burst of up to 1000 events, with a minimum time
between consecutive bursts. An “event burst” is defined as a group of events greater than 40/sec, received
from all connected Event Servers in a period of less than 3 seconds. The time period required between
consecutive bursts, to allow for event processing, can be calculated using the following formula:
∆T = BS/(40-ER)
Where:
∆T = # of seconds required between bursts
BS = Burst Size (number of events in the burst)
ER = Event Rate between bursts
Examples:
1) 1000 Event burst and no events between bursts: ∆T = 1000/40 = 25 seconds
2) 500 Event burst with 30 events/sec between: ∆T = 500/10 = 50 seconds
Note 2 – Up to two events are also generated for every alarm, including one event for entering the alarm condition
and one for return to normal.
Note 3 – The Experion Server includes the option to support OPC Alarms & Events in addition to native Experion
notifications. When the Experion Server is configured to receive alarms and events from an OPC Alarm &
Event Server, the notification limits noted in this table are applicable to the combined set of events received
from all connected event sources.
- 30 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
- 31 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Alarm Pager
The following specifications apply to the alarm paging option.
Protocols Remarks
1
Paging Entry Terminal (PET)
1
Telocator Alphanumeric Protocol (TAP)
UCP protocols Mainly used in Europe.
• UCP 01 The two-digit suffixes refer to the EMI command
• UCP 30 numbers being used by the provider.
• UCP 51
Note 1 – Service Providers in North America generally use the PET or TAP protocols.
- 32 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Model Numbers
Server Hardware
Model Number Description
MZ-NTPC51 Dual processor Server with Windows 2000 Server (Dell 1800)
MZ-NTPC81 Dual processor Server with Windows 2000 Server, RAID-1 (Dell 1800)
MZ-NTPC71 Dual processor Server with Windows 2000 Server, RAID-5, 2U rack (Dell 2850)
TP-DFP202 Desktop 20.1” Flat Panel Display
MZ-PCEB23 Single port Ethernet Comm. Board, 100 Mbps for Server PCs
NE-NICS01 1 Dual port Ethernet Comm. Board, 100 Mbps (for FTE)
MZ-PCEM34 1 GB Memory Module for MZ-NTPC51, -81
MZ-PCEM42 2 GB Memory Module for MZ-NTPC51, -71, -81
MZ-PCDT03 Terminal Server-8 RS232 Ports, RJ45
MZ-PCEB12 8 Port RS-232/422/485 Serial Board PCI Bus
MZ-PCEB11 8 Port RS-232/422/485 Expansion Module
MZ-PCDD06 Trackball w/PS-2 Connector
1
See Fault Tolerant Ethernet Specifications and Technical Data document for FTE hardware
Server Database
Model Number Description
EP-DBASE1 Database Base Software
EP-DPR100 100 Process Point Adder to Database Size
EP-DPR01K 1,000 Process Point Adder to Database Size
EP-DPR02K 2,000 Process Point Adder to Database Size
EP-DPR05K 5,000 Process Point Adder to Database Size
EP-DPR10K 10,000 Process Point Adder to Database Size
EP-DSC100 100 SCADA Point Adder to Database Size
EP-DSC01K 1,000 SCADA Point Adder to Database Size
EP-DSC02K 2,000 SCADA Point Adder to Database Size
EP-DSC05K 5,000 SCADA Point Adder to Database Size
EP-DSC10K 10,000 SCADA Point Adder to Database Size
Server Redundancy
Model Number Description
EP-RBASE1 Redundancy Base Software
EP-RPR100 100 Process Points Redundancy Adder
EP-RPR01K 1,000 Process Points Redundancy Adder
EP-RPR02K 2,000 Process Points Redundancy Adder
EP-RPR05K 5,000 Process Points Redundancy Adder
EP-RPR10K 10,000 Process Points Redundancy Adder
EP-RSC100 100 SCADA Points Redundancy Adder
EP-RSC01K 1,000 SCADA Points Redundancy Adder
EP-RSC02K 2,000 SCADA Points Redundancy Adder
EP-RSC05K 5,000 SCADA Points Redundancy Adder
EP-RSC10K 10,000 SCADA Points Redundancy Adder
- 33 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
SCADA Interfaces
Model Number Description
EP-IDNP3P DNP3 Protocol Interface
EP-IMDBUS Modbus (RTU, Plus, ASCII, & TCP) Interface
EP-IABSER Allen-Bradley Serial Interface (Does not require RSLinx)
EP-IABRSL Allen-Bradley RSLinx Interface (requires EP-IRSL24)
EP-IABINT Allen-Bradley Integration (requires EP-IABSER or EP-IABRSL)
1
EP-IRSL24 Allen-Bradley RSLINX Software, Ver. 2.4
EP-IGES90 GE Fanuc Series 90 PLC via Ethernet (requires EP-IGEAPI)
EP-IGEAPI GE API License
EP-ISMNS5 Siemens S5/S7 &TI PLC Via H1 / TF API
EP-IGEM80 GEC GEM80 PLC Interface
EP-IYTMA5 Yamatake MA500 Interface
EP-IBBRTU Bristol Babcock RTU Interface
EP-IMR35X Moore 351, 352, 353, 383 Interface
EP-IAPLCM Applicom Interface
EP-IHTCHI HITACHI Interface
EP-IASEAI Asea Interface
EP-IMAPAC Moore APACS Interface
Note 1 – RSLinx is available in a variety of packages with varying degrees of functionality. One feature of RSLInx is
the exposure of underlying device data via an OPC Data Access Server. RSLinx OEM, the package
provided with this model number only allows non-remote (OPC client resident on the same PC as RSLinx)
OPC clients to connect to the OPC Server. If the OPC Data Access Server of RSLinx is required and must
be accessed by remote OPC clients, please purchase the RSLinx Gateway version directly from Rockwell
Automation or a distributor.
- 34 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Application Enablers
Model Number Description
EP-AERMGR Recipe Manager
EP-AESHED Point Control Scheduler
EP-AEODBX ODBC Data Exchange
EP-AEPAGE Alarm Pager
EP-AEBRPT Batch Report
Application Toolkit
Model Number Description
EP-AEAPTK Application Development Toolkit
OPC
Model Number Description
EP-OPCCLI OPC Client Interface
EP-OPCCAD OPC Advanced Client
EP-OPCINT OPC Integrator, per Connection
EP-OPCSDA OPC Data Access Server, per Connection
EP-OPCSAE OPC Alarm & Event Server, per Connection
TP-RDM000 Redirection Manager
Engineering Tools
Model Number Description
EP-TQBLDR Quick Builder – SCADA database builder
EP-TDSPBD HMIWeb Display Builder
On-Process Migration
Model Number Description
EP-OPM0BS Base On-Process Migration Support
EP-OPM100 100 Point On-Process Migration Support
EP-OPM01K 1,000 Point On-Process Migration Support
EP-OPM02K 2,000 Point On-Process Migration Support
EP-OPM05K 5,000 Point On-Process Migration Support
EP-OPM10K 10,000 Point On-Process Migration Support
- 35 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
Glossary
- 36 -
Experion Server Specifications and Technical Data EP03-200-210
Release R210 Version 1.1
www.honeywell.com/ps
PlantScape ® and TotalPlant ® are registered trademarks and Experion™ is a trademark of Honeywell International Inc.
All other products and brand names shown are trademarks of their respective owners.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of
merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written
agreement with and for its customer. In no event is Honeywell liable to anyone for any indirect, special or consequential damages.
The information and specifications in this document are subject to change without notice.
USA: Honeywell Industry Solutions, 2500 W. Union Hills Drive, Phoenix, AZ 85027 /Canada: The Honeywell Centre, 155 Gordon Baker Rd., North
York, Ontario M2H 3N7/Latin America: Honeywell, Inc., 480 Sawgrass Corporate Parkway, Suite 200, Sunrise, Florida 33325/Japan: Honeywell
K.K., 14-6 Shibaura 1-chome, Minato-ku, Tokyo, Japan 105-0023/Asia: Honeywell Pte Ltd., Honeywell Building, 17 Changi Business Park Central 1,
Singapore 486073, Republic of Singapore/Pacific Division: Honeywell Pty Ltd., 2 Richardson Place, North Ryde NSW Australia 2113/Europe and
Africa: Honeywell S.A. Avenue du Bourget 3, 1140 Brussels, Belgium/Eastern Europe: Honeywell Praha, s.r.o. Budejovicka 1, 140 21 Prague 4,
Czech Republic/Middle East: Honeywell Middle East Ltd., Technology Park, Cert Complex Block Q, Muroor Rd., Abu Dhabi, U.A.E.