experion server specifications

5/28/2018 Experion Server Specifications

1/38

Experion Process Knowledge

System (PKS)

Experion Server Specifications andTechnical Data

EP03-200-210Release R210

Revision Date: May, 2005Version 1.1


2/38

Experion Server Specifications and Technical Data EP03-200-210Release R210 Version 1.1

- i -

Experion Server Specifications and Technical Data

Table of Contents Page

Revision History ...............................................................................................................................ii iIntroduction ......................................................................................................................................4Server Overview........................................................................................................................... 5

Product Description and Features ................................................................................................... 6Real Time Database..................................................................................................................... 6

Executive Subsystem ............................................................................................................... 6User Interface Subsystem ........................................................................................................ 6Acquisition and Control Subsystem .......................................................................................... 6History Collection Subsystem................................................................................................... 7Alarm and Event Subsystem .................................................................................................... 7Report Subsystem .................................................................................................................... 7Redundancy Subsystem........................................................................................................... 7Configuration Subsystem.......................................................................................................... 7

Point Structures............................................................................................................................ 7User-defined Parameters.......................................................................................................... 8User-defined Structure.............................................................................................................. 8Algorithms................................................................................................................................. 8Container Points .......................................................................................................................8Point Scripting........................................................................................................................... 8User-defined Data Formats ...................................................................................................... 8

Enterprise Model .......................................................................................................................... 8Asset Model .............................................................................................................................. 9Alarm groups ............................................................................................................................ 9

Networking.................................................................................................................................... 9Fault Tolerant Ethernet ............................................................................................................. 9Ethernet .................................................................................................................................... 9ControlNet................................................................................................................................. 9

Server Scripting ............................................................................................................................ 9Extended Event Archiving .......................................................................................................... 11System Management ................................................................................................................. 11

System Performance Server ..................................................................................................11System Event Server .............................................................................................................. 11

Configuration Studio................................................................................................................... 11Options........................................................................................................................................... 13

Server Redundancy.................................................................................................................... 13Fault Tolerant Ethernet............................................................................................................... 13Distributed Systems Architecture ............................................................................................... 14

Consolidated Alarm Summary and Trending.......................................................................... 14Honeywell Systems Integration.................................................................................................. 15

TotalPlant Solution (TPS) System Integration ........................................................................ 15Honeywell TDC3000 Data Hiway Integration ......................................................................... 15Honeywell Safety Controller Integration ................................................................................. 16

OPC Connectivity Options.......................................................................................................... 17About OPC ................................................................................................................................. 17

OPC Advanced Client............................................................................................................. 18OPC Display Data Client ........................................................................................................ 19OPC Client Interface............................................................................................................... 19OPC Data Access Server ....................................................................................................... 19OPC Alarm & Event Server ....................................................................................................19


3/38


- ii -

OPC Integrator........................................................................................................................ 19Redirection Manager .............................................................................................................. 20

SCADA Interfaces ...................................................................................................................... 20Open Data Access .....................................................................................................................21

ODBC Driver........................................................................................................................... 21Network Server ....................................................................................................................... 22

21 CFR Part 11 .......................................................................................................................... 23

Electronic Signature Option .................................................................................................... 23Application Enablers................................................................................................................... 23

Batch Reporting ...................................................................................................................... 23Recipe Management............................................................................................................... 23Point Control Scheduler.......................................................................................................... 23Alarm Pager ............................................................................................................................ 23ODBC Data Exchange............................................................................................................ 24

Application Toolkit ...................................................................................................................... 24Specifications and Sizing ............................................................................................................... 25

Server PC................................................................................................................................... 25Redundancy Performance.......................................................................................................... 26Database Sizing .........................................................................................................................26History Collection ....................................................................................................................... 27History Sizing.............................................................................................................................. 28Real Time Database SCADA Point Structures .......................................................................... 29Data Access Performance.......................................................................................................... 30Notification Performance............................................................................................................ 30Distributed Systems Architecture ............................................................................................... 31

DSA Publishing Server Communications Performance ......................................................... 31DSA Subscribing Server Communications Performance ....................................................... 31Miscellaneous DSA Specifications ......................................................................................... 31

Alarm Pager................................................................................................................................ 32Model Numbers.............................................................................................................................. 33

Server Hardware ........................................................................................................................ 33Server Database ........................................................................................................................ 33Server Redundancy.................................................................................................................... 33Distributed System Architecture................................................................................................. 34Additional Honeywell Device Integration.................................................................................... 34SCADA Interfaces ...................................................................................................................... 34Application Enablers................................................................................................................... 35Application Toolkit ...................................................................................................................... 35Open Data Access .....................................................................................................................35OPC............................................................................................................................................ 35Engineering Tools ...................................................................................................................... 35On-Process Migration................................................................................................................. 3521 CFR Part 11 Option............................................................................................................... 35

Glossary ......................................................................................................................................... 36


4/38


- iii -

Revision History

Revision Date Description

1.0 November 2004 Release Revision

1.1 May 2005 Update with minor corrections


5/38


- 4 -

Introduction

Exper ion Process Knowledge System

The Experion Process Knowledge System(PKS) is a next-generation processautomation system that unifies people withprocess, business and asset managementto help process manufacturers increaseprofitability and productivity. It is the onlyprocess automation system to focus onpeople making the most of the knowledgethey hold. Experion improves businessperformanceand peace of mindbycollecting and integrating process andbusiness data across the entire facility,making information and knowledge availablewhere and when needed, thereby enablingpeople to make the right decisions. At theheart of the Experion PKS is the Experionplatform, which provides a foundation forintegrating all process control and safetymanagement (including non-Honeywellsystems) into a single, unified architecture.The Experion platform embeds advancedapplicationsto improve processperformance, asset and peopleeffectiveness and business agility.

Exper ion Plat form

The Experion platform provides thefoundation for the Experion ProcessKnowledge System (PKS), integrating allprocess control and safety management(including non-Honeywell systems) into asingle, unified architecture. Robust andscalable, the Experion platform is built onHoneywells 30 years of experience indelivering process control and safety systemexpertise. It takes customers well beyondDistributed Control System capabilities byproviding next generation automation controlthrough embedded decision support anddiagnostic technology that drives informationto the decision maker. The safetycomponent maintains the security of an

independent environment from the mainlinecontrol system, increasing security andsystem dependability. The result is a unifiedautomation platform that elevates safetyand process availability, as well asproduction and profitability

.

Archi tecture Overv iew

Experion comprises many different integrated hardware and software solutions depending uponthe needs of the installation. Figure 1 is a representation of the many possible nodes that can beutilized in the flexible and highly scalable Experion architecture.

Fi ure 1. Ex erion PKS Overview Architecture Dia ram


6/38


- 5 -

Server OverviewThis document describes the specificationsand technical data for the Experion Serverhardware and software. The Server is arequired component of Experion. All the

functionality described in this document,including the options, are core functionality.That is, it is developed as a system andlicensed as options to allow users to simplypurchase what is necessary.

Options can be purchased at any time andadded to a system with a simple license key.Most options do not even require anadditional software installation. Theseinclude functions such as: Server Redundancy an on-line

synchronized backup provides high

availability to your process. Distributed Systems Architecture

(DSA) DSA brings multiplesystems together in a seamlessmanner.

Honeywell System IntegrationHoneywell Systems such as TDC2000, TDC 3000, TPS, and FSC arecomprehensively integrated intoExperion.

OPC Connectivity Options theExperion Server can serve data andalarms and events to OPC clients or

it can act as a client to other OPCservers. SCADA Interfacesmultiple

interfaces to RTUs, PLCs, and otherdevices to integrate these devicesinto your control system.

21 CFR Part 11 FunctionsExperion provides the necessaryfunctions, such as ElectronicSignature support, for regulatedindustries.

Alarm Pager send alarms directlyto your maintenance crews pagers,

e-mail, and more. Open Data Access Wheneveryou need to get Experion data into aspreadsheet or database, forexample, Open Data Access isrequired.

On-process Migration migratethe Server software from a currentrelease to the next available releasewithout taking Experion off-line.

For more information about Experion, pleaserefer to:

EP03-100-210 Experion ProcessSystem Overview

EP03-210-210 Experion StationSpecification and Technical Data EP-3-300-210 Experion Platform

CEE-based Controller Specificationsand Technical Data

EP03-310-210 Experion ApplicationControl Environment

EP03-400-210 Experion ChassisI/O Modules - Series A Specificationand Technical Data

EP03-410-210 Experion Rail I/OModules - Series A Specificationand Technical Data

EP03-420-210 ExperionGalvanically Isolated/IntrinsicallySafe Rail I/O Modules - Series HSpecification and Technical Data

EP03-430-210 Experion PM I/OSpecifications and Technical Data

EP03-440-210 Experion DeviceNetSpecification and Technical Data

EP03-450-210 Experion PROFIBUSDP Specification and TechnicalData

EP03-500-210 Honeywell FaultTolerant Ethernet Specification and

Technical Data


7/38


- 6 -

Product Description and Features

Real Time Database

At the heart of the Experion Server softwareis the real time database. The followinginformation is stored in the real timedatabase:

Acquired Data data read from orrelated to controllers

Process History historical store ofacquired data

Alarms and Events System Status Configuration Data details on how

the Experion Server subsystemshave been configured to operate

User Defined Data structures tostore application specific information

To maintain data integrity, memory residentportions are periodically written to the harddisk in a process known as checkpointing.

The Experion Server software consists of anumber of functional subsystems as shownin Figure 2.

Executive Subsystem

Time keeping and scheduling is the major

function of the Executive subsystem. Inessence, this subsystem manages allscheduled tasks throughout the server.This includes items such as requesting

display updates, requesting scheduled

reports, watch dog timers for customapplications.

User Interface Subsystem

For server-connected Stations, thissubsystem manages two tasks:

Keyboard requests, and Writing data to the Station and

reading data entered at the Station

Acquisition and Control Subsystem

For Control Execution Environment (CEE)devices, such as the C200 controller and

The Application Control Environment (ACE)node, this subsystem manages a dynamiccache of data for display on graphics, forhistory, and for use by external applications.This cache grows and contracts dynamicallydepending on the needs of its users Station displays, applications, etc. This isan extremely powerful mechanism as itmeans that not all data is polled from theC200 controller (and other CEE devices).Rather, data is only subscribed and updatedby exception based on a need from a user.And, if more than one user or application

requires the same set of data, the cacheprovides this data without making duplicaterequests to the controller. When users stoprequesting data, the cache no longer asks

for the data.

Data acquisition and control forSCADA devices is also handled bythis subsystem. When points aredownloaded to the server using QuickBuilder, scan tables are built thatdefine how data will be acquired. Theserver polls the devices (RTUs, PLCs,

etc.) at periodic rates. Depending onthe interface, report by exception andother scanning mechanisms aresupported.

Real Time

Database

Real Time

Database

Executive

Executive

User Interface

User Interface

Acquisition &

Control

Acquisition &

Control

History

Collection

HistoryCollection

Alarm &

Event

Alarm &Event

Report

Report

Redundancy

Redundancy

Configuration

Configuration

Real Time

Database

Real Time

Database

Executive

Executive

User Interface

User Interface

Acquisition &

Control

Acquisition &

Control

History

Collection

HistoryCollection

Alarm &

Event

Alarm &Event

Report

Report

Redundancy

Redundancy

Configuration

Configuration

Figure 2. Server Subsystems


8/38


- 7 -

History Collection Subsystem

The on-board history collection system ofthe Experion server is composed of threehistory classes.

Standard History 1 minute snapshot

6 minute average 1 hour average 8 hour average 24 hour average

Fast History User selected 1, 2, 3, 4, 5

(default), 10, 15, or 30second snapshot

Extended History 1 hour snapshot 8 hour snapshot 24 hour snapshot

Historical data can be archived. Thearchiving capabilities include the ability toretain archives on the server hard drive,move the archive to another drive after adefined period of time, or to delete thearchive after a defined period of time.Archiving will not occur if the hard drive fallsbelow a configurable amount of free space.

Once collected, historical data is seamlesslyaccessible by

Trend displays Custom displays

Reports Application programs Spreadsheets ODBC compliant database

The archiving capabilities provide effectivelyunlimited duration of historical storage.

If additional history features are necessary,Honeywells UniformancePHD is optimallysuited for the task.

Alarm and Event Subsystem

Alarming for points from CEE devices,known as Process points, are alarmed andtime stamped at the controller. SCADApoint alarms are initiated, time stamped, andacknowledged by the server.

Each of the configured alarms can beassigned a priority ranging from Journal,Low, High to Urgent. An alarm sub-priority

(0 to 15) can also be assigned to furtherdifferentiate alarms.

All alarms are recorded as events.Additionally, login actions, operator actions,and configuration changes are logged in the

event journal.Report Subsystem

The report subsystem is designed to createreports from a list of standard and optionalreports. This subsystem maintains thereport configuration for scheduled or on-demand execution.

Redundancy Subsystem

The redundancy subsystem is designed tofail over to a backup server in the event of asingle failure of the primary or controlling

server. Please see the section titled ServerRedundancy on page 13 for more details onthis optional function.

Configuration Subsystem

The real time database manages theconfiguration information downloaded byConfiguration Studio.

Point StructuresFor process points (those points resident inCEE devices such as the C200 controller), astandard database point structure is built in

the Real Time Database upon download tothe device. This point structure includes aminimum of necessary parameters.Additional parameters are dynamicallyadded to the point database as neededwhen requested for display, historycollection, etc. This supports the dynamiccache (see theAcquisition and ControlSubsystem section) by providing an explicitlink to the data. In this way, the cache doesnot have to learn where to get the data eachtime it is subsequently requested.

The database also provides the followingstandard point structures: Analog point structure Status point structure Accumulator point structure User defined structure Algorithms Container points OPC advanced points


9/38


- 8 -

For further detail on the parametersassociated with Analog, Status, andAccumulator point structures, please seepage 29 in the Specification section of thisdocument.

Each point in the database has a number ofassociated parameters, all of which can bereferenced relative to a single tag name orcomposite point.

User-defined Parameters

With each of the above point types, it ispossible to add user-defined parameters tothe existing pre-built parameters. Thisenables tags to be extended to contain freeformat values, constant values, or valuesused by applications and scripts to storecalculated or derived plant information.

User defined parameters can be assigned tohistory collection.

User-defined Structure

In order to support other types of data suchas user entered or calculated data fromapplication programs, the server provides auser-definable database area that is fullyintegrated into the system. Data containedin this database is accessible by: Custom Graphics Custom Reports Server based Application Programs

Network based ApplicationsPrograms Composite points

Algorithms

In addition to standard point processingfunctions and VB scripting, the systemallows additional processing through the useof standard algorithms that may be attachedto an analog, status or accumulator point.Functions provided by these algorithmsinclude: Arithmetic calculations Boolean calculation Maximum/minimum value Integration Run hours totalization Group alarm inhibit Report request Application program request

Container Points

Container Points support the TemplateDisplay capabilities. A container pointcombines a group of logically associatedpoints into a single point structure. Thecontainer point parameters are flexible. For

example, a container point could be built fora tank that includes the: Level Temperature Fill valve status Drain valve status Agitator status

Point Scripting

With each standard SCADA and Processpoint, an easy-to-use VBScript can beattached to enable powerful point basedscripts to be processed. These scripts can

be enabled: OnAlarm, OnChange,OnNormal, OnAcknowledge and more. Thepowerful scripting environment also enablesLibrary scripts to be created, enablingrepetitive logic to be simply applied on manypoints. For further details, please refer tothe section titled Server Scripting on page 9.

User-defined Data Formats

Data formats convert field values into valuesthat are more useful for operators and otherapplications. In addition to a wide range ofstandard data formats appropriate for the

optional SCADA interfaces, you can createuser-defined data formats for the OPCClient, Allen-Bradley, and ModiconInterfaces.

When a SCADA point is configured to usean unscaled user-defined data format, thevalue is formatted, but not scaled, prior toloading it into the parameter. Therefore, thescaling for each parameter that uses theformat must be defined. Scaled user-defined data formats will format and scale afield value before loading it into the

parameter.

Enterpr ise ModelWith the volume of process and businessinformation growing rapidly and pressure forincreased efficiency continuing, the ExperionEnterprise model provides sophisticateddata support for todays operators andengineers. The enterprise model delivers a


10/38


- 9 -

consistent definition of all the data in theplant or mill, ranging from a high-endbusiness view down to individual points. Theenterprise model goes well beyondDistributed Control System capabilities byproviding a unified framework for decision

and diagnostic support that is used byengineers, operators, and applications.

Two unique components form the base ofthe enterprise model: the asset model andalarm groups. Details of the implementationand use of asset model and alarm groupsare given in the sections below.

Asset Model

The asset model represents the hierarchicalorganization of items in the enterprise, forexample process units, individual pieces of

equipment or facilities etc.The operator navigates and manages theprocess from this intuitive hierarchicalrepresentation. Alarms are grouped andvisualized using the asset model andsimilarly, when configuring an operator orstation scope of responsibility, the engineerhas the ability to manage this from the samehierarchical representation.

Assets and the asset model form the core ofthe Experion Enterprise Model and replacethe flat area structure that was available inprevious releases of Experion.

Alarm groups

The alarm group functionality provides amechanism to aggregate and indicate alarmstatus for a disparate collection of points.For example, points contained by severaldifferent assets may be in use on a singlegraphic. If the operator needs to have thisgraphic linked to an operator keyboardbutton, the Alarm Group can be used torepresent the LED alarm states for all thepoints in use on the graphic.

Networking

Fault Tolerant Ethernet

Honeywells patented Fault TolerantEthernet (FTE) network utilizes off-the-shelfnetworking hardware to allow Ethernet to

provide DCS network functionality. FTEprovides a robust and high availabilitynetwork infrastructure for communicating toExperion Stations, C200 controllers, ACENodes, etc. Refer to page 13 for moreinformation about FTE. An FTE software

license is bundled with the Server basesoftware. FTE hardware can be added toimplement the solution.

Ethernet

Experion Servers also support an Ethernetnetwork to communicate to nodesthroughout the system.

ControlNet

As an option, ControlNet can be used tocommunicate with C200 controllers. Formore information, please refer to document

EP03-300-200, Experion ControllerSpecification & Technical Data.

Server Scr ipt ingServer Scripting encompasses two features.The first provides scripting support to allowthe behavior of the Server-residentsubsystems and its run time objects to beextended. Examples of server objects are: Server Points and Parameters (described in the

section titled Point Scripting) Reports Assets Tasks (Application Programs)The user configures these scripts to be runby the server either periodically or when aspecified event occurs. In addition, standarddisplays are supplied to allow the user tomonitor the status of running scripts.

Example scenarios of when to use serverscripts include:

Raising an Urgent Alarm whenRelated Points Go into Alarm

Changing the Ranges of Related

Points Checking a Point's Value after It has

Gone into Alarm Using Auxiliary Parameters to Store

and Display Data Reading Data from a Text File Checking a Value at Regular

Intervals


11/38


- 10 -

Generating and Emailing Reports(see Figure 3)

Capturing and Storing Data in aText File

Emailing in Response toUnacknowledged Alarms

Launching an External Application Performing the Same Calculation on

a Set of Points

The second feature is the Server OLEAutomation Object Model that allowsAutomation Controllers to access and

manipulate objects that exist within the

Servers run time environment. AutomationControllers include products such asMicrosoft Visual Basic, Word, Excel, Accessand any programming environment that canuse Microsoft COM objects.

Server scripting uses the Server OLEAutomation Object Model as the means bywhich it interacts with the server objects.These two features together form the Server

Scripting support. Thearchitecture employed byServer Scripting gives itgreat flexibility andfunctionality. There aresome tasks however, thatare better suited to acustom application.

Consult Table 1 to help

classify tasks into those thatare well suited to Serverscripting and those that arebetter addressed by acustom application. Sometasks qualify for bothcategories, and the rules areflexible when deciding whattasks can and cannot be

performed by Server scripts. Wherepossible, existing server functionality shouldbe used in preference to writing Serverscripts. Standard server functionality

optimizes the task implementation.

Table 1. Server Scripting versus Custom Application

Task Server Script Custom Application

Extend server functionality via information transfer Yes Yes

Relatively short processing (< 50 lines of code) Yes Yes

Used to provide linkage to other applications via automation servers Yes Yes

Code is interpreted at run-time. Yes No

Code is compiled and optimized at build time. No Yes

Computationally intensive No Yes

Optimized for supervisory control No Yes

Iterative code No Yes

Relatively complex user interface requirements No Yes

Extensive file handling No Yes

Script (program) state preserved on failover No No

Language VBScript Visual Basic, C++, etc.

Figure 3. Server Scripting Editor


12/38


- 11 -

Extended Event Arch iv ingExtended Event Archiving may be usedwhen the events logged by the system mustbe archived for later review. Storagecapacity is dependent upon media capacity,but storage of over 1 million events is easily

achievable. Approximately 60 Mb of harddisk space is required for every 100,000events archived.

Archived events can be restored so that theyare available for reporting. Event archivesare restored to a playback database. Theyare then available for reporting and can beviewed on the Event Summary display.

System ManagementThe Experion infrastructure includes multiplePC-based nodes. To manage the PC based

infrastructure as one system, Experionincludes two key components to monitor PCperformance in an integrated manner.

System Performance Server

The System Performance Server (SPS)collects real-time system information suchas CPU usage and available free memory,from any Windows 2000 or Windows XPnode. The SPS data is exposed as OPCdata items and available to be historized,trended or displayed on a process graphic ina manner consistent with process data

access. Additionally, any OPC Data AccessClient has access to the data for use of thedata in other applications.

System Event Server

Similarly to the SPS, the System EventServer (SES) collects and consolidatesWindows 2000 and Windows XP Event Loginformation and exposes them as OPCalarms and events. For example an eventcan be generated when a node reports, viathe Windows event log, that a disk is nearlyfull.

The Experion Alarm and Event subsystem isintegrated with the System Event Serversuch that system related alarms or eventscan be viewed from the Alarm Summarydisplay. The unique features of the alarm

summary display that apply to processalarms and messages can now be utilizedwith Windows system events. For examplethe system can be configured such that theoperator must acknowledge a system alarmfrom the Alarm Summary display in the

same manner that a process alarm isacknowledged.

Configurat ion StudioExperion hosts an integrated environmentthat substantially improves engineering andconfiguration management.

Configuration Studio exposes engineeringactivities as tasks rather than tools to theuser.All tasks are applied at a system levelmeaning that you can configure all theservers in your system from one location. Asystem is defined as one or more Experionservers, networked together and designatedby the user to work together in a unifiedway.

Common tasks in Configuration studio willbe performed within the Configuration Studioframework itself or launch specificapplications such as Control Builder, QuickBuilder or HMIWeb Display Builder.

Additions and modifications to the Experiondatabase can be made while the system ison-line and Station and Configuration Studio

can be accessed remotely using a RemoteEngineering and Station Server.

Control Builder

Control Builder enables the configuration ofcontrol strategies in the Control ExecutionEnvironments (CEE) of the C200 andApplication Control Environment (ACE). It isused to configure hardware such asnetworks, I/O modules, controllers, andfieldbus devices as well as control points like regulatory control, device (motor)control, discrete logic, sequential logic and

special user-defined functions. Furtherdetails about Control Builder can be found inthe CEE-based Controller Specification &Technical Data document.


13/38


- 12 -

Figure 4. Configuration Studio sample display

Quick Builder

Quick Builder allows users to configurepoints, communication links tocontrollers/RTUs, stations and printers.Quick Builder leverages a relationaldatabase engine to provide greaterproductivity through capabilities such asfiltering user views of the database,multipoint edit facilities and the intuitiveWindows style interface. Other features that

the relational database provide are the user-defined fields that can be used fortermination schedules, wire numbers, etc.,and a standard set of reports.

HMIWeb Display Builder

HMIWeb Display builder is a powerful tool tocreate custom displays. Details aboutHMIWeb display builder can be found indocument the Experion Station Specification& Technical Data document.


14/38


- 13 -

Options

Server Redund ancy

The Experion Server is optionally redundant.The redundancy subsystem provides a highavailability platform by enabling a pair ofsimilarly configured servers to support eachother in a primary/backup fashion. Shouldthe Primary fail, a fully functioning Backupassumes the Primary role. Primary refers tothe specific server that is actively acquiringdata from the controllers/RTUs and servingdata to the clients. The Primary propagatesall database transactions to the Backup overa redundant network so that both databasesremain in complete synchronization.

The backup server takes over from theprimary server if one of thefollowing conditions occurs:

The primary serverhardware fails and thebackup cannot communicate with it

All network links between theprimary and backup server arebroken

The primary loses C200communications

A user does a manual failover

In addition to synchronizing necessarydatabase files, the redundancy subsystem iscapable of automatically copying user filesfrom the primary server to the backup.

Fault Tolerant EthernetAs an alternative to conventional Ethernetredundancy schemes that typically employtwo separate Ethernet networks, Experioncan be deployed using FTE. The FTEsoftware license is bundled into the Serverlicense, so only FTE networking hardware is

needed to implement the solution.The FTE solution employs a single logicalnetwork over redundant media and does notrequire a server or station to re-establish anetwork connection. By providing morecommunication paths between nodes, FTEtolerates more faults, including all singlefaults and many multiple faults. In addition,FTE is transparent to higher-level

applications, which benefit from the highnetwork availability FTE provides, withoutrequiring any additional softwareconfiguration. Normal Ethernet nodes (non-FTE) can also connect to an FTE networkand benefit from a more availablecommunications environment thanconventional Ethernet redundancy schemes

offer.

FTE Node 1 FTE Node 2FTE Node 1 FTE Node 2

Figure 6. Sample FTE ConfigurationShowing Four Data Paths from One FTE

Node to Another

For additional FTE information, refer to theFTE Specification & Technical Datadocument.

Figure 5. Server Redundancy

FlexStationPrimary

Server

BackupServer

Screen Updates

DatabaseCheckpoints

Data Acquisition


15/38


- 14 -

Distr ibuted Systems Archi tectureDistributed Systems Architecture (DSA) isthe ideal solution for integrating processeswhen there are multiple control rooms, or forsegmenting control across units. DSAprovides the ultimate flexibility for both

operations and control using an integratedsecurity model, providing consolidatedalarms and seamless data access amongstmany other features.

Distributed Systems Architecture alsoprovides the maximum flexibility forgeographically distributed sites. Forexample, it allows multi-segment pipelinesand oil and gas fields with a large number ofwells to be managed from multiple remotelocations, as well as a central control room another industry first from Honeywell.

The figure below shows an example of adistributed system connected using a widearea network. The master control centeraccesses data from the servers at eachremote site. It may or may not have its ownlocally connected controllers. The servers atthe remote sites may also exchangeinformation with each other logically creatinga global database including:

- Global real time data access- Trending of real time and historical

system wide data, on a single trend- Global alarming

- Global system messages

Consolidated Alarm Summary andTrending

The Alarm Summary (for details on theStation Alarm Summary, please refer to theExperion Station Specification & TechnicalData document) shows a consolidated list of

local and remote alarms. The remotealarms displayed to an operator are thosefrom the remote areas for which alarms areenabled on the local server, and which havebeen assigned to the Station or operator.Local and remote alarms can be filtered inthe same way. The Station Alarm Zoneshows the highest priority unacknowledgedalarm, regardless of whether it is a local orremote alarm.

An operator can navigate directly to theAssociated or Point Detail display for a

remote alarm, just as for a local alarm.Similarly, when a trend includes a remotepoint, historical data for that point isretrieved from the remote server in real time.

Figure 7. Distributed Systems Architecture Example

Site A

Site B

WAN/Plant/

Site/Inter-plant

Network

WAN/Plant/

Site/Inter-plant

Network

Site C

WAN/Plant/

Site/Inter-plant

Network

Central

Control

Room

WAN/Plant/

Site/Inter-plant

Network

Site ASite A

Site BSite B

WAN/Plant/

Site/Inter-plant

Network

WAN/Plant/

Site/Inter-plant

Network

WAN/Plant/

Site/Inter-plant

Network

WAN/Plant/

Site/Inter-plant

Network

Site C

WAN/Plant/

Site/Inter-plant

Network

Central

Control

Room

WAN/Plant/

Site/Inter-plant

Network


16/38


- 15 -

Honeywel l Systems Integrat ion

Experion continues to provide a range ofoptions for integrating Honeywell systems.

TotalPlant Solution (TPS) System

IntegrationExperion provides full-scale integration ofTPS using the Experion Server TPS andExperion Station TPS. The details ofthese nodes are available in the ExperionTPS Integration Specification & TechnicalData document.

Honeywell TDC3000 Data HiwayIntegration

Experion provides a tight integration with awide range of Honeywell TDC3000 DataHiway devices. No other system can meet

the level of integration provided by Experionfor existing Data Hiway equipment.

Experions Integration with TDC3000 beginsat the Hiway layer. Using a Data Hiway

Ethernet Bridge, Experion is enabled as apreferred access device on the Hiway. ThisBridge provides Experion with efficientEthernet access to Hiway data and cancoexist with other preferred access networkdevices, like the Basic Operator Station or

Extended Operator Stations. The DataHiway Ethernet Bridge is a Honeywellproduct, so it provides reliable, stableintegration with the existing Data Hiwayequipment. Bridges may be redundant forany Data Hiway. Multiple Data Hiways aresupported with additional Data HiwayEthernet Bridges.

All box/slot configurations on each box canbe performed via system displays inExperion. No custom displays are required.Box status information can also be displayeddirectly in Experion with the supplied system

displays. If Box errors are reported, a fulldescription is immediately displayed on theController Summary Display, allowing anoperator or engineer to take remedial action.

Table 2. Supported TDC3000 Data Hiway Devices

Controller Type Acronym Description/Notes

Basic Controller CB The Basic Controller handles continuous Input/Output operations. It

accommodates I/O for eight modulating slots, plus eight analog inputs.Extended Controller EC The Extended Controller handles continuous Input/Output and logical

operations. It provides 16 modulating slots, 16 status outputs (8 SOA, 8SOB), and 16 optional status inputs.

Multifunction Controller MC

Advanced MultifunctionController

A-MC

The Multifunction Controller (MC) and Advanced Multifunction Controller(A-MC) handle continuous Input/Output operations, logical operations,and sequential control for batch operations. Each MC and A-MC has thecapacity to control 16 modulating slots and can handle: up to 32 analoginputs, up to 72 analog outputs, up to 256 digital inputs, and up to 64counter inputs.

Low Level Process InterfaceUnit (PIU)

LLPIU

High Level Process InterfaceUnit (PIU)

HLPIU

Low Energy ProcessInterface Unit (PIU)

LEPIU

PIUs are used when a large number of process variables need to bemonitored or fed to a higher-level module.

Data Highway Port DHP The Data Hiway Port (DHP) and LCS 620 Hiway Interface Module (HIM)provide a generic interface for non-Honeywell devices, for example:programmable controllers, analyzers, tank gauging systems, machinerymonitoring systems, emergency shutdown systems, data acquisitionsystems, and compressor control systems.

LCS Hiway Interface Module HIM The 620 LCS programmable controller can optionally interface directly tothe Data Hiway using a Hiway Interface Module (HIM) that plugs into theprocessor rack of the controller.

Reserve Basic ControllerDirectory

RCD

Reserve MultifunctionController Director

RMCD

Reserve Extended ControllerDirector

RECD

The Reserve Basic Controller Director, Reserve Extended ControllerDirector and Reserve Multifunction Controller Director are used tomonitor the status of the primary and backup controllers when redundantcontrollers are configured. They are also used to switch control from theprimary controller to the backup, and back again to the primary ifrequired.


17/38


- 16 -

Experion provides a CL/MC (ControlLanguage for Multifunction Controller)compiler, which has the same capability asthe CL/MC compiler used in TPS systems.This allows the user to write, compile andmanage control strategies for the

Multifunction and Advanced MultifunctionControllers, in Experion. The complier alsoallows the CL/MC source code from a TPSsystem to be re-compiled on the ExperionServer after TPS specific tags have beenreplaced with their Experion equivalents.While Experion is not able to compile SOPLprograms (the language used by EOSStations), it can be used to upload anddownload the compiled object code to thecontrollers.

Services are also available with the

Experion TDC3000 Integration toelectronically convert your existingEOS/BOS Hiway databases and performSOPL to CL conversions. This uniqueservice takes your existing 8 or 5 database images and builds a compatibleversion in Experion.

Honeywell Safety Controller Integration

Honeywell provides two safety controllerplatforms:

Fail Safe Controller (FSC) - theproven safety controller, with a

installed base of more than 5000systems and Safety Manager - the next

generation safety controller.

Experion can unify with both safetycontroller platforms into a single plant-widesafety system architecture. The safetycontroller platforms, with its high diagnostic-based Quadruple Modular redundancy

(QMR) technology, increase systemdiagnostic capabilities and improve systemtolerance for critical applications.

The safety controller platforms integrate intothe Experion platform in two ways:

Single or redundant Ethernetconnection to the Experion Server(with or without FTE)

Single or redundant fault tolerantserial link to the Experion Server

A redundant Ethernet integration withExperion delivers a TV approvedredundant, fault tolerant integration,irrespective of whether the safety controlleris redundant or not. Detailed safetycontroller status and extended diagnosticsare available to Experion Station. Theredundant safety controller contains twoseparate TV AK 6 (SIL3) approvedEthernet communication interfaces (coveredby sophisticated diagnostics) communicatingreal time fault tolerant data synchronously toExperion. If a connection via Ethernet is notpossible, a redundant, fault tolerant, RS232or RS485 serial link is supported.The safety controller Sequence of Events(SOE) functionality is integrated withExperion. Signals configured for SOE aretime stamped by the safety controller andtransferred to the Experion Server uponread request. The request frequency is

configurable. Additionally, the safetycontroller and Experion Server can beconfigured to implement timesynchronization. Data acquisition andcontrol is managed as described in earliersections with the advanced capabilities ofreport by exception scanning for highperformance.


18/38


- 17 -

On-Process Migrat ionThis optional feature provides the ability tomigrate the software from a current releaseto the next available release without takingthe Experion System off-line. In otherwords, Experion stays on-line allowing the

operators to maintain their view and controlof the process during the upgradeprocedure.

On-Process Migration is available for theExperion Servers and controllers whenconfigured with redundancy. This sectionexpands upon the Server On-processMigration capabilities. Please refer todocument EP03-300-200, ExperionController Specification & Technical Data formore information regarding the controllerOn-process Migration capabilities.

When configured for redundancy, thisfeature allows the Servers software to beupgraded. This involves the followingprocess:

1. The backup Server node will betaken offline and upgraded to thenew release and restarted.

2. The newly upgraded Server will thenbe synchronized with the runningprimary (previous release) Servernode.

3. The Server nodes will be placed in adual primary mode. In this mode

the upgraded Server nodesoperation may be tested andconfirmed against the previousrelease Server node.

4. Once the upgraded Server nodesoperation is confirmed the previousrelease Server node can be stoppedand upgraded to the latest releasesoftware.

5. The Server node last upgraded is

then started and synchronizedreturning the system to a standardredundant configuration.

OPC Conn ect iv i ty Opt ions

About OPCOPC (OLE for Process Control) consists of aset of standards that define interoperabilityamongst different automation and controlapplications, field systems and devices, andbusiness and office applications. For

detailedinformationabout OPC,visit the OPCFoundations

Web site, http://www.opcfoundation.org.

OPC provides data from a data source(server) and communicates the data to anyclient application in a standard way, therebyeliminating the requirement for anapplication to have specific knowledge abouta particular data source, such as its internal

structure and communications protocols.

Experion integrates OPC with DCStechnology to create the most flexible andpowerful OPC suite available, with a broadrange of Client, Server and redundancyOPC technologies as highlighted in the tablebelow.


19/38


- 18 -

Table 3. OPC Connectivity Options

OPCConnectivityTool Features

Versionsupport

OPC DataAccessClients

OPCAlarms&EventsClients

OPCDataAccessServers

OPCAlarm &EventServers

AncillaryOPCapplica-tions

OPCAdvanced

Client

Integrates complex datastructures and their

corresponding alarmsinto Experion.

SupportOPC A&E

version1.01,and OPCDA version2.0

!(mapped toOPCadvanced

points)

!

OPC DisplayData Client

Brings OPC Data intodisplays without havingto build points.

SupportsOPC DAversion 2.0

!(displayonly)

OPC ClientInterface

Maps information froman OPC Data Accessserver into ExperionSCADA points for thepurposes ofhistorization, control andalarming.

SupportsOPC DAversions 1.0and 2.0

!(mapped to

ExperionSCADApoints)

OPC DataAccessServer

Allows OPC DataAccess Clients to viewExperion point data andthe hierarchicalasset.point.parameterstructure

SupportsOPC DAversions 1.0and 2.05

!

OPC Alarm &Event Server

Exposes Experionsalarm & event data viathe OPC Alarm & EventStandard

SupportsOPC A&Eversion1.01

!

OPCIntegrator

An open methodallowing bi-directionaldata transfer betweentwo or more systems forthe purpose ofsupervisory monitoring,alarming and control.

SupportsOPC DAversion 2.0

!

RedirectionManager

Provides OPC Serverredundancy bytransparently redirectingclient requests to asecondary OPC Serverwhen the primary OPCServer is unavailable.

SupportsOPC DAversions 1.0and 2.05.SupportsOPC A&Eversion1.01

!

OPC Advanced Client

The OPC Advanced Client option containsthe OPC Advanced Alarm & Event Clientand the OPC Advanced Data Client. TheOPC Advanced Client solution provides theunique capability to integrate complex datastructures and their corresponding alarmsinto Experion.

OPC Advanced Alarm & Event Client

The OPC Advanced Alarm & Event Clientallows Experion to seamlessly integrateAlarm & Event Data from other OPC Alarm& Event Servers directly into the ExperionAlarm Summary.

OPC alarms are displayed andacknowledged in the same way as Experionalarms, giving operators a uniform userinterface. For example, when an OPC alarmis received, it appears in the Alarm

Summary; and when an operatoracknowledges the alarm, confirmation of theacknowledgement is sent to the OPC alarmand event server.

Facilities are provided for mapping assetsfrom the source OPC Alarm & Event Serverinto Experion assets. Functionality is alsoprovided to map alarm attributes from the


20/38


- 19 -

source OPC Alarm & Event Server intoExperions alarm attributes.

OPC Advanced Data Client

The Experion OPC Advanced Data Client isprimarily designed for integrating complex

subsystems, such as distributed controlsystems. Such systems typically have point-like structures that are defined as complexdata structures.

OPC items are mapped to OPC advancedpoints. OPC advanced points are built inConfiguration Studio and licensed asSCADA points. The OPC advanced pointsupports creating arbitrary point parameternames to reference OPC items.

After the OPC advanced points are built,

they can be added to trends, customdisplays, group displays, similar to otherpoint types in Experion.

OPC Display Data Client

The OPC Display Data Client is standardfunctionality in Experion and allows the userto insert OPC Data into a display without theneed to build points (the user is not requiredto purchase points for when accessing OPCdata using this client). This is ideal for datathat just needs to be visualized by theoperator and does not need to be alarmed,

historized, etc. OPC Data that is acquired inthis fashion supports both reads and writes.

OPC data items can be added directly tocustom displays without having to buildpoints in Configuration Studio.

OPC Client Interface

The Experion OPC Client Interface isprimarily designed to integrate low-complexity subsystems, such as PLCs,RTUs, single loop controllers etc.Configuration involves individually mappingOPC items to Experion SCADA points(analog, status and so on). If alarming isrequired, configure the associated point'salarm properties.

This interface should be used wheneverthere is a requirement for Alarming andthere is no OPC Alarm & Event Serverpresent.

OPC Data Access Server

The OPC Data Access Server functionalityallows OPC Data Access Clients to viewExperion Point data for control, plant-widehistorization, etc.

The OPC Data Access specificationsoptional point browse section has beenimplemented, allowing OPC Data AccessClients to view the hierarchicalAsset.Point.Parameter structure of theExperion Server.

OPC Alarm & Event Server

The OPC Alarm & Event Server is designedto expose Experions Alarm & Event data inan open manner to applications that requirethis information.

OPC Integrator

OPC Integrator is an open method allowingbi-directional data transfer between two ormore systems for the purpose of supervisorymonitoring, alarming and control. This typeof interface is commonly called an OPCDouble Headed Client.

OPC Integrator is valuable in the followingscenarios:

A system provides an OPC dataaccess server, but not an OPC

client. The system needs to retrievedata from Experion. Experion data needs to be

transferred to a third-party OPCserver whenever it changes,irrespective of the reason for thechange (including when the data ischanged by an operator).

A system includes Experion processcontrollers and needs to transferdata efficiently between thosecontrollers and some SCADAinterfaces at the supervisory control

layer.

OPC Integrator has many built-in featuresto ensure robust communication betweenOPC Servers. OPC Integrator supportsredundant Experion Servers and istherefore itself redundant. OPC Integratoralso supports redundant third party OPCServers natively. While OPC Integratorsupports redundant OPC Servers natively,


21/38


- 20 -

for the ultimate in OPC redundancysupport, Redirection Manager (RDM) isrecommended, offering benefits outlinedbelow.

There are many engineering timesavingfeatures included with OPC Integrator,such as: The ability to browse assets, points

and parameters that exist on thesource or destination OPC Server,

The ability to browse OPC ServerProgIDs on a particular server, and

Bulk item, import and export utilities.

While OPC Integrator could be used totransfer data between two or moreExperion Servers, DSA has beenspecifically built for this application. DSAallows data to be transferred, and also

transfers alarms, history, security, andmessages, in a secure efficient manner.

Redirection Manager

Redirection Manager (RDM) provides OPCServer redundancy by transparentlyredirecting client requests to a secondaryOPC Server when the primary OPC Serveris unavailable.

RDM is typically used by third party OPCData Access and Alarm & Event Clients

when connecting into the Experion OPCServer. Because the Experion OPC Serveris redundant, third party clients dontintuitively know how to handle Experionsredundancy schema. When a third partyclient connects into the Experion OPCServer using RDM, handling of Experionsredundancy schema is handledtransparently.

RDM can be used by Experion OPC Clientsthat dont handle redundant OPC Serversnatively such as the OPC Display Data

Client and the OPC Advanced Client. OtherExperion Clients that are redundancy awarecan also take advantage of RDM for itssuperior redundancy capabilities.

RDM features include: Support for both OPC Data Access

and Alarm & Event standards.

Group and Item synchronizationacross two active OPC Data Accessservers.

RDM will start the OPC Server if thesecondary node is available but doesnot have the OPC server running.

Consolidates OPC connectionsinstead of OPC Clients makingseparate connections into an OPCServer.

SCADA InterfacesIn addition to a wide range of OPC tools,Experion provides dedicated DataAcquisition and Control facilities tocommunicate with a wide range ofcontrollers and Remote Terminal Units(RTUs), listed in Table 4.

Experion supports acquisition of data usingeither:

Periodic Scanning utilizing thistechnique, Experion optimizescommunications traffic byautomatically calculating theminimum number of scan packetsrequired to collect the data.

Report by Exception (RBE) wheresupported by the controller, thistechnique is used to reduce thescanning load of the system whileimproving system response.

If necessary, periodic scanning may be usedin conjunction with RBE to ensure dataintegrity.

On-line Configuration

Given a sufficient level of system privilege, itis possible for users to view, manipulate andanalyze all data related to the SCADAinterfaces. For example a user at anyOperator Station in the system (includingthose operating remotely) could change analarm limit for a point in an RTU.

DiagnosticsOnce a controller or RTU is configured andplaced in service, Experion automaticallyperforms diagnostic scanning of the device.Additionally, Experion performs checks ondata integrity of all data acquired from thecontroller. Should an invalid or timed-outresponse be received, the data is ignoredand the transaction is recorded as an error.Statistics are kept and displayed by the


22/38


- 21 -

system on communication errors by means ofa communications barometer. Thebarometer value will increment for everyfailed call and will decrement for eachsuccessful call. In addition, the systemalarms separate marginaland failure

conditions based on user-defined limits toadvise the operator of a controller that is inerror. Communications statistics are

displayed on a standard system display andare available through the reporting sub-system or custom displays. If a controllerfails, all point parameter values that aresourced from it are indicated as bad to theoperator.

Table 4. Interfaces with Connection Details

SCADA Interface Software Connection Type

Honeywell FSC and Safety Manager Integration Serial and Ethernet

Honeywell S9000 Integration Ethernet

Honeywell 620 LCS Serial and Ethernet Interface Serial and Ethernet

Honeywell UDC 3000/5000/6300 Integration Serial ASCII

Honeywell Micromax LPU & Video Paperless Recorder Serial

Honeywell XLNET HVAC Controller Interface Software CBusHoneywell DPR Recorders (DPR 100, 180, 250, 3000) Serial

Honeywell RM7800 Flame Safeguard Serial (to Q7700 Network Interface)

Honeywell Universal Modbus Interface (HC900, UMC800, Trendview,DPR180/250, UDC2300/3300, DR4300/4500)

Serial and Ethernet

Allen-Bradley Serial Interface (Does not require RSLinx) Serial

Allen-Bradley RSLinx Interface Serial, Ethernet,DH+, and ControlNet

Applicom Interface Proprietary

Asea Interface Serial

Bristol Babcock RTU Interface Serial

DNP3 Protocol Interface Open Standard Serial and Ethernet (UDP)

GEC GEM80 PLC Interface Serial

GE Fanuc Series 90 PLC via Ethernet (requires MZ-AUIF01) EthernetHITACHI Interface Serial

Modbus (RTU, Plus, ASCII, & TCP) Interface Serial, Modbus+, Ascii and Ethernet

Moore 351,352,353,383 Interface Serial

Moore APACS Interface Ethernet and Modulbus

Siemens S5/S7 &TI PLC Via H1 / TF API H1/Industrial Ethernet

YamatakeMA500 Interface Serial

Open Data AccessWhenever another application requires datafrom the Experion database, Open DataAccess is required. For example, Open

Data Access is required when: Reading data into a Microsoft Excel

Spreadsheet Running a query on the database

from Microsoft Access A user written application is

accessing the databaseEach is considered a user of Open DataAccess. The two main components to Open

Data Access are the ODBC Driver and theNetwork Server.

ODBC Driver

ODBC is a standard set of function calls foraccessing data in a database. These callsenable utilizing Structured Query Language(SQL) queries on the database. ODBC canbe used in any client/server architecture,regardless of whether the database andclient application are resident on the samecomputer, separated by a network, or even if


23/38


- 22 -

Client PC or Experion PKS Server

Client PC or Experion PKS ServerExperion PKS Server

Experion PKS Server

Experion PKS ODBC

Client

Experion PKS ODBC

Client

Client Application

Client Application Experion PKS

Database

Experion PKS

Database

Experion PKS ODBC

Server

Experion PKS ODBC

Server

DataRequested

DataSent

DataSent

D

ataRequested

Data Requested

Data Sent

Client PC or Experion PKS Server

Client PC or Experion PKS ServerExperion PKS Server

Experion PKS Server

Experion PKS ODBC

Client

Experion PKS ODBC

Client

Client Application

Client Application Experion PKS

Database

Experion PKS

Database

Experion PKS ODBC

Server

Experion PKS ODBC

Server

DataRequested

DataSent

DataSent

D

ataRequested

Data Requested

Data Sent

Figure 8. Accessing Data via the ODBC Driver

they are on different computers usingdifferent operating systems.

The ODBC Driver allows the Serverdatabase to be queried using SQLcommands from ODBC client applications,

such as Microsoft Access. Additionally,custom application written in Visual Basic orC++ can also access the server databasevia the ODBC Driver. The Server databaseis exposed as a number of read-only ODBCtables including Points, Event History andProcess History. Driver features include:

Open read-only access to plant real-time and historical data

Throttling to prevent performanceimpact

Redundancy of data storage Fully functional examples for

productivity improvementsIt is optimized for Microsoft Access andother ODBC ad hoc query/reportapplications.

The Experion ODBC driver has two parts:the ODBC Server and the ODBC Client.The ODBC Client handles the ODBC callmade by a client application and passes it tothe ODBC Server. The ODBC Serverprocesses the ODBC calls, queries theExperion server database and returns theinformation to the client application.The ODBC Server always runs on the

Experion server computer. The Experion

ODBC Client can run on the server or onany other computer on the network. Figure8 shows a basic Experion ODBC driverconfiguration.

Network Server

The Network Server provides extremelyefficient, access to the Experion databasefor network based applications such asMicrosoft Excel Data Exchange and NetworkAPI options.

Microsoft Excel Data Exchangeallows Microsoft Excel to obtainreal-time and historical data fromthe Experion system. This optionprovides read and write access todata in one or more ExperionDatabases, providing a powerfuldata consolidation and reporting

tool. Wizards for Microsoft Excelare included to help set up the datato be collected.

Applications executing on othernetwork-connected platforms mayeasily access Experion real-timedata over the network using theNetwork API. The API provideshigh-level subroutine calls in VisualC/C++ or Visual Basic to allowread/write access to Experion datain a networked environment.


24/38


- 23 -

21 CFR Part 11The Experion Server provides enhancedcapabilities to support the Pharmaceuticalindustry and other FDA regulated industriesand their unique requirements related toregulations such as 21 CFR Part 11. These

features may be employed in any industrybut are specifically designed to meet theguidelines of 21 CFR Part 11.

Electronic Signature Option

This option enables the following: Electronic Signatures on C200

Messages Electronic Signatures on SCADA

points Journaling of OPC Server changes

to the database Journaling of Network Server

changes to the database Electronic Signatures on Point

Scheduler Support for reason sets for control

actions on SCADA points Journaling of changes that have

been made to the Server databaseusing Quick Builder. Full Printedname of the user that performed thedownload will be recorded.

Ability to securely enable anddisable Electronic Signatures bylocation.

In addition to the electronic signature optionthe following technical controls to meet 21CFR Part 11 compliance are available asstandard functionality:

System must be running to performQuick Builder downloads.

Only windows users that are alsoExperion operators can performQuick Builder downloads.

The system will default to using FullOperator name in events on startupand the field to change this setting is

not shown on the systemconfiguration display.

App l icat ion EnablersThe Experion Server provides powerfulapplication enablers with configurable(rather than programmatic) facilities tosupport individual application requirements.Application implementation time is greatly

reduced, providing extremely cost effectiveautomation.

Batch Reporting

Batch Reporting enables integratedreporting of batches or lots of a production

process run, to be compiled and archivedautomatically by the Experion Server. Thisfeature enables batch history and events tobe output either as a CSV file or directly intoMicrosoft Excel, if available. The BatchReport option is designed as a simplediscontinuous batch or lot reporting option.For a complete batch solution with Experion,please refer to TotalPlant Batch (TPB),which is completely integrated with Experionproviding advanced batch control andadvanced reporting tools.

Recipe ManagementRecipe Management provides facilities tocreate recipes and download them tonominated process units. Each recipe mayhave up to thirty items, with recipes chainedtogether to form larger recipes, if required.Recipe items may be used to set ingredienttargets, set alarm limits, set timers and placeequipment into correct operating state.Items may be individually enabled forscaling.

Point Control Scheduler

The Scheduler option allows pointsupervisory control to be automaticallyscheduled to occur at a specified time. Thismay occur on a one-shot basis, daily,workday, weekend, holiday, or a day of theweek.

Alarm Pager

The Alarm Pager option provides the abilityto page, SMS or email Experion operationaland system alarms.

Alarms can be forwarded to one or multiple

recipients, and can be escalated to anotherrecipient if an alarm remainsunacknowledged. The availability of eachrecipient can be defined such that alarmsare only sent to those that can attend tothem.

Alarm pager can be configured to use aservice provider or a local base station forthe broadcast of pages or SMS messages.


25/38


- 24 -

The information that is forwarded can becustom designed to include values such asTime, Date, Point ID, Alarm, Priority,Description and Value etc

The Alarm pager option can be used in a

variety of ways. For example it allowsoperators to move away from their controlroom desk or can be used to alert non-operational personnel to specific alarms.

ODBC Data Exchange

Thisoption enables two-way exchange ofdata between the Experion Server databaseand an ODBC-compliant local or networkthird-party database. It uses standardStructured Query Language (SQL)commands. The Experion Server acts as aclient application in this configuration, in

contrast with the ODBC Driver option wherethe Experion Server acts a serverapplication. Data from an Experion Serverdatabase can be transferred to a third-partydatabase, and data from a third-partydatabase can be transferred into theExperion Server database. Informationexchanged includes point values, pointhistory, and user file data. Databases thatinclude ODBC drivers include Microsoft SQLServer, Oracle 7, Microsoft Access, andSybase 10. This option can be configured toperiodically exchange data or exchange onrequest.

App l icat ion Toolk i tTwo application-programming interfaces(API) are available. The first is forapplications written to execute on theExperion Server and the second is forapplications that are required to run on

network-based clients (that are notnecessarily operator stations).

The API (programmed in C/C++) on theserver includes the following functions:

Read and write to point parametersin the database

Access to historical data Initiate supervisory control actions Access to the alarm/event

subsystem Access to user-defined database Provide a prompt for operator input

The API (programmed in Visual Basic orVisual C/C++) on the network-based clientsincludes the following functions:

Read and write to point parametersin the database

Access to historical data Initiate supervisory control actions Access to user-defined database Create alarms/events


26/38


- 25 -

Specifications and Sizing

Server PCA 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 thesespecifications but may not necessarily be the example platforms listed below. PCs purchaseddirectly through Honeywell carry full support as a qualified offering.

The table below lists suggestions per system size configuration.

Minimum System

This is the minimum hardware necessary to run the Experion components. It should beused for small configurations that may consist of 1 non-redundant Experion Server with 1Station or 1 Redundant Experion Server pair with 1 Station. The system typically onlyincludes 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 cansupport up 10-12 Stations or a Redundant Server can support 6-8 Stations. This type ofsystem includes 1 or 2 Stations with a single or dual screen actively monitoring andoccasional report generation.

Performance System

An advanced configuration may consist of a Redundant Experion Server pair, multipleDSA Servers, and greater than 12 Stations with single, dual, or quad screenconfigurations. This system typically includes active monitoring from multiple Stationsand random report generation.

SystemConfiguration

MinimumServer/eServer

TypicalServer/eServer/RemoteEngineering and Station

ServerPerformance

Processor Dual 2 GHz Xeon orFaster

Dual 2.4 GHz Xeon orFaster

Dual 3 GHz Xeon orFaster

RAM 1 GB 1 2 GB 2 GB

Networking 100 Mb Ethernet 100 Mb Ethernet 100 Mb Ethernet1000 Mb Ethernet

Video Resolution 1024 x 768, 65K colors 1024 x 768, 65K colors 1024 x 768, 65K colors

Hard Drive 36 GB 36 GB 36 GB

Operating System Windows 2000 Server Windows 2000 Server Windows 2000 Server

Example HardwarePlease contact yourHoneywellrepresentative forHoneywell-supplied

platform details.

Dell PowerEdge 1600,Dual CPU

Dell PowerEdge 1600,Dual CPU or

Dell PowerEdge 2600,Dual CPU

Dell PowerEdge 1800,Dual CPU or

Dell PowerEdge 2850Dual CPU

Note 1 In these configurations, paging may occur on these systems. Based on the intended usage of the platform,this configuration is acceptable. For better performance, users should upgrade the systems with anadditional 512 MB of RAM.


27/38


- 26 -

Redundancy PerformanceThe Experion Server redundancy option is an extremely robust and mature subsystem designedto provide the highest possible availability with the following specifications:

Specification

Checkpoint Period Default setting is 300 seconds (5 minutes)

User-defined File Backup Period 1 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 ofdatabase files between the primary and backup servers.

Database SizingThe Experion Server database is sized per the following specifications:

Database Item Default Size Maximum Size

Point Count1 50 20,000 Process Points50 65,000 SCADA Points

Process Points + SCADA Points !65,000 Points

Experion Station FlexConnections

140 402

Experion Station Console

Connections

010 103

Experion Station ConsoleExtension Connections

03 per ES-C 03 per ES-C3

Printer Connections 50 50Channels 90 99SCADA RTUs (Controllers) 100 255

Algorithm Blocks 6000 6000Assets 4000 40004Assignable assets5 1000 1000

Nesting depth for asset hierarchies 10 10

Children per asset No Limit ( up to the 4000 totalassets)

No Limit ( up to the 4000 totalassets)

Alarm groups6 5000 5000

Nesting depth for alarm grouphierarchies 5 5

Children per alarm group 500 500

DFDs (Dynamic Objects) onNamed Displays

1000 1000

Trend Sets 3000 3000Operating Groups 16000 16000Reports 1000 1000Point Control Schedules 1000 1000

Operators 1000 32767Recipes 500 32767Concurrent Alarms 1000 1000Concurrent Messages 1000 1000Stored Events 32000 32767

Extended Events Limited by hard disk size Limited by hard disk size

STD History Point Parameters 2000 10000EXTD History Point Parameters 2000 10000

FAST History Point Parameters 1000 100007Number of User Files 3 150Number of Application Tasks 80 80Point Lists 2000 2000SOE Entries 10000 32767


28/38


- 27 -

Note 1 The Experion database can be comprised of a mix of SCADA and Process Points in increments of 100Points.

Note 2 When a system includes Process Points, the number of Stations connections may need to be limited to keepthe data access performance within specified limits (see the Data Access Performance table). Servers withlarge 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 towardthis limit include both ES-F, ES-C nodes and ES-CE nodes. Total of ES-C and ES-CE nodes combinedcannot 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 processunits, individual pieces of equipment or facilities etc. This specification is a limit for a system that could becomprised of multiple servers.

Note 5 Assignable assets provide a way to assign assets to an operator's scope of responsibility. An assigned assetincludes all asset children of the assigned asset including any points associated with those assets or anyalarm 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 Col lect ionThe on-board history collection system of the Experion server is composed of three historyclasses. To support daylight savings and time zones, all collected data is historized in Universal

Coordinate Time (UCT) time stamp.

History Class Size

Standard History 1 minute snapshot 6 minute average 1 hour average 8 hour average 24 hour average

Fast History Stores snapshots at regular intervals called the fast historyinterval. This user selected interval can be 1, 2, 3, 4, 5 (default),10, 15, or 30 second snapshot

Extended History

1 hour snapshot 8 hour snapshot 24 hour snapshot


29/38


- 28 -

History Siz ingThe Experion Server history subsystem meets the following specifications:

Default DurationDefault Number

of SamplesMaximumDuration

MaximumNumber ofSamples

Standard History1 minute snapshot 24 hours 1442 69 days 100,000

6 minute average 1 7 days 1682 416 days 100,000

1 hour average 1 1 month 746 11.4 years 100,000

8 hour average 1 3 months 281 91.2 years 100,000

24 hour average 1 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

Fast History 21 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






Note 1 The averages are calculated using the 1-minute base interval. That is, 6-minute averages are calculated onsix 1-minute values.

Note 2 Only one of the Fast History intervals can be configured per server. The 5-second snapshot is the defaultFast History interval.


30/38


- 29 -

Real Time Database SCADA Point Stru ctu resThe following point structures and associated parameters are provided in the Real TimeDatabase when interfacing to SCADA devices.

PointStructure

Standard Parameters

Analog Point Name Scan Status SP Low Limit Point Description OP High Limit 0% & 100% Range

Control Deadband Scan Period Operator ControlLevel

Process Variable Scan Address OP Low Limit

Setpoint Control Timeout PV Clamp Flag

Normal Mode Alarm Permit Flag Engineering Units

Output Alarm Status Drift Deadband

Mode Up to 8 Alarm types 1 Alarm Deadband

SP High Limit Alarm Status Associated Display

Up to 4 user definableinputs

PV Last ProcessedTime 2

Status3 Point Name Output Output Pulse Width

Point Description Scan Status Re-Alarm Status Output Width Normal Mode Associated Display

Process Variable Scan Period Alarm Permit Flag

Control Timeout Scan Address Input Width

Mode Alarm Priority Control Failure AlarmPriority

PV Last ProcessedTime 2

Operator ControlLevel

Accumulator4 Point Name Scan Status Output Pulse Width

Point Description Normal Mode Re-Alarm Status

Output Width Scan Period Associated Display

Process Variable Scan Address Input Width

Control Timeout Mode Alarm Priority

Output Alarm Permit Flag PV Last ProcessedTime 2

Operator ControlLevel

Control Failure AlarmPriority

Note 1 Supported alarms include: PV Hi, PV Lo, PV HiHi, PV LoLo, Deviation Hi, Deviation Lo, Transmitter Hi,Transmitter Lo, Rate of Change, Control Fail, and Control Timeout. Each of the configured alarms can beassigned a priority ranging from Journal, Low, High to Urgent. An alarm sub-priority (0 to 15) can also beassigned to further differentiate alarms.

Note 2 Each time the PV is polled from the RTU, Experion will track and maintain the time/date of when the valuelast changed

, or more specifically, was last processed. If the Analog point in Experion, has a drift deadbandof 1%, then the last processed time is not updated until the PV moves by >1%. Similarly, if the driftdeadband is 0%, then the last processed time is not updated until the PV moves slightly.

Note 3 The PV of a status point can range from a single bit to a three bit digital input, allowing up to eight possiblestates.

Note 4 Data associated with pulsed inputs are stored in the system in an accumulator point type that will provideautomatic tracking of instrument rollover.


31/38

Experion Server Specifications an

experion server specifications

Documents

control subsystem

event subsystem

executive subsystem

report subsystem

redundancy subsystem

configuration subsystem

user interface subsystem

history collection subsystem