Plants Cape Process System and Controller

Release 320 Ver. 1.0

PlantScapeProcess System and Controller

Specification andTechnical Data

PS03-132Release 320

Revision Date: 27 October 2000Version 1.0

PS03-132 Ver 1.0Page 2 Release 320

PlantScape System & Controller Specification & Technical Data -- Release 320

PlantScape Process System & ControllerSpecification and Technical Data

Table of Contents Page

Introduction ..........................................................................................................................4Product Overview.................................................................................................................4System Overview .................................................................................................................6Product Description.............................................................................................................9

Control Processor Modules...................................................................................................................9Input/Output Modules..........................................................................................................................11Control Processor Functions -- Control Builder and Control Solver....................................................12Control Processor Load Performance ................................................................................................14

PlantScape System Overview ...........................................................................................16PlantScape System Philosophy ..........................................................................................................17

PlantScape Server Key Features.......................................................................................18Algorithms ...........................................................................................................................................21Trending..............................................................................................................................................23User Documentation ...........................................................................................................................30

Specifications.....................................................................................................................33Controller Function Block Types in CB10 Control Builder ..................................................................33PlantScape System Performance & Capacity Specifications .............................................................34PlantScape Server Hardware Descriptions.........................................................................................42PlantScape Server Sizing Specifications ............................................................................................43C200 Control Processor Specifications ..............................................................................................44Chassis Specifications ........................................................................................................................45Power Supply Specifications...............................................................................................................46Terminal Blocks, Cables and Connector Sizes...................................................................................46ControlNet Specifications....................................................................................................................47Honeywell-Recommended ControlNet Coaxial Trunk Cable Types ...................................................48

Topologies and Configuration Examples .........................................................................50PlantScape Hybrid Controller Examples.............................................................................................50Controller Redundancy Example ........................................................................................................52FOUNDATION Fieldbus Example...........................................................................................................53

Model Numbers ..................................................................................................................54Controllers, Racks, Power Supplies & Communications Modules......................................................54Miscellaneous Hardware.....................................................................................................................55Terminal Blocks, Cables and Connectors...........................................................................................56Hybrid Controller Software ..................................................................................................................57PlantScape Station Software ..............................................................................................................57PlantScape Server/Station Hardware .................................................................................................58Distributed Server Architecture (DSA) Licenses .................................................................................58PlantScape Process Server Software.................................................................................................59PlantScape Process Server Software – Redundancy Options ...........................................................60PlantScape Software Options and Tools ............................................................................................61SCADA to Process Server Conversion Software................................................................................63PlantScape Documentation ................................................................................................................64PlantScape Demonstration Unit..........................................................................................................65

Appendix A: Server Hardware Requirements .................................................................66

Ver 1.0 PS03-132Release 320 Page 3


Revision Status

Revision Date Description

0.1 March 2000 Draft

1.0 27 October 2000 Final version; updated AIOM limits



Introduction

ntroducing the Honeywell PlantScape family of process control solutions from Honeywell.PlantScape is a cost-effective open control system for batch, process and SCADA applications. The

PlantScape family includes the PlantScape Process System, the PlantScape SCADA System andPlantScape Vista. The award-winning PlantScape system sets a new standard in scalable hybridcontrol systems by providing the highest level of performance, flexibility, and ease of use at the lowestlife-cycle cost of ownership.

The heart of the PlantScape family is a powerful, open Microsoft Windows NT-based client/serversystem. Its advanced architecture encompasses a new, high-performance controller, advancedengineering tools, and an open control network. PlantScape makes use of new technology thatincludes:

• a powerful Microsoft Windows NT-based Server with dynamic data caching, alarming,human/machine interface, history collection, and reporting functions;

• a compact Hybrid Controller that provides truly integrated control;• object-oriented tools to quickly and easily build reusable control strategies;• ControlNet, an open, state-of-the-art producer/consumer control network; and• secure Internet browser technology for on-line documentation and support.

With PlantScape, the user configures the system instead of building it from scratch. Most industrialprocess control applications call for a number of common elements, such as communicationsprotocols and control algorithms. PlantScape includes such elements in its standard operatingframework, allowing the user to concentrate on the application, not the system.

The PlantScape system allows operation to begin as soon as point and hardware configuration iscomplete, with a minimum of system building required. With PlantScape, the user is up and running inminimum time!

Product Overview

PlantScape enables increased engineering productivity through graphical object-based tools and a fulllibrary of powerful process control functions. It addresses world-wide regulations and practices in theprocess industries and adapts to local language and interfacing customs. The basic systemcomponents of PlantScape are:

• Hybrid Process Controller for integrated process and discrete control• C200 Control Processor• Redundant or Non-redundant configuration options• 50 msec or 5 msec Control Execution Environments• FOUNDATION Fieldbus Device Interface• Flexible, compact I/O family with optional Remote Termination Panels• Galvanically Isolated/Intrinsically Safe I/O for hazardous area requirements• Integration with Allen-Bradley PLC5/C and Logix 5550 Programmable Logic

Controllers• PlantScape Performance Process or SCADA Server PC/NT

• Redundant or Non-redundant configuration options• Large Selection of third-party controller drivers• Distributed Server Architecture for plant-wide and geographically distributed

systems• PlantScape Station Human Machine Interface (HMI)

• Rotary or permanent stations for maximum flexibility and cost-effectiveness• High resolution graphical operator interface• Chart Visualization: a run-time monitoring display for loaded Sequences

• PlantScape Software

I



• PlantScape Process, SCADA and Vista options to cover all user needs• Control Builder with Comprehensive Control Libraries for process point

building and Multiple Workstation use• Display Builder for powerful operator graphic creation• Knowledge Builder On-Line HTML-Based Documentation• Discrete Logic Tools and Configuration Utilities

• Process Control Networks• ControlNet - supports redundant media for high system robustness• Ethernet - for flexibility based on open technology

The Hybrid Process Controller architecture, featuring the C200 Control Processor, handles a widevariety of requirements, including continuous processes, batch processes, discrete operations, andmachine control needs. Compact and cost-effective, the C200 is ideal for integrated regulatory, fastlogic, sequential, and batch control applications. Control functions are provided through a library oftemplates called Function Blocks (FBs). Strategies are easily built using a state-of-the-art graphicalengineering tool called Control Builder. Once built, control strategies can be loaded and monitoredusing Control Builder.

Figure 1. PlantScape System Architecture

The Hybrid Process Controller supports ControlNet Interoperability, the capability to communicatewith Allen-Bradley controllers like the PLC-5, the Logix 5550 and other ControlNet devices. This allowscomplete integration of high-speed logic with process control applications. The PlantScape Serverprovides monitoring and supervisory control of these devices.

High AlarmLow AlarmComm . Err.

LAN (TCP/IP, Ethernet, etc.)

PlantScapeProcessServer

PlantScapeStation

Chassis I/O -Series A

C200 HybridProcess

Controllers

AnalogDigitalRTD &ThermocoupleSerialPulse

ControlNet (redundant media)

Co

ntr

olN

et

Honeywell - S9000, LCS620, TDC3000,

FSC, UDC, 7800, DPRAllen-Bradley

OPC Client & ServerModicon (Modbus +)

GE FanucFieldbus

and many more!

Control Solver50 msec and 5 msec

Co

ntr

olN

et

A-B PLC5/C A-B Logix 5550

PlantScapeSCADAServer

Co

ntr

olN

et

Fieldbus Linking Devices

GI/IS Rail I/O - Series H

Fiber OpticIsolation

Fiber OpticIsolation

Hazardous Area

��

��

��

��

H1

H1

��

H1

H1

ServerControl Builder

Knowledge BuilderDocumentation

Fieldbus Configuration

��

H1

H1

FOUNDATION Fieldbus Devices

Rail I/O - Series A


System Overview

The PlantScape system is a tightly integrated, scalable hybrid control system which represents thebest available technologies and is functionally differentiated against PC software and PLC(Programmable Logic Controllers) systems.

PlantScape system features include:

Figure 2. PlantScape Features Object-Based Graphics with Powerful Features Like DisplayScripting and Active-X Support


• Integrated Database -- Control Builder configuration includes information for both the Controller andPlantScape Server. Information is entered once, not repeated in several databases.

• Integrated Alarms and Events -- Alarms are configured by Control Builder, generated by the ControllerProcessor, recorded into the event system, and acknowledged by operators on the PlantScape OperatorStation alarm summary display. Users do not have to separately configure process alarms in both thecontroller and the supervisory system.

• Point Detail Displays – Standard Detail displays for points are an example of the 300 standard displays thatare included with the system. Users can operate from these displays or, if they choose, create customdisplays. PlantScape provides maximum usability and flexibility at the same time!

• Integrated On-line Documentation -- The PlantScape system gives users quick access to systeminformation and support using the latest Internet technologies. It features SafeBrowse , Internet-awareHTML (hypertext markup language) documentation, on-line help and on-line technical support. Users won’tneed to search through multiple sets of documentation. SiteDocs allows users to add links to site specificelectronic documentation within Knowledge Builder.

• Integrated Network Support:

• ControlNet: a realtime open Deterministic process control Network , features deterministic datadelivery optimised for real-time process control via single or redundant media.

• Ethernet: a commercial off-the-shelf network solution which allows controllers to connect to the serverwith standard available technology.



• Real-time Database – The server features a true Client/Server architecture where a real-time database onthe server provides data to a number of client applications including:

• operator stations• third party applications (such as Microsoft Excel, Microsoft Access, LIC Energy)• web pages

• Open Systems – PlantScape incorporates the latest open technologies and standards including ODBC,AdvanceDDE, Visual Basic and OLE for Process Control (OPC) to make implementation simple.

• FOUNDATION Fieldbus Interface – FOUNDATION Fieldbus measurement and actuation devices can beintegrated into PlantScape regulatory, sequential and logic control operation. A ControlNet to FOUNDATION

FIELDBUS Linking Device allows the powerful PlantScape Controller to interface with Fieldbus devices, suchas valves, transmitters and sensors.

• Distributed Server Architecture -- With PlantScape's Distributed Server Architecture, multiple PlantScapesystems can operate as one – within a single plant, or across the world - without any duplication ofengineering effort. Distributed Server Architecture has been designed to handle the most stringent remoterequirements over slower wide-area networks, and as a result, deliver extremely high performance over localhigher speed plant networks.

• Advanced System Infrastructure – PlantScape includes a complete infrastructure that includes, ancomplete alarm/event management subsystem, easy to configure reports, extensive history collection and avariety of standard system trends.

The PlantScape Process system provides a uniquely integrated system solution consisting of thePlantScape Server, PlantScape Station and Hybrid Controller on ControlNet or Ethernet. Ratherthan just another controller, the Hybrid Controller is the focal control engine of this highly integratedsystem. Server, Station and Hybrid Controller components were designed to perform as a singlehighly optimized system, providing functions and efficiencies which are not generally available inloosely coupled human machine interface (HMI)/programmable logic controller (PLC) style systems.

Another unique aspect of this system is its ability to directly integrate existing automation or SCADA(Supervisory Control and Data Acquisition) networks, without the need for special gateways. This

Figure 3. Control Builder Supports a Powerful Set of Algorithm Libraries for ImplementingProcess Control Strategies



latter system functionality can also be purchased alone as PlantScape SCADA, where the applicationdoes not involve the Hybrid Controller.

PlantScape SCADA system provides cost-effective integration for a wide range of 3rd party PLCs,controllers, Honeywell modular controllers and field instrument products. Applications range fromsingle-user HMI for a few points up to full scale SCADA systems consisting of tens of thousands ofpoints and up to 40 connected Stations. The key elements of PlantScape SCADA are the PlantScapeServer and PlantScape Station. PlantScape Station can run in either Windows NT or Windows95/98.

The PlantScape System includes a very powerful supervisory control and networking system, withfeatures such as:

• Integrated detail displays, custom graphics, alarms, history, and reports• Multiple operator stations per Server with optional remote modem access• Redundant NT-based server operation• Operation of non-PlantScape controllers• A common interface for SCADA, process and discrete control• Database and diagnostic integration with process and discrete controllers.• Leading edge graphical building tools• Standard and user-definable application templates• Natural hierarchical control building environment• Full self-documenting control strategies• Identical engineer and operator view for on-line monitoring• International system and local language support• Optional applications such as Alarm Pager interface, Downtime Analysis• Chart Visualization: a run-time monitoring display for loaded Sequences



Product Description

Control Processor Modules

The Hybrid Controller with C200 ControlProcessor option, shown in Figure 4, consistsof a Chassis (Rack), Power Supply, ControlProcessor, ControlNet Interface, RedundancyModule, Ethernet Module and I/O Modules. Anoptional Battery Extension Module (not shown)is also available. The Chassis is available in 5sizes - 4, 7, 10, 13, and 17 slots. All modulescan be removed and inserted under power. Allcomponents are available with conformalcoating for maximum environmental protection.

The Power Supply ❶ is separate from theRack and does not consume any slots. It ismounted on the left end of the Rack. Both120/240 VAC and 24 VDC supplies areavailable.

The C200 Control Processor Module ❷ is adouble wide, two-board assembly featuring a 100 MHz PowerPC 603E processor and eight (8) Mbytesof RAM with error detection and correction. It supports both non-redundant and redundant controllerconfigurations. Four (4) Mbytes of parity-protected Flash ROM is used for permanent program storageand allows easy upgrades. A built-in lithium battery backs up the controller database, and an optionalone-slot wide Battery Extension Module provides a rechargeable option instead of replacing the lithiumbattery.

The PlantScape Server communicates to the controller along a ControlNet or an Ethernet Network.The ControlNet Interface (CNI) ❸ links the Controller with either of two ControlNet Process ControlNetworks. ControlNet is a flexible, high performance network supporting Supervisory/Peer(controllers to HMI), Peer-to-Peer and I/O Network communications. It is an open network for whichthe specification is owned and managed by ControlNet International, of which Honeywell is a foundingmember. Data throughput is 5 Mbits/sec. via single or redundant media options and featuresdeterministic data delivery. The physical media is RG6 coaxial with BNC connectors in a trunk-and-drop, bus topology. The total possible network length is 10 km, using fiber optic repeaters, and 6 km,using coax cable and repeaters. The maximum coax network segment length is 1 km (dependent onnumber of taps and drops), and the maximum fiber network segment length is 3 km (dependent onfiber grade). Each Supervisory/Peer Network segment supports up to 10 non-redundant or 10redundant controllers. Each Control Processor can connect to up to 8 I/O chassis via the I/O Network.

The Ethernet Module ❹ supports Ethernet communication from the Server to the Supervisory ControlNetwork and provides a peer to peer network for interoperability. External devices can communicatewith the Hybrid Controller through the Ethernet network. This is an open network built with off-the-shelfPC hardware and is a familiar and efficient mode of communication. It can easily overcome distancesbetween locations and currently requires a switched network topology for 10MB TCP/IP support. Themodule provides a 10BastT Ethernet Cable connector and supports one segment as a supervisorynetwork (with no routers). Ethernet Modules are not used with Redundancy Modules.

For Control Processor redundancy, the Redundancy Module ❺ provides redundancy between twocontroller chassis. Synchronization of primary and secondary is completely transparent to the user,and control switchover time in the event of a system failure is negligible. The Redundancy Module(RM), which connects to its redundant partner via fiber optic cable, can be replaced on-line withoutdisrupting control of the user’s process. The following are some of the important features of the RM:

Figure 4. Hybrid Controller & Chassis I/O Format

1 5

3 3

2

1

3

2

4



• Transparency of Synchronization -- Control chassis synchronization does not cause any user perceivedcontrol interruption. The redundant control system automatically synchronizes a secondary solely bypowering up a properly cabled and populated secondary control chassis.

• Transparency of Switchover -- The occurrence of switchover of the control chassis is unnoticeable to theoperator, unless triggered by an alarm or an event. Control interruption time is negligible.

• User Commanded Switchover -- The user can force a switchover condition if desired.• Guaranteed Store - Communication transfers are not acknowledged as successful unless both the primary

and a synchronized secondary (if present) both receive the message.• Output Coherency on Switchover -- All outputs remain unchanged during a switchover with no bump to the

process. Switchover does not cause outputs to revert to a prior value.• Reaction to Impending Chassis Power Loss – Upon detection of power loss, the RM (a) notifies its

partner and initiates a switchover, (b) records the power loss event in its non-volatile event log and (c) haltsnormal operations to prevent memory corruption.

• Fault Isolation -- A single fault does not propagate from a control chassis to its partner to cause the controlsystem to cease to control properly.

• One Module Design -- C200 modules can be used either with or without the RM for both non-redundant andredundant applications.

• Partner Failure Diagnosis -- The cause of a failure in one controller chassis can be diagnosed from theRM in its partner chassis.

• RM On-Line Replacement -- The RM can be replaced on-line without disrupting control of the user process.

The New FOUNDATION Fieldbus Linking Device interfaces the FOUNDATION Fieldbus H1 network withthe PlantScape Hybrid Controller via ControlNet. This allows each Controller to access data andcontrol Fieldbus devices, enhancing the power of PlantScape’s Controller.

The controller, I/O system and all of its components are approved for mounting in Class I, Division 2,Groups A, B, C, and D areas and fully meet stringent industrial CE-Mark (European Community)immunity and emissions requirements.



Input/Output Modules

Honeywell offers three families ofI/O:• CIOM-A: Chassis mounted

I/O Series A• RIOM-A: Rail mounted I/O

Series A• RIOM-H: Rail mounted I/O

Series H, for use in Div 1/Zone1 Hazardous locations

Chassis – Series A I/Omodules are a rack-mounted(chassis) family of I/O available ina wide variety of densities.Modules have a small form factor(5” x 5”) and feature deterministicI/O update rates, diagnosticsfeatures, local (front of module)or remote terminations, andsoftware configuration/management support. Available modules and specifications are listed in PS03-232, PlantScape I/O Specification and Technical Data.

RIOM-A modules clip to standard DIN-Rails to provide easy and cost effective remote I/O installations.One ControlNet Gateway (Redundant or Single media versions) will provide access to up to eight I/OModules in any combination of AI, AO, DI, or DO types. The Modules are compact and can bemounted horizontally or vertically. An optional bus extender cable allows for even greater mountingflexibility. The RIOM-A line consists of ControlNet adapters, power supplies, terminal base units andI/O modules, all designed to lower installation, wiring, and maintenance costs. Additional information isavailable in the PS03-632, PlantScape Rail - Series A I/O Specification and Technical Data.

Rail - Series H Galvanic Isolation/Intrinsic Safety (GI/IS) I/O modules provides a compact family ofI/O that can be mounted and operated in areas with potentially explosive (Ex) atmospheres. All SeriesH components are certified and can easily be distributed throughout a given hazardous location. Referto PS03-531, Rail I/O Modules Series H Specification and Technical Data, for hazardous locationclassification and I/O details. Corrosion protection to test level G3, according to ISA-S71.04-1985, is astandard feature of Series H I/O components. Additional information is available in the PS03-532,PlantScape Rail - Series H I/O Specification and Technical Data.

Corrosion Protection. Corrosion is one of the leading failure mechanisms of electronic boards inharsh environments. In order to insure the maximum possible reliability in such environments,Honeywell has gone the extra step by providing an optional conformal coating solution. All RIOM - HI/O modules and designated CIOM-A modules are conformally coated with a protective layer designedto safeguard the electronic components against corrosion in harsh environments. Other systemcomponents, such as racks, power supplies, controllers, etc., are available with or without optionalcoating.

CIOM-A (Chassis I/O Series-A)

RIOM-A (Rail I/O Series-A)

RIOM-H (Rail I/O Series-H)

Hazardous Area



When the coated option is selected, all control and I/O components are capable of withstanding a G3or Harsh environment. This Harsh environment is defined by ANSI/ISA-S71.04-1985, “EnvironmentalConditions for Process Measurement and Control Systems: Airborne Contaminates,” as shown inTable 1. The coating option will thus dramatically improve the system reliability in those situationswhere a well-controlled environment is not possible.

Table 1. Definitions from ANSI/ISA-S71.04-1985 -- "Environmental Conditions for ProcessMeasurement and Control Systems: Airborne Contaminants"

Severity Level G1Mild

G2Moderate

G3Harsh

GXSevere

Copper Reactivity Level (angstroms) < 300 < 1,000 < 2,000 ≥≥≥≥ 2,000

Contaminant Gas Concentration (parts/billion)

H2S < 3 < 10 < 50 ≥≥≥≥ 50SO2, SO3 < 10 < 100 < 300 ≥≥≥≥ 300Cl2 < 1 < 2 < 10 ≥≥≥≥ 10

Group A

NOX < 50 < 125 < 1,250 ≥≥≥≥ 1,250

HF < 1 < 2 < 10 ≥≥≥≥ 10NH3 < 500 < 10,000 < 25,000 ≥≥≥≥ 25,000

Group B

O3 < 2 < 25 < 100 ≥≥≥≥ 100

Gas concentrations are for reference purpose only and are believed to approximate the reactivity levelsassuming relative humidity is less that 50%. For each 10% increase in relative humidity above 50%, orchange in relative humidity by greater then 6%/hr, the severity level can be expected to increase by onelevel.

Conformal coating is recommended for any installations for which the ambient environment meetseither Moderate (G2) or Harsh (G3) conditions. PlantScape Systems installed and maintained in a Mild(G1) control room environment (defined by the Classifications shown above) do not need this addedlevel of protection. For those installations where the ambient environment exceeds Harsh (G3)conditions, it is recommended that the system components be both conformally coated and mounted ina sealed enclosure. Purging adds an even greater degree of protection.

In the above specification, Copper Reactivity Level refers to the amount (thickness) of corrosion whichaccumulates on a copper test coupon over a period of one month. Gas concentrations listed are forreference purpose only and are believed to approximate the listed Severity Levels assuming a relativehumidity of less than 50%. The Severity Level of an area can only be measured by a copper coupontest (or by a suitable corrosion monitor); it cannot be determined by measuring concentrations ofgasses and humidity. Note that an increase in relative humidity above 50% as well as a relativehumidity rate of change of more than 6% per hour can drastically increase the Severity Level.

Control Processor Functions -- Control Builder and Control Solver

Control Builder is a graphical object-oriented development software package, supporting PlantScapeC200 Controller system design, documentation, and monitoring. It provides a comprehensive set oftools for handling I/O, continuous, logic, motor, sequential, batch and advanced control functionsthrough a library of Function Blocks (FBs). FBs are basic objects provided by Honeywell to executedifferent control functions. Each block supports parameters that provide an external view of what theblock is doing. FBs easily interconnect via “soft wires” to construct control applications or strategies.

Function Blocks are grouped together and contained in Control Modules (CMs) and, in the case ofsequential FBs, Sequential Control Modules (SCMs). SCMs greatly simplify batch logicimplementation by sequencing a group of process equipment through a series of distinct steps toaccomplish one or more process tasks. CMs and SCMs act as “containers” for Function Blocks.This is a very powerful tool for creating, organizing, and checking out control strategies. Figure 6



illustrates a simple Control Module -- in this case a PID loop -- made up of basic FBs. Note that in thisexample four FBs are “contained” within the CM named FIC105. Each Control Module may bescheduled at its own execution rate from 5 msec to 2 sec, and the user can schedule Function Blocksand Control Modules to execute in any desired order.

Control Builder enhances engineering productivity by enabling “top-down” implementation, enabling thecreation of reusable control strategies. Control Builder uses icons to represent control blocks whichcan be “wired” together using simple point and click techniques. Control drawings can be used on-lineto monitor control execution and make changes to control parameters, thereby significantly simplifyingcontrol strategy checkout. Control Builder also allows templates to be created, modified and reused sothat control strategies can be built and duplicated with a minimum of effort.

Control functions currently supported in the PlantScape Control Builder Libraries are listed in theSpecifications section. Types of functions blocks include Process Variable, Regulatory Control,Fieldbus Integration, Device (Motor) Control, Discrete Logic and Sequential Control, as well as general

purpose blocks like Flags, Numerics,Timers and Arrays. Additional functionlibraries are available as well. Thebuilt-in capabilities of the ControlSolver execution environment enableusers to take advantage of these libraryoptions.

Due to its rich set of standard features,SCMs greatly simplify Batch logicimplementation. In addition, the SCMimplementation follows the S88.01standard. Standard features includeabnormal handling, providing analternative sequence execution for userspecified abnormal conditions.Abnormal handlers support restartcapabilities, re-starting the sequencefrom the position it was left or any otherStep the process requires to continue.Standard Abnormal handlers include:Checking, Interrupt, Restart, Hold, Stopand Abort. Each Sequence supports upto 50 recipe parameters, each with arange, material code and scale option

and 50 history parameters for actual dosed material or reached temperatures. The mode track optionallows for different operating philosophies. Devices, such as motors, pumps, and controllers, willfollow SCM mode changes allowing either operator or sequence device control. The devices can alsobe pre-configured with the action required after an SCM start, abnormal situation or restart. Thisreduces the SCM step configuration.

For example, a Common SCM can be implemented for a header dosing application. This is a specialSCM that can be operated on different equipment units depending upon the selected unit instance. Itsaves implementation, test and maintenance time required to support the application. SCMs are fullyintegrated with our TotalPlant Batch package for flexible batch operation

Control Builder also supports a multi-user control strategy development and debugging environment.The function provides remote access to engineering databases across any media capable of TCP/IPand UDP/IP communication. For maximum security, access is password protected. Several userscan create, configure and load control strategies at the same time from different workstations. Multipleusers can have the same chart open, with full write access to the first user who opens a chart.

Figure 6. Simple Control Module Example



When multiple users open a chart for monitoring, all users can change controller values based on theirsecurity level.

The Control Solver Control Execution Environment (CEE) is the execution and schedulingenvironment for the C200 Control Processor. It is available in two base execution rates, 50 msec(normal) and 5 msec (fast). CEE is the underlying support layer for the execution of all controlfunctions. It features:

• Individual per-module selectable execution rates of 50, 100, 200, 500, 1000 and 2000 msec for the 50msec CEE and 5, 10, 20, 50, 100 and 200 ms for the 5 msec CEE. All Control Modules and SequentialControl Modules, regardless of function block content, can, in each case, execute at any of these 6 rates.Note that all function blocks within a CM or SCM execute at the same rate.

• Configurable phase assignment of any modules executing slower than the base rate. This provides theability to “load balance” a Control Processor.

• Peer-to-peer communication between C200 Control Processors. Implementation is transparent so thatpeer-to-peer connections are configured in the same way as intra-controller connections.

The Fieldbus Configuration Tools integrate the Hybrid Controller with Fieldbus devices. Keyfeatures include:• Communication through the ControlNet path from the PlantScape Server• Block and Device tag and address setting• An easy-to-use graphical environment for creating linkages, loops and a schedule based upon Fieldbus

concepts.• Configuration of hardware information, ControlNet nework addressing, Linking Device paths, Device

descriptions, and the base directory to store Device Description information.

Control Processor Load Performance

The Control Processor provides a very flexible execution environment for performing all types ofcontrol at different execution speeds. To determine how much control can be performed by aProcessor, Processor Usage and Memory Usage are considered. The number of modules orblocks a Control Processor can execute is determined by available CPU and memory resources.Other constraints, such as total number of CMs and SCMs, must also be taken into account.

PlantScape is designed for a wide variety of applications. System Performance and CapacitySpecifications are given in the Models and Specifications section. These specifications should bereviewed to ensure that PlantScape will meet the application requirements. Table 2 represents anexample non-redundant C200 configuration (not necessarily typical). Refer to Table 7.14 for adescription of the Function Block content of each module type.



Table 2. C200 Controller (Non-Redundant, 50 msec CEE) Capacity, SampleConfiguration

Module Type No. ofModules

Period,sec

ModulePU

ModuleMU

Total PUs* TotalMUs

I/O Module (64 max) 40 0.05 0.3 0.6 240 24Analog Data Acquisition CM 20 1 2.9 7.4 58 148Small Analog Data Acq. CM 10 2 0.47 1.0 2.35 10Regulatory Control CM 100 0.5 2.8 3.9 560 390Auxiliary Function CM 10 0.5 4.2 13.1 84 131Digital Data Acquisition CM 20 0.1 1.2 3.1 240 62Small Digital Data Acq. CM 10 0.1 0.22 0.6 22 6Device Control CM 140 0.1 1.3 3.1 1820 434Logic Control CM 10 0.1 1.0 3.5 100 35Sequential Control Module (SCM) 50 1 2.0 55 100 2750

Total 3226 3990Max 3600/1600** 4000

PU = Processing Unit per Control Cycle; MU = Memory Unit, KbytesPUs for any given CM = (PU per Cycle) / (Cycle Time, sec.)

*Total PUs = (No. of Modules) x (Module PU) / (Period, sec.) for each CM type.Available Period for all CM and SCM types are 0.05, 0.1, 0.2, 0.5, 1.0 and 2.0 sec. I/O Modules fixed at 0.05 sec.**Total PUs for Non-Redundant/Redundant Control Processors (Module PUs apply to non-redundant only).

Peer-to-Peer CommunicationCEE to CEE peer-to-peer allows data to be shared among separate Control Processors irrespectiveof controller location within a Server domain (i.e., within a Supervisory/Peer ControlNet). If aconnection can legitimately be formed between two function blocks within the same controller, thenthat same connection is permitted between two of the same type of function blocks, which are inseparate controllers. All data connections are done via data “pulls.” The only data “push” allowed inPlantScape is the output expression of a Sequential Control Module Step function block. PlantScapeprovides end point fail safe data protection and handling. Connections are protected againstfailures and abnormal conditions by always receiving either live-process data or fail-safe data.

CEE to PLC peer-to-peer allows exchange of data on a controller level between a Control Processorand PLC’s or other devices. The Exchange FBs support both the PCCC (Programmable ControllerCommunications Commands) and CIP (Control and Information Protocol). The data is stored in theexchange FBs and can be used in any control strategy. The Exchange FBs can also be used toexchange data between two Control processors, which are not within the same name space of a singlePlantScape system, because these protocols support direct ControlNet addressing.

Table 7.8 contains peer-to-peer performance information. In order to maximize the number ofsubscription items and allow for some spares, it is best to choose the slowest subscription rate neededfor a given controller’s application.



PlantScape System Overview

PlantScape is a modular, supervisory control and networkingsystem designed around a high performance, Microsoft WindowsNT-based operating system. All components of this system arefully integrated. For example, when a user-built Control Module isloaded, appropriate data is automatically loaded to both the C200Control Processor and the PlantScape Server database. A Serverdatabase point is built for each named block. Features likenavigation tools and integrated alarming give the system aconsistent look and feel from the controller to the Operator Station.Consistent tag names are used in the Hybrid Controller and in thePlantScape Server. A dynamically scheduled cache in theServer gathers all data requests into request lists, providing optimaldata access performance and memory utilization while minimizingthe data access load on the Hybrid Control Processor.

The PlantScape System incorporates leading edge, open-systemtechnologies, such as Microsoft Windows NT, Ethernet, TCP/IPand standard Intel-based PC hardware to provide comprehensive facilities in an economical and easyto use package. By optimally combining a comprehensive set of supervisory functions with the controlcapabilities of the Hybrid Controller, the PlantScape architecture enables simplified operation andengineering in a fully integrated system environment.

Figure 8. Hybrid Controller Points Built Using Control BuilderBecome Immediately Accessible to the Operator via Standard Displays

Figure 7.PlantScape Process Server



The PlantScape architecture ensures that the user has complete and transparent access toHybrid Controller database. PlantScape also integrates with a wide range of other Honeywell andthird-party devices, thereby leveraging existing control investments and enabling complete integrationof process information. Process information is accessible by operators, process engineers andMIS level computers, allowing control and monitoring for higher productivity, reductions in costs,higher product consistency, and less waste.

PlantScape System Philosophy

PlantScape is designed around a solid, but flexible system framework. The framework is aimed atproviding the following key productivity benefits for the users and implementers of the system:

• Operational Ease of Use and Consistency• Engineering Ease of Use• Speed of Engineering Implementation

With PlantScape, the user simply configures the system instead of building the system from scratch.Even though a diverse range of applications exist in the industrial process market, many commonelements are required for most systems. PlantScape simply includes such elements in its standardoperating framework, allowing the user to concentrate on the application, not the system.

The standard PlantScape system allows operation to begin as soon as point and hardwareconfiguration is complete, with no further system building required. Once PlantScape is populated withthe user’s point data, a number of standard displays and other facilities are available, such as:

• Alarm Summary Displays

• Event Summary Display

• Operating Group Displays

• Trend Displays

• Loop Tuning Displays

• Diagnostic Displays

• Display Summary

• Standard Reports

• Pre-defined Composite Points

• Composite Point Detail Displays

• Point Processing Algorithms

• Pre-configured push buttons/toolbar for all key functions

• Pull-down and Screen-based Menus

• Most recent/urgent alarm field on all displays

• Standard Status Bar on all displays

• Chart Visualization: a run-time monitoring display for loaded Sequences

PlantScape provides many standard facilities, yet is extremely flexible, allowing the user to modify orextend standard functionality where required. All standard displays, for example, are modifiable by theuser. This means the user is up and running in minimum time!



PlantScape Server Key Features

Standard facilities include:

• Windows NT-based server and Windows NT or Windows 95/98 based human machineinterface

• Multiple local and remote operator stations• FOUNDATION Fieldbus Interface• Complete server redundancy• Support for redundant controller/RTU communications• Integration of multiple systems using Distributed Server Architecture• Real-time data access for a wide variety of process connected devices• Supervisory data acquisition and control of controllers and remote terminal units• Powerful alarm management• Extensive historization and trending• Flexible standard or customized reports• Live video integration• Industry standard local and wide area network integration• Secure data integration with third party applications• Rich application development environment• ActiveX Document and Scripting support• Secure HTML access within Station window via SafeBrowse

Operator Interface

State of the art, objectbased graphics providea powerful interface forthe user. The use ofindustry standards,such as MicrosoftWindows NT, Windows95/98, and the Internet,minimizes operatortraining by providing afamiliar operatingenvironment.

Extensive use of userconfigurable pull-downmenus and toolbarsallow easy, intuitivenavigation and fastaccess to key processdata. The usability ofthe operator interface isfurther enhanced withfeatures such as lastcommand recall, copyand paste, live videointegration, ActiveXdocuments, scripting,launching applicationsand support forstandard peripheralssuch as:

Figure 9. PlantScape Main Menu



• sound cards,• touch screens,• dual screens video cards, and• trackballs.

Critical information is conveyed using dedicated annunciators for alarms, controller communicationfailures, operator/controller messages and equipment downtime conditions. A dedicated alarm line atthe bottom of each graphic shows the most recent (or oldest) highest priority, unacknowledged alarmat all times.

Standard system displays make it easy for operators to learn and use the system. An extensiverange of standard displays is available including:

• Menu/navigation displays • Alarm summary• Event summary • Trends• Operating groups • Point details• System status displays • Configuration displays• Loop Tuning displays • Diagnostic and maintenance displays• Summary displays

Live video integration is an important feature where remote sites may be unmanned. PlantScape notonly allows the operator to view live video from remote locations but also provides the ability to switchcameras, and pan, tilt or zoom the camera to focus in on a particular area. An alternative to live videois WebCam. WebCam allows a CCTV camera to be connected to the Ethernet, and is thereforeavailable to all operator stations via SafeBrowse.

SafeBrowse allows the user to securely browse either the Intranet or Internet. This allows the systemto view corporate documents, such as Standard Operating Procedures from across the world, or tokeep operators informed of relevant product information. SafeBrowse has three levels of security:

• Unrestricted• Restricted (limited to certain URLs)• No Access

Rotary Connected Stations permit any number of operator stations on a network to share apreconfigured number of connections to a PlantScape system. This allows a large number of users ona network to access production data on a part-time basis.

Real-Time Database

The PlantScape SCADA real-time database provides the following standard system structures:• Analog Point Structure• Status Point Structure• Accumulator Point Structure• User Defined Structure

Each point in the database has a number of associated parameters, all of which can be referencedrelative to a single tag name or ‘composite point’.

PlantScape maintains the real time database that requires frequent high-speed access as memoryresident information and other less frequently accessed data as disk resident data. Memory residentdata is checkpointed to disk every minute to minimize loss of data in the event of loss of power.



Analog Point Database

Analog points include the following parameters:

! Point Name ! Point Description ! Control Deadband! Process Variable ! Setpoint ! Normal Mode! Output ! Mode ! SP High Limit! Up to 4 user definable inputs ! Scan Status ! OP High Limit! Scan Period ! Scan Address ! Control Timeout! Alarm Permit Flag ! Alarm Status ! Up to 4 Alarm types! Alarm Status ! Associated Display ! SP Low Limit! 0% & 100% Range ! Operator Control Level ! OP Low Limit! PV Clamp Flag ! Engineering Units ! Drift Deadband! Alarm Deadband

Status Point Database

The PV of a status point can range from a single bit to a three bit digital input, allowing up to eightpossible states. Status points include the following parameters:

! Point Name ! Point Description ! Output Width! Process Variable ! Output ! Control Failure Alarm Priority! Mode ! Scan Status ! Normal Mode! Scan Period ! Scan Address ! Operator Control Level! Alarm Permit Flag ! Alarm Priority ! Output Pulse Width! Re-Alarm Status ! Associated Display ! Control Timeout! Input Width

Accumulator Point Database

Data associated with pulsed inputs are stored in the system in an accumulator point type that willprovide automatic tracking of instrument rollover. Analog points include the following parameters:

! Point Name ! Point Description ! 0% & 100% Range! Process Variable ! Rollover Value ! Operator Control Level! Raw Counts ! Scale Value ! Up to 4 Alarm types! Meter Factor ! Scan Status ! Associated Display! Scan Period ! Scan Address ! Engineering Units! Alarm Permit Flag ! Alarm Status

Container Points

Container Points are used to support the building of Template Displays. A container point combines agroup of logically associated points into a single point structure. The parameters of a container pointare flexible, for example a container point could be built for a tank that includes the:! level! temperature! fill valve status! drain valve status! agitator status



Most recent,highest priority,unacknowledgedalarm

Annunciator

Filters

Figure 10. Standard Alarm Summary Display

User Defined Structure

In order to support other types of data such as user entered or calculated data from applicationprograms, PlantScape provide a User Definable Database area that is fully integrated into the system.Data contained in this database is accessible by:

• Custom Graphics• Custom Reports• Server based Application Programs• Network based Applications Programs• Composite points

Algorithms

In addition to standard point processing functions, the system allows additional processing through theuse of standard algorithms that may be attached to an analog, status or accumulator point. Functionsprovided by these algorithms include:

• arithmetic calculations• boolean calculation• maximum/minimum value• integration• run hours totalization• group alarm inhibit• report request• application program

request

Alarm/EventManagement

The PlantScape Systemprovides comprehensivealarm and event detection,management, andreporting facilities. One ofthe keys to operatoreffectiveness is presentationof alarm information. Manytools are provided to quicklytarget the process problems,including:

• Multiple alarm priorities• Dedicated alarm zone• Associated display• Audible alarms• Alarm cutout• Area assignment• Operator log• Hierarchical alarming• Alarm/event reporting• Alarm/communication/ message/downtime annunciator• Alarm priority escalation

The standard Alarm Summary display allows operators to focus in on the problem at hand bysupporting filters. Alarms may be filtered by:

• Area• Acknowledge Status



Figure 11. Standard Multiplot Trend Display

• Priority

Alarms on the Alarm Summary display can be acknowledged either individually or per page. Oncustom graphics, alarms can similarly be acknowledged on an individual or per page basis. Thestandard point alarm behavior is the alarm will flash red if unacknowledged and in alarm and be steadyred if acknowledged, yet still in the alarm condition.

Up to 4 alarms can be configured for a point. Supported alarms include:• PV Hi• PV Lo• PV HiHi• PV LoLo• Deviation Hi• Deviation Lo• Rate of Change

Each of the configured alarms can be assigned a priority ranging from Journal, Low, High to Urgent. Inaddition to the configurable alarms PlantScape supports, a range of other point alarms includingControl Fail and Control Timeout.

The Event Summary list events that occur in the system, including:• Alarms• Alarm Acknowledgments• Return to Normal• Operator Control Actions• Operator Login & Security Level Changes• On-line Database Modifications• Communications Alarms• System Restart Messages

Up to 30,000 events may be stored in the Event Summary. The extended Event archiving optionenables up to one million events tobe stored online, in addition theevents can be archived to removablemedia for access at a later date.

Historization

History collection is available overa wide range of frequencies in bothaverage and snapshot/productionformats. A large amount of historycan be retained on line, withautomatic archiving allowingretention of and access to unlimitedquantities of historical data.

The default history collectionintervals are:

• 5 second snapshot• 1 minute snapshot• 1 hour snapshot• 8 hour snapshot• 24 hour snapshot• 6 minute average• 1 hour average• 8 hour average• 24 hour average

Once collected historical data is available for use by trend facilities, custom displays, reports,application programs, spreadsheets and ODBC compliant databases. Archives can be stored on the



local hard drive, optical media, tapes, etc. Optionally, the user can also store history to TotalPlantUniformance. See Table 9 for history sizing specifications.

Trending

Flexible Trend Configuration allows trends to be configured on line as necessary by simply enteringthe point and selecting the parameter from the database. Any of the history collection intervals may beused as the basis. Standard trend types include:

• Single bar graphs• Dual bar graphs• Triple bar graphs• Multi-plot trends• Multi-range trends• X-Y scatter plots,• Numeric tables• S9000 and Micromax Set Point Program plots• Group trends

Functions provided for analyzing and manipulating data include:• Combination real-time/historical trending• Trend zooming, panning, and scrolling• Hairline readout• Declutter• Configurable trend density• Simple recall of archived history• Trend protection• Smart clipboard support for copy/paste of data

The declutter feature, for example, enables individual traces on multi-type trends to be temporarilydisabled for clearer viewing without requiring reconfiguration of the trace. Trends may be easilyconfigured on line through standard trend displays, without the need to build displays. Real-time andhistorical data are presented together on the same trend. Archived history may be accessedautomatically by simply scrolling to, or directly entering, the appropriate time and date.

Reporting

The supervisory system provides many built-in reporting functions. Standard report descriptionsinclude:

• Alarm/Event Log reports all alarms and events in a specified time period. By using filters, this reportprovides an operator and/or point trace facility.

• Alarm Duration Log reports the time of occurrence and elapsed time before return-to-normal for specificalarms in a specified time period.

• Integrated Excel Report provides the ability to launch a report built using Microsoft Excel in a similar wayto all other standard reports. Microsoft Excel can access the PlantScape database using the Open DataAccess option.

• Optional Downtime Analysis provides reports of downtime events sorted by category and/or reasoncodes.

• Free Format Report Writer generates reports in flexible formats, which may include math and statisticalfunctions such as Max/Min and standard deviation.

• Point Attribute Log reports on points displaying specific attributes, such as off-scan, bad data, and alarminhibit.

• Point Cross-Reference determines database references for specified points to enable easier systemmaintenance when points are decommissioned or renamed.

• ODBC Data Exchange Reports -- See the Application Enablers Section.

Reports may be generated periodically, or on an event-driven or demand basis and may be configuredon line. Report output may be directed to screen, printer, file, or directly to another computer foranalysis or viewing electronically.



Security

To maintain system security, PlantScape provides configurable security levels, control levels and areaassignments. These may be configured for each individual operator or alternatively for each operatorstation. Up to six security levels limit operator access to PlantScape functions:

Level 1: Signed-off modeLevel 2: View only mode with alarm acknowledgeLevel 3: Level 2 plus control of field parametersLevel 4: Level 3 plus field parameters of level 4, configure standard system infrastructure such

as reportsLevel 5: Level 4 plus user configured field parametersLevel 6: Unlimited access

Operator sign-on/sign-off security provides up to 255 control levels to limit operator control of individualitems of plant and equipment. Any actions initiated by an operator are logged in the Event database byan operator identifier. In addition any control actions to a given point is only allowed if the control levelconfigured in the operator profile exceeds the level assigned to the point.

An operator password consists of 5-6 alphanumeric characters and is encrypted. Operators maychange their own passwords, however a new password can’t be the same as the last 10 passwordsused in the previous 3 months. When signing on, three unsuccessful attempts will lock the operator outfor a lock-out period. Once signed on (logged on), an operator can sign off (log off) at any time or willbe automatically signed off after a defined period of inactivity.

Area assignments limit operator access to graphics, alarms and point data to assigned areas,providing effective plant partitioning. Individual operator profiles, including security levels, controllevels and area assignments, are activated when operators sign on to the system.

Interfaces

PlantScape provides Data Acquisition and Control facilities to communicate with a wide range ofcontrollers and RTUs. A list of controllers/RTU interfaces is shown in Table 3.

Data Acquisition – PlantScape supports acquisition of data using either:

• Periodic Scanning -- utilizing this technique, PlantScape optimizes communications traffic by automaticallycalculating the minimum number of scan packets required to collect the data.

• Report by Exception (RBE) – where supported by the controller, this technique is used to reduce thescanning load of the system while improving system response.

If necessary, periodic scanning may be used in conjunction with RBE to ensure data integrity.

On-line Configuration -- Given the sufficient level of system privilege, it is possible to view,manipulate and analyze all data in the system from any Operator Station in the system, including thoseoperating remotely via dial-up modem links.

Diagnostics -- Once a controller or RTU is configured and placed in service, PlantScape automaticallyperforms diagnostic scanning of the device. Additionally, PlantScape performs checks on data integrityof all data acquired from the controller. Should an invalid or timed-out response be received, the data isignored and the transaction is recorded as an error. Statistics are kept and displayed by the system oncommunication errors by means of a communications barometer. The barometer increments for everyfailed call and decrements for each successful call. In addition, the system alarms separate marginaland failure conditions based on user defined limits to advise the operator of a controller that is in error.Communications statistics are displayed on a standard system display and are available through thereporting sub-system or custom displays. If a controller fails, all point parameter values that aresourced from it are indicated as bad to the operator.



Table 3. Interfaces with Connection Details

Controller/RTU Connection type

Honeywell S9000 Ethernet Honeywell LCS620 Serial/Ethernet Honeywell Data Hiway Proprietary Honeywell UDC Serial Honeywell Micromax Serial Honeywell FlameSafeguard

Serial

Honeywell DPR Serial Honeywell XLNET CBus Honeywell FSC Serial and Ethernet Honeywell FS90 Serial Honeywell UMC Serial Allen Bradley SLC5/xx Serial/Ethernet/DH+ Allen Bradley PLC5 Serial/Ethernet/DH+/ControlNet Allen BradleyControlLogix

Serial/Ethernet/DH+/ControlNet

Modicon Serial/Modbus+ AdvanceDDE Open Standard OPC Client Open Standard Bristol Babcock DPC Serial SquareD Ethernet and Synet Siemens S5/S7 H1/Industrial Ethernet Yamatake HoneywellMA500

Serial

Moore Mycro Serial Moore APACS Ethernet & Modbus Fieldbus Open Standard GE Fanuc Series 90 Ethernet ASEA Serial Universal Modbus Serial/Modbus+ Applicom Proprietary Bailey Ethernet, SCSI & Serial Hitachi Serial

OPC Client -- The OPC Client capability allows information from third-party OPC servers to bemapped into SCADA point parameters in the PlantScape Server. This information is then able to bedisplayed, alarmed, historized and controlled. The OPC Client is based on V1.0a of the OPCspecification. For more information on the wide range of OPC Servers available seewww.opcfoundation.org.

Allen-Bradley Integration Interface - PlantScape is tightly integrated to the PLC5/SLC range ofcontrollers. For example, PlantScape provides standard diagnostic displays that are automaticallygenerated by the system. In addition any alarms, such as rack faults, major or minor faults, areautomatically alarmed in PlantScape’s standard alarm summary display. No configuration is required.PlantScape also has complete access to the A-B PD (PID Configuration) or Honeywell SmartTransmitter files by simply building a single point.

http://www.opcfoundation.org/



Figure 12. Redundant PlantScape SCADA Example

PrimaryServer

BackupServer

ClientStation

DataAcquisition

DatabaseCheckpoints

Screen Updates

Process/SCADAServer

Process/SCADAServer

Process/SCADAServer

Process/SCADAServer

Site A Site B Site C

Wide Area Network

Master Control Center

Figure 13. PlantScape Distributed Server Architecture

Server Redundancy

The PlantScape server canbe optionally redundant.The PlantScapeRedundancy subsystemprovides a high availabilityplatform by enabling a pairof similarly configuredPlantScape servers tosupport each other in aprimary/backup fashion.Should the Primary fail, afully functioning Backupassumes the Primary role.Primary refers to the specificPlantScape server which isactively acquiring data from the controllers/RTUs and serving data to the clients. The Primarypropagates all database transactions to the Backup over a redundant network so that both databasesremain in complete synchronization.

Distributed Server Architecture

Distributed Server Architecture is the ideal solution for integrating processes when there are multiplecontrol rooms, or for segmenting control across units, providing the ultimate flexibility for bothoperations and control. Distributed Server Architecture also provides the maximum flexibility forgeographically distributed sites. For example, it allows multi-segment pipelines and oil and gas fieldswith a large number of wells to be managed from multiple remote locations, as well as a central controlroom - Another industry first for PlantScape.

Figure 13 shows an example of a distributed system connected using a wide area network. The mastercontrol center accesses data from the servers at each remote site. It may or may not have its ownlocally connected controllers. The servers at the remote sites may also ex-change information with

each other logicallycreating a global databaseincluding:• Global real time data

access• Trending of real time

and historical systemwide data, on a singletrend

• Global alarming• Global system

messages

Further details onDistributed ServerArchitecture are availablein the PlantScapeDistributed ServerArchitecture – ElevatingDistributed Control to theHighest Plateau documentSL-53-655.



Application Enablers

PlantScape provides powerful application enablers with configurable (rather than programmatic)facilities to support individual application requirements. Application implementation time is greatlyreduced, providing extremely cost effective automation.

Recipe Management -- PlantScape Recipe Management provides facilities to create recipes anddownload them to nominated process units. Each recipe may have up to thirty items, with recipeschained together to form larger recipes if required. Recipe items may be used to set ingredient targets,set alarm limits, set timers and place equipment into correct operating state. Items may be individuallyenabled for scaling.

Downtime Analysis -- Downtime Analysis may be used to detect, record and code any equipmentbreakdowns or process delays to provide plant downtime analysis. A list of all current downtime eventsis maintained as well as the history of previous downtime events, with each assigned a category and areason code. Downtime reports may be printed periodically or on-demand, showing downtime durationsorted by categories and reasons.

Point Control Scheduler -- The Scheduler option allows point supervisory control to be automaticallyscheduled to occur at a specified time. This may occur on a "one-shot" basis, at a pre-determinedinterval, or on specific days.

SPQC -- The SPQC(Statistical Process & Quality Control) option provides powerful statisticalprocessing capabilities for real-time data collected by the system. Facilities include on-line generationof control charts for X-Bar and R-Bar, histograms and Sigma trends, Shewart's calculations for UCL(Upper Control Limit) and LCL (Lower Control Limit), and on-line statistical alarming.

Extended Event Archiving -- Extended Event Archiving may be used when the events logged by thesystem are required to be archived for later review. Storage capacity is dependent upon mediacapacity, but storage of over 1 million events is easily achievable. Approximately 60 Mb of hard diskspace is required for every 100,000 events archived.

Alarm Pager -- Point alarms may optionally be sent to an alarm paging or messaging system. Up to100 pagers can be configured, and each pager has a schedule of operation so that users are onlypaged when they are on call. The information they receive is what normally appears on the alarmsummary. For each phone number configured, the user may specify the days of the week and times ofthe day that the pager is in use. Points can be scheduled to ring one or more of the configured pagers.

ODBC Data Exchange -- This option enables two-way exchange of data between the PlantScapeServer database and an ODBC-compliant local or network third-party database. It uses standardStructured Query Language (SQL) commands. The PlantScape Server acts as a client application inthis configuration. Information exchanged includes point values, point history, and user file data.Databases that include ODBC drivers include Microsoft SQL Server, Oracle 7, Microsoft Access, andSybase 10.

Open Data Access -- Whenever another application requires data from the PlantScape database,Open Data Access is required. Some examples of when Open Data Access is required are:

• reading data into a Microsoft Excel Spreadsheet• running a query on the database from Microsoft Access• another PlantScape system requiring point data• an OPC Client requires point data• a user written application is accessing the database

Each of the instance of any of the above is considered a ‘user’ of Open Data Access.



There are three main components to Open Data Access that are described below:

The ODBC Driver allows the Server database to be queried using SQL commands from ODBCclient applications, such as Microsoft Access. The Server database is exposed as a number ofread-only ODBC tables including Points, Event History and Process History. Driver featuresinclude:

• Open read-only access to plant real-time and historical data• Throttling to prevent performance impact• Redundancy of data storage• Fully functional examples for productivity improvements

It is optimized for Microsoft Access and hence other ODBC ad hoc query/report applications.

OPC Server -- The PlantScape OPC Server capability allows a third-party OPC client applicationto read/write PlantScape point parameters. The OPC server is based on Honeywell's HCI servertoolkit, which in turn is based on OPC specification V1.0a. It supports all mandatory OPCinterfaces.

Network Server – The Network Server provides extremely efficient, access to the PlantScapedatabase for network based applications such as Microsoft Excel Data Exchange, Network NodeInterface and Network API options.• Microsoft Excel Data Exchange allows Microsoft Excel to obtain real-time and historical

data from the PlantScape system. This option provides read and write access to data in oneor more PlantScape Databases, providing a powerful data consolidation and reporting tool.Wizards for Microsoft Excel are included to help set up the data to be collected.

• When Network Node Interface is licensed on a PlantScape server it can read/write pointdata to another PlantScape server.

• Applications executing on other network connected platforms may easily access PlantScapereal-time data over the network using the Network API. The API provides high levelsubroutine calls in Visual C/C++ or Visual Basic to allow read/write access to PlantScape datain a networked environment.

Application Toolkit

Two types of application programming interface (API) are available. The first is for applications writtenon the PlantScape server and the second is for applications that are required to run on network basedclients (that are not necessarily operator stations).

The API (programmed in C/C++) on the server includes the following functions:• read and write to point parameters in 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 VB (Visual Basic) or Visual C/C++) on the network-based clients includes thefollowing functions:

• read and write to control module parameters in the database• access to historical data• initiate supervisory control actions• access to user-defined database• create alarms/events



Figure 15. Display Builder Example

Engineering Tools

Quick Builder -- QuickBuilder, allows users toconfigure points,controllers/RTUs, stationsand printers. Quick Builderleverages a relationaldatabase engine (MicrosoftJet Engine) to providegreater productivity throughcapabilities such as filteringuser views of the database,multipoint edit facilities andthe intuitive Windows styleinterface. Other features thatthe relational databaseprovide are the user-definedfields that can be used fortermination schedules, wirenumbers, etc., and astandard set of reports.Additions and modificationsto the PlantScape databasecan be made while thesystem is on-line.

Display Builder -- Display Builder is an object-based, fully integrated custom display builder fordevelopment of application specific graphics. Animation of displays is completed quickly and easily withsimple point and click typeconfiguration. A library ofcommonly used plantequipment such as vessels,piping, valves, tanks, motors,etc., is supplied with DisplayBuilder to further speedgraphic development. Inaddition, Template Displaysmay be used to reduceconfiguration time wheresimilar displays need to berepeated throughout thesystem. Process objects andcolor palettes allow quick andeasy creation of customobjects with or without 3Deffects. Graphic displays canalso be significantly enhancedthrough the use of VisualBasic Scripting and ActiveXcomponents. Effects such ashigh-speed animation, tooltips, and control of a stationfrom an application arepossible with VB Scripting. Additionally, a wide array of ActiveX component types, such as playingsound and video can be invoked.

Figure 14. QuickBuilder Example



Figure 16. Knowledge Builder embedded in anOperator Station window

User DocumentationPlantScape documentationis available in three basicforms to the user:

• Printeddocumentation (seebelow)

• On-line Help (F1function key fromwithin severalapplications)

• Knowledge BuilderElectronic On-lineDocumentation usingHTML FrameBrowser (see below)

The following is a listing ofcomponents in theelectronic PlantScapeKnowledge BuilderDocument Set:

Table 4. PlantScape Knowledge Builder Electronic Documentation

Electronic Document Component Description

PlantScape Guides

Overview A comprehensive overview of the PlantScape System.Planning Guide Covers all aspects of PlantScape System planning.ControlNet Installation Guide Procedures for installing all Control System related cabling, wiring,

and associated hardware components.Control Hardware Installation Guide Procedures for installing controller, I/O, communications, and

special function modules.Control Building Guide Procedures for configuring a PlantScape control strategy. Includes

guidelines on how to build detail displays with a reference to thePlantScape Display Building Guide.

Start-up and Shutdown Guide Procedures for normal start-up, shutdown, and restarts, includingcontroller, networks and SCADA.

Troubleshooting and MaintenanceGuide

Procedures for troubleshooting and maintenance, with diagnosticinformation.

Rail I/O Implementation Guide Provides information about the RIOM-H (GI/IS) components as asupplement to existing procedures.

Fieldbus Implementation Guide Procedures for interfacing FOUNDATION Fieldbus devices withPlantScape’s Hybrid Controller.

Server and Client Installation Guide Procedures for installing Server and Clients.Server and Client ConfigurationGuide

Procedures for configuring Server devices, points, reports etc.

Operators Guide Procedures for operating Station, including monitoring andcontrolling, managing alarms, and generating and viewing reports.

Administration Guide Procedures for system administration, including topics such assecurity and system back-ups. Incorporates SCADA and ProcessSystem administration information.

Statistical Process & Quality Control Procedures for implementation of SPQC



Electronic Document Component Description

Application Development Guide Procedures for writing Server applications.

Display Building Guide Procedures for building custom Server displays.

Quick Building Guide Procedures to create and modify configuration databases, whichdefine how system items, such as Stations and points, are set up.

PlantScape Reference

Control Builder Component Reference General information on control module components (how theywork).

Control Builder Parameter Reference Detailed information on Control processor module and functionblock parameters.

Control Specification Reference Detailed process specification information for PlantScape System.

Control Builder Notification Reference Describes error codes generated from within Control Builder.

Hardware and Point Building Reference Detailed reference for PlantScape SCADA Server hardware andpoints.

Controllers Reference Comprehensive reference guide to all SCADA drivers.

PlantScape Theory

Communications Theory Covers all aspects of PlantScape communications, includingController peer-to-peer.

Control Builder Components Theory General information on control module components (how theywork).

Notifications Theory General notifications theory information (how it works).

PlantScape General Information

Supporting Information

Frequently Asked Questions Answers to frequently asked questions about the PlantScapeSystem.

Global Notices and Trademarks Copyright and license information.

Honeywell Contacts Lists identifying important contacts within Honeywell.

References Identifies non-PlantScape Honeywell documents that may besources of reference for the material discussed in KnowledgeBuilder.

Other Resources

WWW Resource Links Provides links to important web sources of information.

Getting Started A complete guide to getting the PlantScape system up andrunning.

Help Provides Knowledge Builder Help.

Dictionary Dictionary of terms and acronyms used in PlantScape.

Global Table of Contents Complete Table of Contents for Knowledge Builder.

Site Docs Site Docs allows the user to add links to site specific electronicdocumentation within Knowledge Builder. A trial version of SiteDocs is included!

Search Engine Extensive search capability for Knowledge Builder data base.

Functions Block Home Pages Control Builder Function Block reference providing examples,detailed theory, etc.

Training Training course schedules, enrollment information, course outlinesand more!



The following is a listing of available PlantScape printed documentation:

Table 5. Printed PlantScape Document Set

PlantScape System

TC-DCXX11 PlantScape Overview• Includes:

– PlantScape Concepts– Supervisory and Control Components– Monitoring and Controlling the Process

TC-DCXX21 PlantScape Planning Guide• Includes:

– Planning and Design– Hardware Configuration– ControlNet Configuration Planning– Site Planning

TC-DCXX31 PlantScape Process Startup and Shutdown Guide• Includes:

– Startup and Restart– System Shutdown

TC-DCXX51 PlantScape Hybrid Controller Installation Guide• Includes:

– Controller and Hardware Installation– Enclosure Installation– ControlNet Installation

TC-DCXX61 PlantScape Process Control Building Guide• Includes:

– Control Building Guide

TC-DCXX71 PlantScape Reference• Includes:

– TC-DCX101, PlantScape Control Builder Reference– TC-DCX111, PlantScape Troubleshooting and Notifications Reference– TC-DCX121, PlantScape Control Specifications Reference

TC-DCXX81 PlantScape Theory• Includes:

– Control Builder Components– Peer-to-Peer Functions– Controller Redundancy

– Control Functions– Notifications Theory– Communications Theory

TC-DCSX21 Getting Started with PlantScape

TC-DCSX31 PlantScape Software Installation and Upgrade Guide

TC-DCX131 PlantScape Rail I/O – Series H Implementation Guide

TC-DCX151 PlantScape Linking Device Implementation Guide

TC-DCX171 PlantScape Rail I/O - Series A Implementation Guide

TC-DCX181 PlantScape Network Planning Guide

PlantScape SCADATC-DSXX11 PlantScape Application Development Guide

TC-DSXX21 PlantScape Server and Client Configuration Guide

TC-DSXX31 PlantScape Display Building Guide

TC-DSXX41 PlantScape Operator's Guide

TC-DSXX51 PlantScape Server and Client Installation Guide

TC-DCS101 PlantScape Statistical Process & Quality Control User’s Guide

TC-DSX111 PlantScape Controllers Reference

TC-DSX121 PlantScape Administration and Startup Guide



Specifications

Table 6. Controller Function Block Types in CB10 Control Builder

Function Block (FB) Type

• General Purpose" Flag" Numeric" Timer" Type Convert Block" General Purpose Array (Numeric, Flag, Text)" Message block support for Operator messages

• PV Algorithms" Data Acquisition" Totalizer" General Linearization

" PV Calculator" Dead Time" Lead / Lag

• Regulatory Control Algorithms" Proportional, Integral, Derivative (PID)" PID with Feedforward" Override Selector (4 inputs)" Remote Cascade" Auto Manual" Switch (8 input single pole)" Fanout Block (1 input/up to 8 outputs)

" Regulatory Calculator" Ratio Bias" Ramp / Soak" Positional Proportional" Pulse Length" Pulse Count

• Device Control (Motor Control)• Discrete Logic (per IEC 1131 standard)" 2oo3 (2-out-of-3 Voting)" AND" CHECKBAD" DELAY" EQ (Compare Equal)" FTRIG (Falling-Edged

Trigger)" GE (Compare Greater Than

or Equal)" GT (Compare Greater Than)" LE (Less Than or Equal)" LIMIT" LT (Compare Less Than)" MAX (Maximum)" MAXPULSE (Maximum Time

Limit Pulse)

" MIN (Minimum)" MINPULSE (Minimum Time

Limit Pulse)" MUX (8-Input Multiplexer)" MUXREAL (8-Input

Multiplexer, Real Number)" MVOTE (Majority Vote)" NAND" NE (Compare Not Equal)" nOON (n-out-of-N Voting)" NOR" NOT" OFFDELAY" ONDELAY" OR" PULSE (Fixed Pulse Output)

" QOR (Qualified OR)" ROL (Rotate Left)" ROR (Rotate Right)" RS (Reset-Dominant Flip-

Flop)" RTRIG (Rising-Edged

Trigger)" SEL (Selector Function)" SELREAL (Selector Function,

Real Number)" SHL (Shift Left)" SHR (Shift Right)" SR (Set-Dominant Flip-Flop)" TRIG (Change Detect Trigger)" WATCHDOG" XOR (Exclusive OR)

• Sequential Control Functions (follows S88.01)" Step FB" Transition FB" Handlers: Main, Interrupt, Check, Restart, Hold, Stop, Abort

• Data Exchange" Request (Numeric, Flag, Text)" Response (Numeric, Flag, Text)• I/O Channel Blocks

" Analog Input (AI)" Analog Output (AO)" Pulse Width Modulation (PWM)" Rail I/O Series A (Input & Output)

" Digital Input (DI)" Digital Output (DO)" Serial Interface Array (Numeric, Flag, Text)" Fieldbus Analog & Digital (Input & Output )



Table 7. PlantScape System Performance & Capacity Specifications

Table 7.1. Operational Display Update

Maximum Continuous Display Update Rate 1 sec

Typical Display Response Time to a Field Change, 100Parameters Per Display, Single Station/Server (Stationconfigured for 1 sec. update)

< 2 sec

Typical Display Call Up Time, 100 Parameters Per Display,Single Station/Server (call up time dependent on displaycomplexity; excludes initial call up)

< 2 sec

Maximum number of concurrent users connected to oneServer

10 for Process Server (20with NT Server)

40 for SCADA Server

Table 7.2. Server Redundancy

Minimum Server Switchover Time 10 sec

On server switchover, the C200 Controller performs an event recovery. This causes Controllers toreport all current alarm conditions. The server will report all current process alarms and events.

Database synchronization is performed as an on-line, background activity without affecting theoperation of the servers. Synchronization time depends on system configuration (e.g., database size,history, processor speed).

Table 7.3. Server Notifications

Maximum number of events (burst condition) 500 events

Maximum number of events/second (sustained) 40/sec

Maximum number of alarms/second (sustained) 20/sec

Note: Up to two events are also generated for every alarm, including one event for entering the alarm condition andone for return to normal.

Table 7.4. Multi-User Control Builder Operational Limits

Maximum Control Builder Clients connected to single Server 4

Minimum continuously available Network Bandwidth required foreach multi-user CB Client.

128KB



Table 7 (cont’d). PlantScape System Performance & Capacity Specifications

Table 7.5.a. Distributed Server Architecture Performance Specifications

DSA Process Server, Publishing Communications Performance

AvailableNetwork

Bandwidth 4

Max NetworkThroughput (Param /

Second) 1

Max Throughput /Server (Param /

Second) 2, 3

MaximumSubscribing Servers

64 Kb 100 100 1

128 Kb 200 200 2

256 Kb 400 400 3

512 Kb 800 800 4

1Mb 1000 1000 4

2 Mb 2000 1000 4

10 Mb 10000 1000 4

Table 7.5.b. DSA SCADA Server, Publishing Communications Performance

AvailableNetwork

Bandwidth 4

Max NetworkThroughput (Param /

Second) 1

Max Throughput /Server (Param /

Second) 2, 3

MaximumSubscribing Servers

64 Kb 100 100 1

128 Kb 200 200 2

256 Kb 400 400 3

512 Kb 800 800 4

1Mb 1000 1000 4

2 Mb 2000 1500 4

10 Mb 10000 2000 4

Table 7.5.c. Subscribing Server Communications Performance

Available NetworkBandwidth 4

Max Network Throughput(Param / Second) 1

Max Publishing Servers

64 Kb 100 1

128 Kb 200 2

256 Kb 400 4

512 Kb 800 6

1Mb 1000 8

2 Mb 2000 10

10 Mb 10000 10

Notes for DSA Capacity

1. Maximum traffic on any individual network segment.2. For PlantScape Process Servers, the total parameter throughput caused by remote station

displays, local station displays, fast history, etc., cannot exceed 1000 parameters/sec3. A subscribing Station is one that displays data from another publishing server through DSA. A

larger number of Stations subscribing to remote data will result in a greater amount of networktraffic. Absolute maximum number of subscribing Stations/publishing Server is 20

4. “Available Network Bandwidth” means dedicated continuously available bandwidth for DSA usebetween the Servers, and not shared bandwidth with other applications such as Station accessor Control Builder Multi-User access.

Maximum alarm/notification rate is 20/sec/server.




Table 7.6. Supervisory Process Control Network

Ethernet (R320) ControlNetSupervisory Networks per non-redundantor redundant server

Note: Mixed Supervisory ControlNet &Ethernet on same Server is notsupported.

1 non-redundantnetwork

1 redundant or non-redundant network

Allowable Combinations of Controllers *per Server

10 or less Non-Redundant only

10 (whether redundant ornon-redundant)

Network Topology Switched Conjoined

Data Rate 10 Mbits/sec 5 Mbit/secMedia Redundancy Non-redundant only Single cable or redundant

media operationsupported.

*Controller Definitions including PLCsNote: Multiple Controllers per chassis isNOT supported.

Non-Redundant: 1 C2001 CL55501 PLC5/C or E 1

1 SLC (Ethernet only)

Redundant:2 C200s in a Chassis Pairwith 2 RMs

1 A Logix5550 or PLC5/C counts as a Controller only if a SCADA connection is formed to it. Use of the

EXCHANGE FB does not constitute a SCADA connection.

Table 7.7. Control Execution Environment (CEE) General Configuration Options

Base Execution Periods supported 50 ms, 5 ms

Base Execution Period 50 ms CEE 5 ms CEE

Controller Redundancy Supported Yes No

Remote I/O Supported Yes No

I/O Module Function Block Execution Period 50 ms 5 ms

Available CM/SCM Execution Periods 50, 100, 200, 500,1000, 2000 ms

5, 10, 20, 50, 100,200 ms

Configurable Peer-to-Peer Update Rates (Period)(Rate at which a CEE can subscribe to data from other CEEsthrough peer-to-peer communications.)

100, 200,500, 1000 ms

10, 20, 50, 100,200,

500, 1000 ms




Table 7.8. Controller Communications Performance PPS = Average Parameters per Second

50 ms CEE 5 ms CEE

Overall Communications Performance per PlantScape Server

Maximum Total Parameter Access Response Rate to the Serverfrom all Controllers combined.(Includes Display updates, Fast/Slow History, Excel I/ODBC Exchange, and CBMonitoring)

4000 PPS 4000 PPS

Overall Communications Performance per CEE/CPM

Maximum Total Parameter Access Response Rate(Includes all Server Data Requests and peer communications)

2000 PPS 2000 PPS

CEE to CEE Peer-to-Peer Communications Performance per CEE/CPM

500 PPS 500 PPS

ControlNet ControlNet

50 @ 100 ms100 @ 200 ms250 @ 500 ms500 @ 1 sec

5 @ 10 ms10 @ 20 ms25 @ 50 ms50 @ 100 ms100 @ 200 ms250 @ 500 ms500 @ 1 sec

Ethernet Ethernet

Maximum Initiator Node Pull/Get Request Rate (to all target nodes).(Based on the number of requests for peer data and the peer update rate.)

250 @ 500 ms500 @ 1 sec

250 @ 500 ms500 @ 1 sec

Maximum Target Node Response Rate to Pull/Get Requests (fromall initiator nodes).

500 PPS 500 PPS

Maximum Initiator Node Push/Store Request Rate (to all targetnodes) 1

50 PPS 50 PPS

Maximum Target Node Response Rate to Push/Store Requests(from all initator nodes).

50 PPS 50 PPS

CEE to PLC – Peer-to-Peer

Supported Protocols and commandsPCCC (Programmable Controller Communications Commands): Typed Read and Typed Write through logical ASCII addressing

CIP (Control and Information Protocol):

Data Table Read and Data Table Write

Supported File Type

B (Binary), F (Floating Point), N (Integer), I (Input), O (Output), S (Status), A (ASCII)



Communications Capacity per CEE/CPM

CEE to PLC – Peer-to-Peer 50 ms CEE 5 ms CEE

Maximum Number of REQUEST blocks per CEE/CPM 32 32

Maximum Number of RESPONSE blocks per CEE/CPM 32 32

Maximum Number of “active” Target Devices for REQUEST blocksper CEE/CPM.DHRIO Module only counts as 1 Target Device even when communicating withmultiple PLCs on either DH+ network

2

8 8

Maximum Number of DHRIO Modules per CEE/CPM 2 2 (local chassis only)

Target communication performance 500PPS 2 500PPS 2

1 Currently the SCM Step is the only block type that can initiate peer push/store requests for CEE to CEE peer communications.

Number of parameters communicated per second depends upon target device configuration and use of requested Function Block2 The communication performance is not guaranteed, it depends on the response from the target device, the number of Exchange

FBs communication through the same path and the application implementation in the target device.

Table 7.9. Controller Redundancy (50 ms CEE only)

Control Processor Module (CPM) models supported C200 only

Control Processing Switchover Interruption Time 500 ms

Redundancy Module Cable Medium Fiber Optic Cable

Redundancy Module Cable Lengths 1, 3, 10 meters

Redundancy Module Slot Width 2 slots

Initial Synchronization Time (from Sync Start to Completion) 90 sec

Maximum Elapsed Time Between Commanded Switchoverand Completion of Initial Synchronization

120 sec

Maximum Elapsed Time Between Switchover Due toPower Cycle of the Primary and Completion of InitialSynchronization

150 sec




Table 7.10. I/O Module and Fieldbus Capacity

50 ms CEE 5 ms CEE

Maximum number of I/O ControlNet CNI’s per Controller Chassis 4 0

Maximum Number of IOM’s per CEE/CPM 64 12

Maximum Number of Analog IOM’s per CEE/CPM 64 12

Maximum Number of Serial Interface Modules per CEE/CPM 3 1

Maximum Number of FTA assemblies per Serial Interface Module(Each FTA connected counts as 4 IOMs in the 64 Max IOM calculation above andthe 24 IOMs/CNI calculation below.)

2 2

Maximum Number of Remote I/O Racks + Rail Adapters(combined) per CEE/CPM.

8 0 (local I/O

only)

Maximum Number of IOMs per ControlNet CNI -- Rack + RailModules in any combination (except SIM & PIM as noted) (Each Pulse Input Module counts as 1.5 IOMs in the 24 IOM/CNI calculation, eachDHRIO Module counts as 1 IOM.)

24 0 (local I/O

only)

Maximum number FF Linking Devices per CEE/CPM

Note: Each Linking Device counts as 1 IOM in the 64 IOMs/CPM calculationabove.

8 0 (local I/Oonly)

Maximum number FF Linking Devices per Non-Redundant Server 8 0 (local I/Oonly)

Maximum number FF Linking Devices per Redundant Server (NI-FBUS Service and NI Configurator must be run on the Backup Serveronly)

16 0 (local I/Oonly)

Maximum number FF Linking Devices per NI Configurator Project file (i.e.,use one project file per LD)

1 0 (local I/Oonly)

Maximum Number of H1 segments per FF LD (Each segment is defined as a FOUNDATION 31.25 kbaud H1 network)

2 N/A

Maximum number of FF Devices per H1 segment connected to a LD. 10 N/A

PlantScape Process systems do not support both the Linking Device and the MZ-NTIF15interface. NZ-NTIF15 is a valid option with any other PlantScape Process System. It isalso valid with any PlantScape SCADA system or any PlantScape VISTA system.

Table 7.11. Input Module Sampling Period Specifications

Sampling Period

Typical Input Modules(Includes CIOM-Series A and RIOM-H Modules, with exceptions noted below)

25 ms

High Density/Non-Isolated Analog Input Module 250 ms

Digital Input Module used by 5 ms CEE (local only) 1 ms

RTD Module (CIOM-Series A) 50 ms

Thermocouple Module (CIOM-Series A) Can vary slightly depending upon the frequency setting and upon the number of points

50 ms

Serial Interface Module (CIOM-Series A) 250 ms



Table 7.12. CEE/CPM Processing Resources

PU = Processing Unit. The PU represents a platform-independent amount of processing resource (time) required tocomplete a predefined amount of computational (control) work.

CEE/CPM Configuration PU Maximum

50 ms CEE – Non Redundant Configuration 3600 PU/sec

50 ms CEE – Redundant Configuration 1600 PU/sec

5 ms CEE – Non Redundant only 2400 PU/sec

Table 7.13. CEE/CPM Memory Resources and Block Configuration MU = Memory Unit = 1 Kbyte = 1024 bytes

Maximum available CEE/CPM memory resources 4000 MU

Maximum total number of CMs, SCMs and IOMs configurable perCPM/CEE

1000

Maximum number of component blocks per CM Note: This maximum number is achievable under nominal operating andmonitoring conditions. The following items may lower the maximum numberof FB's that can be placed in or monitored from a single CM:

• Monitoring frequently changing values

• Operating in a redundant system

• Operating with high peer-to-peer configured

40

Maximum number of Steps & Transitions (in all handlers) perSCM

160 (80 Step/Transitionpairs)

Maximum number of process history points per CEE/CPM 500




Table 7.14. Typical IOM/CM/SCM Processing and Memory Resource Requirements

Processing Resource Consumption Memory

ResourceConsumption

Typical Module Types(FB Content in Parentheses)

Total Processing Consumption (PU/sec) per moduletype = Processing Resource Consumption (PU/moduleexecution) / Execution Period (sec/module execution)* Number of Modules

50/5 ms CEENon-Redundant

(PU/ModuleExecution)

50 ms CEERedundant(PU/ModuleExecution)

All CEEConfiguration

s (MU/Module)

Typical I/O Module(Average consumption of available IOM’s)

0.3 0.19 0.6

Analog Data Acquisition CM(10 AI, 10 DataAcq FB’s)

2.9 3.8 7.4

Small Analog Data Acquisition CM(1 AI, 1 DataAcq FB’s)

0.47 0.43 1.0

Regulatory Control CM(1 AI, 1 DataAcq, 1 PID, 1 AO, 6 Logic FB’s)

2.8 2.8 3.9

Auxiliary Function CM(10 Aux. FB’s, such as AuxCalc, Totalizer)

4.2 5.1 13.1

Digital Data Acquisition CM(10 DI, 10 Flag FB’s)

1.2 1.2 3.1

Small Digital Data Acquisition CM(1 DI, 1 Flag FB’s)

0.22 0.14 0.6

Device Control CM(2 DI, 2 DO, 1 DevCtl, 5 Logic FB’s)

1.3 1.3 3.1

Logic Control CM(20 Logic FB’s)

1.0 1.0 3.5

Sequence Control Module (SCM)(1 each of Main, Hold, Stop and Abort Handlers, 10Steps with 8 Outputs each, 10 Transitions with 5Conditions each, 10 Recipe items, 5 History items)

2.0 3.0 55

Sequence Control Module with an aliastable of size 45 rows by 100 columns(1 each of Main, Hold, Stop and Abort Handlers, 10Steps with 8 Outputs each, 10 Transitions with 5Conditions each interspersed in all the handlers, 10Recipe items, 5 History items)

2.0 3.0 150

Sequence Control Module with an alias tableof size 500 rows by 9 columns(1 each of Main, Hold, Stop and Abort Handlers, 10Steps with 8 Outputs each, 10 Transitions with 5Conditions each interspersed in all the handlers, 10Recipe items, 5 History items)

2.0 3.0 146

The following Block Libraries consume the followingextra memory when the first block is loaded to theC200 Controller:

! Exchange (PLC5 & Logix5550) – 70 MUs! Pulse Input IOM – 100 Mus! GI/IS Series R IOMs – 125 MUs



Table 8. PlantScape Server Hardware Descriptions

Table 8.1. MZ-NTPC02 – PlantScape Performance Server PC With Windows NTWorkstation

Description:PC suitable for providing PlantScape Server Platform for medium to large applications (e.g., over5 stations, databases over 2000 points, advanced control or other applications, extra high-speeddata acquisition) or for users who want a platform with the longest life before obsolescence. Forcustomers purchasing their own PCs, see Appendix A for guidelines.

Includes:• Current "best-performance" Pentium III processor

suitable for PlantScape for WINDOWS NT serversupport

• 256 MB Memory minimum• 8x SCSI CD-ROM Drive minimum• 9 GB Hard Disk minimum• Keyboard• Mouse• Mini-Cartridge Tape Drive• Microsoft Windows NT Workstation 4.0 with Service

Pack 6a

Special Notes:• Monitor not included - ordered

separately• COM1/COM2 may be used for

serial communications• If more than 2 serial ports

required, or RS-422/485, useMulti-port Serial Communicationsboard

• Required for any new PlantScapeProcess system

Table 8.2. MZ-NTPC03 -- PlantScape Windows NT Operator Station PC

Description:PC suitable for providing PlantScape Station for Windows NT Operator Station Platform.

Includes:• Current "best-price" processor suitable for

PlantScape Windows NT Station mini server andclient support,

• 128 MB Memory minimum• 8x SCSI CD-ROM Drive minimum• 9 GB Hard Disk minimum• Keyboard• Mouse• Microsoft Windows NT Workstation 4.0 with Service

Pack 6a

Special Notes:• Monitor not included - see

Hardware Options



Table 9. PlantScape Server Sizing Specifications

Database Item Default Size Maximum

Point Count

PlantScape SCADA points use acomposite point structure. A status pointcontains a PV, OP and a Mode. An analogpoint contains a PV, SP, OP, Mode and 4auxilliary parameters.

Total number of PlantScape Processpoints = 2 * Number of Processors +Number of IOMs + Number of CMs +Number of SCMs.

The total Server point count = totalPlantScape SCADA point count + totalPlantScape Process point count.

2050100300650

1,0002,0005,00010,00015,00020,000

65,000

Station Connections License 20 Process

Printer Connections 50 50

Channels 90 99

Scada RTUs (Controllers) 100 255

Algorithm Blocks 6,000 6,000

Areas 1,000 1,000

Numbered Custom Displays 800 32,467

DFD’s on Named Displays 300 300

Numbered Custom Shapes 700 32,567

Trend Sets 3,000 3,000

Operating Groups 16,000 16,000

Reports 200 200

Point Control Schedules 1,000 1,000

Operators 400 32,767

Recipes 500 32,767

Concurrent Alarms 1,000 1,000

Concurrent Messages 1,000 1,000

Concurrent Delays 1,000 1,000

Stored Delays 2,000 32,767

Stored Events 10,000 32,767

Extended Events 100,000 1,000,000

STD History Point Parameters 2,000 10,000

EXTD History Point Parameters 200 5,000

FAST History Point Parameters 100 1,000

Number of User Files 3 150

Number of Application Tasks 80 80

Point Lists 2,000 2,000

SOE Entries 1,000 32,767



Table 10. C200 Control Processor SpecificationsTC-PRS021, TK-PRS021

Parameter Operative and Storage Limits Transportation Band

Ambient Temp Range 0 to +60°C no fans -40 to 85°C 1

Temp. Rate of Change ≤ 1°C/min. ≤ 5°C/min.

Relative Humidity 2

Uncoated (TC-PRS021)Coated (Tk-PRS021)

5 to 95% (non condensing)Mild (G1)Moderate (G2) or Harsh (G3)

5 to 95% (non cond.)G1G2 or G3

Vibration (3 axes)FrequencyAccelerationDisplacement

10 to 60 Hz0.5 g max.0.1 inches

10 to 60 Hz1 g max.0.1 inches

Mechanical ShockAccelerationDuration

5 g max.30 ms max.

20 g max.30 ms max.

Barometric PressureAltitude -300 to +3000 m Any 1

Corrosives G2 std, G3 option (ISA S71.04) 3 G3

Module Power Requirements +5 VDC +/- 5% @ 1.5 A+3.3 VDC +/- 5% @ 1.0 A

Module Battery Backup Time 4

Lithium Battery (standard, built in)

Battery Extension Module (BEM)

144 hours (non-rechargeable,replaceable) - 6 days

120 hours (rechargeable) - 5 days

Lithium battery isdisconnected duringshipment.

Removal/Insertion under power(RIUP)

NOT PERMITTED when equipment isinstalled in a Class I, Division 2,Hazardous (Classified) Location.PERMITTED when equipment isinstalled in ordinary, non-hazardous,locations (I/O modules reloadautomatically)

CE Conformity (Europe) 89/336/EEC, EMC DirectiveEN 50081-2, Emissions, IndustrialEN 50082-2, Immunity, Industrial

N/A

CertificationsUL (Unclassified Locations)

CSA & FM Class I, Div. 2,Groups A, B, C, & D(see Table 12 for agency symbols)

UL 508, Industrial Control Equipment

Mounting (Maintenance may require ahot work permit)

1 The 1/2AA Lithium Battery has a non-restricted classification due to its size. It can be shipped without any special

documentation or note on the shipping list. The battery is specified for operation from -55 °C to +85 °C.2 The maximum relative % humidity specification applies up to 40°C. Above 40°C the RH specification is de-rated to 55%

to maintain constant moisture content.3 With an enclosure. Enclosure external temperature limits TBD.4 CPM backup is provided via the Lithium Battery or the Battery Extension Module (BEM), but not by both. The Lithium

battery must be removed from the Control Processor if a BEM is used in the rack. A label inside the CP front doorprovides that warning.



Compliance and Certification Specifications

Compliance to European Union Directives. This product has the CE mark and is approved forinstallation within the European Union and EEA regions. It has been designed and tested to meet thefollowing directives:

• EMC Directive. This apparatus is tested to meet Council Directive 89/ 336/ EEC ElectromagneticCompatibility (EMC) using a technical construction file and the following standards, in whole or inpart:

• EN 50081- 2 EMC – Generic Emission Standard, Part 2 – Industrial Environment• EN 50082- 2 EMC – Generic Immunity Standard, Part 2 – Industrial Environment

The product described in this document is intended for use in an industrial environment.

• Low Voltage Directive. This product is also designed to meet Council Directive 73/ 23/ EEC LowVoltage, by applying the safety requirements of EN 61131– 2 Programmable Controllers, Part 2 –Equipment Requirements and Tests.

Agency Standard Description

CE Mark Standard Compliance Electrical Emissions and SusceptibilityCSA C22.2 No. 142-M1983 Process Control Equipment

C22.2 No. 0-M1982 General Requirements Canadian Electrical Code, Part IIC22.2 No. 4-M1982 Bonding and Grounding of Electrical Equipment

FM ISA S12.12 Nonincendive Electrical Equipment for Use in Class I & II, Div. 2and Class III, Div 1 & 2 Hazardous (Classified) Locations

UL 508 Industrial Control Equipment

Table 11. Chassis SpecificationsTC-FXX041, TC-FXX071, TC-FXX102, TC-FXX132, TC-FXX171, TK-FXX101, TK-FXX131

Model Moduleslots

Dimensions (with mounting tabs& power supplies) W x H x D

Approx. weight(without modules)

TC-FXX041 4 26.3 x 16.9 x 14.5 cm (10.3 x 6.7 x 5.8 in) 0.75 kg (1.6 lbs)TC-FXX071 7 36.8 x 16.9 x 14.5 cm (14.5 x 6.7 x 5.8 in) 1.1 kg (2.4 lbs)

TC-, TK-FXX102 10 48.3 x 16.9 x 14.5 cm (19.0 x 6.7 x 5.8 in) 1.45 kg (3.2 lbs)TC-, TK-FXX132 13 58.8 x 16.9 x 14.5 cm (23.1 x 6.7 x 5.8 in) 1.9 kg (4.2 lbs)

TC-FXX171 17 73.8 x 16.9 x 14.5 cm (29.1 x 6.7 x 5.8 in) 2.2 kg (4.8 lbs)Minimum Chassis-to-Cabinet Vertical Distance 15.2 cm (6.0 in)Minimum Chassis-to-Cabinet Horizontal Distance 10.2 cm (4.0 in)Minimum Chassis-to-Chassis Vertical Distance 20.3 cm (8.0 in)Minimum Chassis-to-Chassis Horizontal Distance 10.2 cm (4.0 in)Type of mount Panel mountEnvironmental Conditions Agency Certification Same as Power Supply SpecificationsMinimum Enclosure Depth 20.3 cm (8.0 in)

Hardware Mounting Options

Hardware may be installed in cabinets by Honeywell, interconnected and tested, and then supplied tothe customer, or it may be supplied separately (not installed in cabinets) such that the customer isresponsible for suitable mounting and interconnection/test. Note that in order to comply with applicableregulations and codes, the controller and I/O racks may have to be located in a room, vault, orenclosure that is accessible only to qualified persons. Please refer to NEC 110-17, part 1 (1996National Electrical Code, Copyright 1995 NFPA) or to the appropriate local or national electricalstandards for more information.



Table 12. Power Supply Specifications TC-FPCXX2, TC-FPDXX2, TK-FPCXX2, TK-FPDXX2

Model Uncoated:Coated:

TC-FPCXX2TK- FPCXX2

TC-FPDXX2TK- FPDXX2

Input Voltage Range 85-132 VAC or170-265 VAC (selectable)

19.2-32 VDC1

Input Power4 150 VA, 92 W 100 W

Maximum Inrush Current 15 A 30 A

Frequency Range 47-63 Hz DC

Total power output maximum, watts 70 W @ 60 °C 70 W @ 60 °CBackplane Output Current, Maximum2 1.5 A @ 1.2 V

4 A @ 3.3 V10 A @ 5.1 V2.8 A @ 24.0 V

Fuse Protection3 non-replaceable fuse is soldered in place

Wiring #14 AWG (1.4 mm)

Dimensions (L x D x H) 11.2 x 14.5 x 14.0 cm (4.41 x 5.71 x 5.51 in)

Weight – Approximate 1.1 kg (2.5 lb.)

Location Left side of chassis (does not consume a slot)

Environmental ConditionsOperating TemperatureStorage TemperatureRelative Humidity

0 to 60 °C (32 to 140°F)-40 to 85°C (-40 to 185°F)5 to 95% noncondensing

Uncoated (TC-FPCXX2, TC-FPDXX2)Coated (TK-FPCXX2, TK-FPDXX2)

Mild (G1)Moderate (G2) or Harsh (G3)

Agency Certification(when product is marked)

marked for all applicabledirectives

Class I, Div 2, Groups A, B,C & D Hazardous locations

1Input may drop to 16 V for a maximum of 2 minutes each hour for motor starting.

2The combination of all output power (5 V backplane, 24 V backplane, 3.3 V backplane and 1.2 V backplane) cannot exceed70 W.

3This fuse is intended to guard against fire hazard due to short circuit conditions and may not protect the power supply fromdamage under overload conditions.

4Note earlier models were rated as follows: TC-FPCXX1 -- 55 W @ 60°C; 70 W @ 45°C and TC-FPDXX1 -- 50 W @ 60°C;70 W @ 40°C.

Table 13. Terminal Blocks, Cables and Connector Sizes

Description Model Number Wire Size Range

I/O Module Terminal BlocksI/O Module Field Wiring Conn., 20 position TC-TBNH 1 wire @ 14-22 AWG (0.64-1.63 mm)

or 2 wires @ 16-22 AWG (0.64-1.30 mm)I/O Module Field Wiring Conn., 36 position TC-TBCH 1 wire @ 16-22 AWG (0.64-1.30 mm)



Table 14. ControlNet Specifications9904-KTCX15, TC-PCIC01, TC-CCN013, TC-CCR013, TK-CCR013

Parameter Specification

Data rate 5 Mbit/sec

Redundancy Single cable or redundant operation supported

ControlNet Components End devices (workstations and controllers), taps, trunk cable, cableconnectors, terminators, segments, repeaters, and bridges.

Cable Type and Topology RG-6 Quad Shield cable, BNC connectors, trunk & drop, bustopology. See next page for recommended cable types.

Cable Type by Application• Light industrial applications• Heavy industrial applications• High and low temperature applications,

as well as corrosive (harsh) areas• Moisture Resistant (direct burial,

flooding, etc.)

• Standard PVC CM-CL2• Lay-on Armored and Interlocking Armor• Plenum FEP CMP-CL2P

• Flood burial

Maximum Distance and Total Numberof Repeaters Between any two (2)Nodes

• Maximum Coax plus Fiber length of 10 km• Maximum of 5 Repeaters (6 Segments)

• Maximum Coax Segment Length• Maximum Fiber Segment Length

• 1000 m (3280 ft.) - 16.3 m (53.4 ft.) x [Number of Taps - 2]• See Repeater Specifications below

Maximum Total Length DifferentialBetween A and B Trunk

• 800 m (2624 ft.) (total link)

Fiber Optic Repeater Specifications – TC-RPA001, TC-RPRS01, TC-RPFM01

Mounting DIN rail mountable (35 mm wide rail)

Maximum Number of Fiber Modulesper TC-RPA001 ControlNet ModuleAdapter

Four (2 ports/module)

Power Requirements (TC-RPA001) 24 VDC, 700 mA maximum

Fiber Optic Repeater Model TC-RPFS01 (300 M) TC-RPFM01 (3000 M)Optical power budget 4.2 dB 9.3 dBCable wavelength specification 650 ηm (red) 1300 ηmFiber Type 200 µm glass (HCM) 62.5 µmFiber Termination Type Versalink ST Termination

Maximum possible fiber optic segment distance is dependent on the quality of the fiber, number of splices, and connectors.For more ControlNet topology information, refer to the Planning Guide in Knowledge Builder or to TC-DCXX21.

Figure 17. ControlNet Fiber Optic Example -- Use of 2 Fiber Segments to Interconnect 2 Non-Redundant-Media ControlNet Trunk Segments

Local ControlNet Trunk

R1 T1 R2 T2

TC-RPA001 TC-RPFM01

R1 T1 R2 T2

Remote ControlNet Trunk

Tap

Fiber Segments -- 3 Km max each

24 Vdc

TC-RPA001

R1 T1 R2 T2

TC-RPFM01

R1 T1 R2 T224 Vdc

Tap

R1 T1 R2 T2

TC-RPA001 TC-RPFM01

R1 T1 R2 T224 Vdc

R1 T1 R2 T2

��TC-RPFM01

R1 T1 R2 T2



Table 15. Honeywell-Recommended ControlNet Coaxial Trunk Cable Types (12)

HoneywellPart

Number

Supplierand PartNumber

FieldUsage

NEC /CEC

Rating(15)

Jacketcolor

Jacketmaterial

DielectricType

ElectricalProperties

CompatibleConnector

Comments

51192416 Belden3092A(4)

riser-rated CMR Black PVC (10) Foam PE ControlNetnetwork-tested by

Honeywell

51192417-100 (7)

Standard HoneywellControlNet raw trunkcable (sold as TC-KCC900).

(2) CommScope5060R

riser-rated CMR Black PVC (10) Foam PE (5) (8) CommScope version ofBelden 3092A cableabove.

CommScope5060

generalpurpose

CMG Black(3)

PVC (10) Foam PE (5) (8)

CommScope5061

plenum-rated

CMP Natural Kynar FoamFEP

(6) (9)

Belden3093A

plenum-rated

CMP Gray fluoro-copolymer

FoamFEP

(6) (9) Belden states this cableis suitable for Outdoorand Direct Burialapplications.

CommScope5060B

direct-burial Black PE Foam PE (5) (8) Not armored

Belden123092A

interlockedaluminum

armor

Black PVC Foam PE (5) (8) See note 13

Belden133092A

interlockedsteel armor

Black PVC Foam PE (5) (8) See note 13

Belden543092A

corrugatedaluminum

armor

Black PE Foam PE (5) (8) See note 14

Belden553092A

corrugatedsteel armor

Black PE Foam PE (5) (8) See note 14

CommScope5060A

corrugatedaluminum

armor

Black PVC (10)

(11)(16)Foam PE (5) (8) Armor layer plus outer

PVC jacket. Jacket alsoavailable in PE.

CommScope5060C

continuouscast armor

Black PVC (10)

(11)Foam PE (5) (8) Jacket also available in

PE.Belden1191A

messenger Black PVC (10) Foam PE (6) (8) Separate messengerwire.

CommScope5060M

messenger Black PVC (10)

(11)Foam PE (5) (8) Separate messenger

wire. Jacket alsoavailable in PE.

BeldenYR-28890

hi-flex CM Black PVC (10) Foam PE (6) (8) More flexible centerconductor and shields.

CommScope5060F

hi-flex CMG Black(3)

PVC (10) Foam PE (6) (8) More flexible centerconductor and shields.

See Notes next page…



Table 15. Honeywell-Recommended ControlNet Coaxial Trunk Cable Types (cont'd)Notes:

1. ControlNet is a registered trademark of ControlNet International, Ltd.

2. Meets electrical/mechanical requirements of standard trunk cable 51192416

3. Other jacket colors (white, red, blue, green, orange, brown, yellow, violet, or gray) available if specially ordered

4. Standard raw trunk cable used in Honeywell-supplied, pre-assembled trunk cable assemblies TC-KCCX01 through TC-KCC500

5. Electrical characteristics are the same as standard ControlNet trunk cable 51192416

6. Electrical characteristics are the same as standard ControlNet trunk cable 51192416 except greater attenuation results in lessdistance capability than 51192416 cable

7. Standard ControlNet trunk cable connector 51192417-100 is Amphenol part # 31-71000-RFX used in Honeywell-supplied pre-assembled trunk cable assemblies TC-KCCX01 through TC-KCC500

8. Connector specified in note 7 above should be usable because cable diameter and jacket thickness dimensions are the sameas (or very close to) standard 51192416 cable

9. Connector specified in note 7 above may not be usable because cable diameter and jacket thickness dimensions are smallerthan standard 51192416 cable

10. Cables with PE (polyethylene) jacket last longer outdoors than cables with PVC jacket. Protect PVC cables outdoors byplacing them in conduit away from moisture.

11. This cable is also available with PE jacket

12. All cables in the table above are 75-ohm, RG6/U-style, quad-shield (foil/braid/foil/braid) cables with suitable electricalcharacteristics for ControlNet networks

13. Belden states this armored cable can be used outdoors (without conduit protection) but not for direct burial. Basically it isBelden 3092A cable with armoring and outer PVC jacket.

14. Belden states this armored cable can be used outdoors (without conduit protection) and also for direct burial (due to moistureimmunity of jacket and underlying tape). Basically it is Belden 3092A cable with armoring, flooding, and outer PE jacket.

15. Refer to supplier’s datasheet for approval information printed on cable jacket, especially for approvals needed for Canadianapplications

16. CommScope states that the armor is also available in interlocked aluminum or steel



Topologies and Configuration Examples

PlantScape Hybrid Controller “Models at a Glance” ExampleBased upon ControlNet

Figure 18. Model Number Example

The above example is meant to illustrate typical component model numbers necessary for a smallsystem. It does not include software components and is not intended as the basis for placing aPlantScape System order. A power supply always attaches to the left-end of a rack and does not useany rack slots.

The Supervisory ControlNet is a physically separate network from the I/O ControlNet (both shown).This network carries supervisory messages between the PlantScape Server and Controllers as well aspeer-to-peer messages between controllers. The I/O ControlNet carries messages between controllersand IOMs. A ControlNet Tap consists of two BNC connectors for trunk line cable connection, anintegral 1-meter drop cable, and a BNC connector for ControlNet Interface (CNI) connection. Severalphysical models are available to accommodate different mounting layouts.

Other PlantScape operator stations connect to PlantScape via a LAN above the Server, not via theSupervisory ControlNet.

TC-FXX102 -- 10-slot rack

TC-PRS021 -- C200Control ProcessorTC-CCR013 --

ControlNet Inter face(CNI), RedundantMedia

TC-FPCXX2 --120/240 VACPower Supply

TC-PCIC01 - - ControlNetCommunication InterfaceModule for PC ( redundantmedia) (in server)

Terminators --TC-TCXBNC

Taps - - 9904-TPS, R,YS, and YR (4 kinds)

PlantScape Server(sta tions not

shown)

(Optional) TC-CCR013 - -CNI to connect to otherI/O racks

Main ControllerRack

Additional orRemote I/O Rack

TC-CCR013 -- CNI,Redundant Media

I/O modules and terminal blocks

LAN Connection - -Ethernet, TCPIP, etc.

ControlNet Cable (TC-KCCxxx) - Supervisory

ControlNet



PlantScape Hybrid Controller “Models at a Glance” Example

Based on Ethernet

Figure 18. Ethernet Topology Example

R320 introduces Ethernet communication from the server to the controller. This enhances flexibilitybased upon open technology. Ethernet connectivity exists on the supervisory network and as a meansto connect external devices (such as PLC5s, etc.). It includes switched network topology and 10 MBTCP/IP support. The new Honeywell module, TC-CEN011, connects via a 10BaseT Ethernet Cableconnector.

The Supervisory ControlNet is a physically separate network from the I/O ControlNet (both shown).The Supervisory network can now be based on Ethernet instead of ControlNet. It carries supervisorymessages between the PlantScape Server and Controllers as well as peer-to-peer messages betweencontrollers. The I/O ControlNet still based on ControlNet, carries messages between controllers andIOMs.

The above diagram depicts a basic Ethernet topology implementation. Key Configuration Rulesinclude:

• Only a Switched Ethernet Supervisory (Server to Controller) topology is supported. Only Non-Redundant C200 Controllers may be used with an Ethernet Supervisory Control Network, wherethe Ethernet is in a Control Rack. However, you can use the Ethernet Module with RedundantC200 Controllers for peer-to-peer exchange when it's located in the I/O Rack.

• Support for ControlNet and Ethernet to different C200 Controllers simultaneously from the sameServer is not supported in R320.

• A downlink ControlNet segment must be used to support remote I/O. An Ethernet Module, locatedin an I/O rack, can be used to Exchange peer-to-peer with external devices.

• The PCIC ControlNet PC card is not needed. Instead, an Ethernet NIC card must be installed inthe PC. A separate PC Ethernet Interface card is required between the Server and the Stations.

PlantScape Stations

Redundant PlantScapeServer

Ethernet (TCP/IP)

ControlNe t

Ethernet

PLC5/E

SecondRedundant PlantScapeServer

Ethernet (TCP/IP)

Ethernet

ControlNe tTC-CEN011 - Ethe rne t Interf ace M odule Switch

TC-CEN011 - Ethe rne tInterface Module



“Controller Redundancy at a Glance” Example

Figure 19. Redundant Controller Configuration Example

The above example illustrates some key configuration rules and requirements for ControllerRedundancy. These include:

• Specific models that support redundancy must be used in both chassis of a redundant chassis pair: C200Control Processor (TC-PRS021), ControlNet Interface (TC-CCN013/ TC-CCR013), and Redundancy Module(TC-PRR021).

• I/O Modules are not permitted in either chassis of a redundant chassis pair. IOMs do not supportredundancy at this time.

• Both chassis of a redundant chassis pair must have identical slot-for-slot configurations (i.e., same locationin both chassis).

• CNIs in chassis containing I/O modules do not have to support chassis redundancy.• All CNIs on any ControlNet network must support either Single Media or Redundant Media, but not a mixture

of both.

Up to four (4) I/O CNIs can be used to connect to IOM chassis, with a maximum of 24 IOMs supportedper CNI. Note that support for 64 IOMs (the maximum per controller) only requires 3 CNIs. All I/OCNIs may share a single ControlNet trunk cable, or individual cables may be used as needed. As anexample, a controller with 3 I/O CNIs could use a single I/O ControlNet cable, two I/O ControlNetcables or three individual cables. All three configurations would be valid.

Honeywell

OK

TC-FXX072 -- 7-slot Chassis

Redundant ChassisIdentical Configuration(module-for-module)

TC-CCR013 -- CNI,Redundant Media

TC-FPCXX2 --120/240 VACPower Supply

ControlNet Cable (TC-KCCxxx) -- Supervisory

Terminators --TC-TCXBNC

TC-CCR013 -- CNI toconnect to I/O chassis

TC-PRR021 --RedundancyModule

toServer

OK

Honeywell

NO IOMs PERMITTED IN CONTROLLERCHASSIS FOR

CONFIGURATION!!

ControlNet Cable -- I/O Comm

toChassis

GN-KRRxx1 -- RedundancyCable (Fiber

TC-PRS021 -- C200Control Processor

NO IOMs or ETHERNET MODULESPERMITTED IN CONTROLLER CHASSISFOR REDUNDANT CONFIGURATION!!



“FOUNDATION Fieldbus at a Glance” Example

Figure 20. FOUNDATION Fieldbus Integration Example

The above example illustrates key configuration rules and requirements for supporting Fieldbusintegration using the Linking Device, NI Configurator Software, and RSLINX . Specific rules toconsider when configuring your integrated system include:

! Support for FOUNDATION Fieldbus requires the Linking Device (1757-CN2FF). Each Linking Devicesupports up to two (2) FOUNDATION 31.25 kbaud H1 networks. Each network is permitted tosupport no more than 10 FOUNDATION Fieldbus devices. Up to eight (8) Linking Devices can beused on a single I/O ControlNet segment.

! Each Linking Device requires separate 11-30 VDC power (nominally 24 VDC) at 270 mA. ALinking Device does not provide power to the H1 network. Power, conditioning and networktermination must be provided separately. Refer to Fieldbus FOUNDATION Specifications fordetailed rules and topology.

! PlantScape Process software version R310 or greater is required. The National InstrumentsFieldbus Configuration Package (TC-NIFB01) configures the Foundation Fieldbus devices. Allen-Bradley RSLINX Software (MZ-NTTP02) is required for the NI Configuration Package to functioncorrectly.

��

1757-CN2FF -Linking Devices

(DIN Rail Mounted)

PTPT ��

��

��

��

��PTPT

��

H1 Network (2)

FOUNDATION Fieldbus Device Networks

��

��H1 (1)

H1 (2) Remote I/O Chassis - Series A

ControlNet, Redundant Media

��24 VDC

Condit ionedPower

24 VDCCondit ioned

Power

ControlNet

RedundantControl

Processor

Non-RedundantControl

Processor

TC- CCR013, ControlNet

PlantScape Stations

RedundantPlantScape

Servers

Ethernet (TCP/IP)

��

��H1 (1)

H1 (2)

High AlarmLow AlarmComm. Err.

High AlarmLow AlarmComm. Err.

ControlNet

H1 (2)

H1 (1)

TC-NIFB01 - NI Configurator SoftwareMZ-NTTP02 - RSLINX Software

H1 Network (1)



Model Numbers

Table 16. Controllers, Racks, Power Supplies & Communications ModulesModel Description Uncoated Model

NumberCoated Model

Number 1

Hybrid Controller

C200 Control Processor 2 TC-PRS021 TK-PRS021

Battery Extension Module TC-PPD011

Redundancy

Redundancy Module TC-PRR021 TK-PRR021

Redundancy Cable 1 Meter GN-KRR011



Racks

4 Slot Rack TC-FXX042


10 Slot Rack TC-FXX102 TK-FXX102

13 Slot Rack TC-FXX132 TK-FXX132


Power Supplies

120/240 VAC Power Supply TC-FPCXX2 TK-FPCXX2

24 VDC Power Supply TC-FPDXX2 TK-FPDXX2

Communication

ControlNet Interface (single media) 3 TC-CCN013

ControlNet Interface (redundant media) 3 TC-CCR013 TK-CCR013

Ethernet Interface Module TC-CEN011

Allen-Bradley Fieldbus Linking Device 1757-CN2FF

ControlNet ISA Interface 4 9904-KTCX15

ControlNet PCI Interface 4 TC-PCIC011

Conformal coating optional except as noted.2

Each operating Control Processor or Redundant Control Processor Pair requires purchase of oneControl Solver license, TC-SWCS11 or TC-SWCS21. Note that the actual software is included withthe PlantScape Process Server Software, MZ-PSPBxx. TC-SWCS11 and TC-SWCS21 consist of thelicense to use this software.

3 The Series “D” (Tx-CCx013) ControlNet Interface Modules ship with R310 and later. They displacetheir corresponding model numbers from Series “C” (Tx-CCx012). The Linking Device requires theuse of either the new Series CNIs or the previous Series “C with updated R310 firmware.

49904-KTCX15 and TC-PCIC01 are used with both dual and single ControlNet media. 9904-KTCX15will be replaced in R320 by TC-PCIC01. 9904-KTCX15 is only available for R310 and earlier systemsand replacements.



Rack Configuration ServicesModel Number Model Description

TC-RCFG01 Rack Configuration Service, per rack

TC-RCFG01 is a per-rack configuration service for any size rack. It includes the following:• Installing Power Supply, Controllers, CNIs, RMs, BEMs, IOMs and Terminal Blocks per customer’s configuration• Loading correct firmware in all Controllers, CNIs, RMs, and IOMs, and setting initial parameters on CNIs• Testing that all Rack components pass power up diagnostics

Without TC-RCFG01, Controllers, IOMs, Terminal Blocks, Power Supplies and other components are shipped in theiroriginal factory containers. Customers are then responsible for making sure all Controllers, RMs, IOMs, CNIs, andKTC cards have the appropriate firmware and loading if necessary (instructions are included with the system). If aServer is purchased, PlantScape Server software is loaded and the ControlNet Interface card is configured regardlessof whether or not TC-RCFG01 is purchased.

• For CIOM-Series A I/O models and specifications, refer to PS03-232, PlantScape I/O Specification and Technical Data.• For RIOM -Series H I/O models and specifications, refer to PS03-532, Rail I/O Modules Series H Specification and Technical Data.• For RIOM - Series A I/O models and specifications, refer to PS03-632, Rail I/O Modules Series A Specification and Technical Data.

Table 17. Miscellaneous Hardware

Model Number Description

TC-LABL01 I/O Door Label

TC-XXXXX1 Blank Cover Modules (Qty 2)

TC-BOOT01 Backplane Connector Boot

TC-BATT01 Spare Battery -- Control Processor

TC-BATT03 Spare Battery – Battery Extension Module (BEM)

Figure 20. Illustrations of Different ControlNet Tap Styles

T-Style Taps Y-Style Taps

9904-TPS(straight)

9904-TPR(right angle)

9904-TPYS(straight)

9904-TPYR(right angle)



Table 18. Terminal Blocks, Cables and ConnectorsModel Number Description

I/O Module Terminal Blocks

TC-TBNH I/O Module Field Wiring Conn., 20 position – screw

TC-TBCH I/O Module Field Wiring Conn., 36 position -- screw

ControlNet connectors and terminators

TC-MC1BNC Connector, BNC/RG-6 plug (for Trunk Cables, Pkg. of 2)

TC-MC2BNC Connector, BNC, bullet (Jack-to-Jack, Pkg. of 2)

TC-MC3BNC Connector, BNC, barrel (Plug-to-Plug, Pkg. of 2)

TC-MC5BNC Connector, BNC, isolated bulkhead (Jack-to-Jack, Pkg. of 2)

TC-MC6BNC Connector, BNC, right angle (Jack-to-Plug, Pkg. of 2)

TC-TCXBNC ControlNet Terminator (BNC, Pkg. of 2)

9904-CTK ControlNet Coax Network Tool Kit

1786-TCAP Tap Dummy Load (Pkg. of 5)

ControlNet Interface Products *

9904-RPT ControlNet Repeater Coax (120/240 VAC)

9904-RPTD ControlNet Repeater Coax (24 VDC)

9904-CP ControlNet Network Access Cable

TC-RPFS01 ControlNet Repeater Fiber Optic (300 M)

TC-RPFM01 ControlNet Repeater Fiber Optic (3000 M)

TC-RPA001 ControlNet Modular Repeater Adapter

ControlNet Taps (see below)

9904-TPS T-Tap Straight

9904-TPR T-Tap Right angle

9904-TPYS Y-Tap Straight

9904-TPYR Y-Tap Right angle

ControlNet Trunk Cable (with connectors)

TC-KCCX01 1 meter

TC-KCCX03 3 meters

TC-KCCX10 10 meters

TC-KCCX30 30 meters

TC-KCCX50 50 meters

TC-KCC100 100 meters



TC-KCC900 275 meters (no connectors)

Note: Refer to ControlNet Cable System Planning and Installation Manual for details* Coax Repeaters are not FM approved. Only Fiber Optic Repeaters have FM approval: TC-

RPFS01, TC-RPFM01 and TC-RPA001.



Table 19. Hybrid Controller Software

Model Number Model Description

TC-SWCS11 1 CS01 Control Solver (license only)

TC-SWCS21 1 CS02 Control Solver 5 msec CEE (license only)

TC-SWCB11 2 CB10 Control Builder - CL01 Continuous Library

- SL01 Sequential Library

TC-SWCB31 3 CB10 Control Builder Client License

TC-NIFB01 National Instruments Fieldbus Configuration Package(required, along with MZ-NTTP02, RSLINX, to configure FF devices)

1One CS01 or one CS02 license is required to be purchased for each individual operating ControlProcessor or Redundant Control Processor pair. Software is provided as a part of PlantScapeBase Server System Software, MZ-PSPBxx, but the license is not included.

2One license is included as a part of PlantScape Base Server System Software, MZ-PSPBxx.Must purchase an individual license for each separate usage.

3TC-SWCB31 allows ControlBuilder access to engineering databases via TCP/IP and UDP/IPcommunications. It can be run in clients loaded with Station or Server. A login dialog providesaccess restriction. Each database can be accessed simultaneously by up to four (4) clients. Alicense is required for each accessing client.

Table 20. PlantScape Station Software


MZ-NTUL04 PlantScape Process Station - 1 User





Table 21. PlantScape Server/Station Hardware


PlantScape Server/Station Hardware & Options

MZ-NTPC02 Performance Server PC/NT

MZ-NTPC03 Operator Station PC/NT

MZ-NTPC04 PlantScape Mini Server PC loaded w/ NT Workstation

MZ-PCRT05 High Resolution 17" Monitor

MZ-PCRT06 High Resolution 21" Monitor

MZ-PCEB21 Ethernet Comm. Board, 100mbs

MZ-PCDT03 Terminal Server-8 RS232 Ports, RJ45

MZ-PCEB12 8 Port RS-232/422/485 PCI Bus Serial Board

MZ-PCEB11 8 Port RS-232/422/485 Expansion Module

MZ-PCDU03 1 Honeywell Univ. Station Membrane Keyboard 110/220V

MZ-PCDB01 Honeywell TDC3000 High Performance Data Hiway Bridge

MZ-PCDD06 Trackball w/PS-2 Connector

MZ-PCEM01 Tape for ZIP Substitution

MZ-PCEM02 128 MB DIMM Memory Expansion Module

TC-PSMP01 PlantScape Mouse Pad

TC-PSKY01 PlantScape Keyboard Overlay1 MZ-PCDU03 includes keyboard, cable and PC interface card. Qualified for use with both PlantScape SCADA

and PlantScape Process. TP-DIKBNA, Desktop Integrated Keyboard w/o Trackball, also supported; see GUSdocumentation for product details.

Table 22. Distributed Server Architecture (DSA) Licenses


Base Server System (Software & License)

MZ-NTDS00 1 DSA Enabling License (Required for DSA)

MZ-NTDS01 DSA License, Maximum 2 Remote Servers



MZ-NTSE01 DSA License Expansion, Max 2 To Max 5 Servers

MZ-NTSE02 DSA License Expansion, Max 5 To Max 10 Servers1

Every server that is to participate in a Distributed Server Architecture (DSA) system must include MZ-NTDS00.DSA requires the use of areas; this item prevents disabling the use of areas on the Server.



Table 23. PlantScape Process Server SoftwareModel Number Model Description

MZ-PSW320 1 PlantScape Media and Documentation for R320MZ-PSW310 1 PlantScape Media and Documentation for R310

Base Server System Software (License Only)

MZ-PSPB02 Process Base Server Software 50 Cont Mods/Points




MZ-PSPB06 Process Base Server Software 1,000 Cont Mods/Points






Server Database Point Count Expansion Software (License Only)

MZ-PSBE02 Process Base Server Software 50 to 100 Point Expansion



MZ-PSBE05 Process Base Server Software 650 to 1,000 Point Expansion

MZ-PSBE06 Process Base Server Software 1,000 to 2,000 Point Expansion





MZ-PSPBxx includes Controller & System Documentation, Control Solver software (licenses mustbe purchased separately), Control Builder (one license included), and Station (one licenseincluded). MZ-PSBExx allows Base System Server size expansion. Note that MZ-PSPBxxincludes all components of the SCADA Development Base System Software, MZ-NTBDxx, exceptfor the one included driver, and performs all SCADA functions as well.

1MZ-PSW320 and MZ-PSW310 contain release-specific software, documentation, mouse pad,overlay, promotional CD and packaging. They cannot be ordered separately. When orderingthrough e.BOB or the TPC, one copy is included with MZ-PSPBxx.



Table 24. PlantScape Process Server Software – Redundancy Options

Server Redundancy Software Adder -- Must Match Base System Size (License Only)

MZ-PSPR02 Process Server Redund Software - 50 Point




MZ-PSPR06 Process Server Redund Software – 1,000 Point






Server Expansion Redundancy Software Adder (License Only)

MZ-PSRX02 Process Server Redund Software 50-100 Point Expansion



MZ-PSRX05 Process Server Redund Software 650-1,000 Point Expansion

MZ-PSRX06 Process Server Redund Software 1,000-2,000 Point Expansion





Redundancy Option does not include a Station License and must match base Server size.



Table 25. PlantScape Software Options and ToolsModel Number Model Description

Third-Party Communication Interface Software

MZ-NTTP01 1 Allen-Bradley RSLINX Software, Ver 1.7 (for R130 and earlier)

MZ-NTTP02 1 Allen-Bradley RSLINX Software, Ver. 2.0 (R200 and later)

PlantScape Communication Interface Software

MZ-NTIF01 Honeywell S9000 Ethernet Interface Software

MZ-NTIF02 Honeywell 620 LC Serial and Ethernet Interface Software

MZ-NTIF03 Honeywell TDC 3000 Data Hiway Interface and Configuration Software

MZ-NTIF04 Honeywell UDC 3000/5000/6300 Interface and Configuration Software

MZ-NTIF05 Modicon PLC, MODBUS RTU Interface Software

MZ-NTIF06 Allen-Bradley PLC Base Serial Interface (Does not require RSLINX)

MZ-NTIF07 Allen-Bradley PLC Base RS-LINX Interface

MZ-NTIF08 Allen-Bradley Integration

MZ-AUIF01 2 GE API License

MZ-NTIF10 GE Fanuc Series 90 PLC ( 90-30/90-70 ) via Ethernet(requires MZ-AUIF01)

MZ-NTIF11 Honeywell XLNET HVAC Controller Interface Software

MZ-NTIF12 Siemens S5 &TI PLC Via H1 / TF API

MZ-NTIF13 Honeywell Micromax LPU & Video Paperless Recorder

MZ-NTIF15 Fieldbus Interface Software

MZ-NTIF16 Advanced DDE Client

MZ-NTIF18 GEC GEM80 PLC

MZ-NTIF19 MA500 Interface

MZ-NTIF20 SQUARE D Interface

MZ-NTIF22 DPR Recorders (DPR 100, 180, 3000)

MZ-NTIF23 RM7800 Flame Safeguard

MZ-NTIF24 Bristol Babcock RTU

MZ-NTIF25 Moore 351,352,353,383 controllers

MZ-NTIF26 Bailey InfiNet 90 Interface

MZ-NTIF27 Applicon

MZ-NTIF28 FSC Serial Modbus

MZ-NTIF29 HITACHI INTERFACE

MZ-NTIF30 FS90 Interface

MZ-NTIF32 OPC Client Interface

MZ-NTIF33 Asea Interface

MZ-NTIF34 Universal Modbus Interface

MZ-NTIF35 Moore APACS Interface 1

Required for Server communication support to AB PLC products, whether over ControlNet, Ethernet,or Data Hiway+. Also required when using the Fieldbus Integration Package (TC-NIFB01) and theLinking Device (1757-CN2FF). Only version 2.1 (currently being shipped) is supported for FieldbusIntegration.

2 Required for MZ-NTIF10.

All models above are Licenses only.



Table 26. PlantScape Software Options and Tools (cont’d)PlantScape Common Application Enabler Software

MZ-NTAE01 Recipe Manager

MZ-NTAE02 Point Control Scheduler

MZ-NTAE03 Downtime Analysis

MZ-NTAE04 Statistical Process Quality Control

MZ-NTAE05 ODBC Data Exchange

MZ-NTAE08 Extended Event Archiving

MZ-NTAE09 Alarm Pager

PlantScape Common Developers Software Options

MZ-NTDE04 Application Development Toolkit

PlantScape Common Network Enabler Software

MZ-NTNE02 Network Node Interface Software

MZ-NTAD01 Open Data Access -- 1 User

MZ-NTAD02 Open Data Access -- 5 Users

MZ-NTAD03 Open Data Access -- 10 Users

PlantScape Additional Engineering Tools(Extra Copies For Off-Line Use)

MZ-NTET01 Quick Builder - SCADA database builder

MZ-NTET02 Display Builder for Windows

MZ-NTET03 S9000/620 LC Configuration Tools

All models above are Licenses only.



Table 27. SCADA to Process Server Conversion SoftwareModel Number Model Description

SCAN 3000 or PlantScape SCADA-PlantScape Process (License Only)

MZ-PSSU01 SCADA to Process Conversion, 20 Points*

MZ-PSSU02 SCADA to Process Conversion, 50 Points*

MZ-PSSU03 SCADA to Process Conversion, 100 Points



MZ-PSSU06 SCADA to Process Conversion, 1,000 Points






*Conversion to 100 Point Process System


SCAN 3000 or PlantScape SCADA to PlantScape Process Redundancy (License Only)

MZ-PSRU01 SCADA To Process Redundancy, 20 Points





MZ-PSRU06 SCADA To Process Redundancy, 1,000 Points








Table 28. PlantScape DocumentationModel Number Model Description

PlantScape Printed System Documentation

TC-DCXX11 PlantScape Overview

TC-DCXX21 PlantScape Planning

TC-DCXX31 PlantScape Process Startup and Shutdown Guide

TC-DCXX51 PlantScape Hybrid Controller Installation Guide

TC-DCXX61 PlantScape Control Building Guide

TC-DCXX71 PlantScape Reference(Contains of TC-DCX101, PlantScape Control Builder Reference, TC-DCX111,PlantScape Troubleshooting and Notifications Reference, and TC-DCX121,PlantScape Control Specifications Reference.)

TC-DCXX81 PlantScape Theory

TC-DCX131 PlantScape Rail I/O – Series H Implementation Guide

TC-DCX151 PlantScape Linking Device Implementation Guide

TC-DCX171 PlantScape Rail I/O - Series A Implementation Guide

TC-DCX181 PlantScape Network Planning Guide

SCADA Printed System Documentation

TC-DSXX11 PlantScape Application Development Guide

TC-DSXX21 PlantScape Server and Client Configuration Guide

TC-DSXX31 PlantScape Display Building Guide

TC-DSXX41 PlantScape Operator's Guide

TC-DSXX51 PlantScape Server and Client Installation Guide

TC-DCS101 PlantScape Statistical Process & Quality Control User’s Guide

TC-DSX111 PlantScape Controllers Reference

TC-DSX121 PlantScape Administration and Startup Guide

PlantScape Documentation Accessories

TC-DCXX91 PlantScape Process System Documentation Set(Contains TC-DCXX11, DCXX21, DCXX31, DCXX41, DCXX51, DCXX61,DCXX81, DSXX11, DSXX21, DSXX31, DSXX51, DCX131, TC-DCX151)

TC-DCSX11 PlantScape Pre-Sales Documentation Set (contains TC- DCXX11,DCXX21, DCX121)

TC-DCSX21 1 Getting Started With PlantScape

TC-DCSX31 PlantScape Software Installation and Upgrade Guide

TC-DCDX11 2 PlantScape Knowledge Builder Documentation (CD-ROM for 1 Server)

TC-SDOC01 PlantScape Site Docs

TC-DPQ001 PlantScape Product Qualification Handbook1 One copy included with each PlantScape Process Server system shipped.2 Included with Process Base Server Software MZ-PSPBxx.



Table 29. PlantScape Demonstration UnitModel Number Model Description

TC-DEMO11 PlantScape Demonstration System

TC-DEMOC1 PlantScape Demo System Case

TC-DSW3201 PlantScape Demo Media and Documentation for Release 320

TC-SWDEMO2 PlantScape Demonstration Software License1

Contains release-specific software, documentation, mouse pad, overlay, promotional CD and packaging. Oncecopy is included when the license,TC-SWDEMO, is ordered. The latest release is always assumed unlessotherwise specified.

2Can be ordered separately for standalone SCADA demo use.

Upgrade and Previous Release Demo Software

TC-DUG320 PlantScape Demo Ugrade Media and Documentation for R320

The PlantScape Demonstration Unit provides a portable, self-contained system which can beused for demonstrations and training purposes. It does not include the server or monitor, butincludes all needed hardware components, including a simulator panel which interfaces with thecontroller I/O Modules.

The Demonstration Unit is ordered in three parts:• Demonstration System (TC-DEMO11, see below)• Demonstration Case (TC-DEMOC1)• Demonstration Software License (TC-SWDEMO)• R320 Release-Specific Demo Software Package (TC-DSW320)

Note that the System and demo software can also be ordered as a separate package forPlantScape SCADA demos.

A list of components included in TC-DEMO11 is given in the table below.

Table 30. TC-DEMO11 Contents

Model Number Description Qty

TC-PRS021 C200 Control Processor 1

TC-CCR013 ControlNet Interface (CNI), Redundant Media 1

TC-FPCXX2 AC Power Supply 1

TC-FXX102 10 Slot Chassis 1

TC-IAH061 Analog IN 4-20MA 1

TC-OAH061 Analog OUT 4-20MA 1

TC-IDJ161 24VDC ISOL DI 1

TC-ODJ161 24VDC ISOL DO 1

TC-PCIC01 ControlNet Interface (CNI) for PC 1

TC-TBNH 20 Position NEMA Connector 2

TC-TBCH 36 Position NEMA Connector 2

9904 TPR CN Taps 2

TC-TCXBNC Terminators (package of 2) 1

TC-XXXXX1 Blank Panels 2

TC-MC3BNC Connector, BNC, Barrel (package of 2) 1



Appendix A: Server Hardware Requirements

Honeywell offers the latest PCs for optimal server performance. Should a PlantScape customer needto purchase their PC independently, the following requirements must be followed. Honeywell does notsupport customer-purchased PC hardware nor PC operating software. However, with Carbon Copy 32software installed (included with R320), Honeywell will support the installed PlantScape software.

The number of Servers and Stations does not determine system configuration. If a large and complexprocess is being considered, this will effect the size of the database. For example, a configuration mayrequire passive monitoring and occasional report generation, but the process is large and complex.Therefore, it would be preferred to install a system which matches the medium system rather than thesmall system. Use the table below to approximate your database size.

Table 1.1. Database Sizing Chart

SystemSuggestion

Definition DatabaseSize

Configuration Examples

Small May consist of:

! 1 non-redundant Server

! 1 station

! Passive monitoring andoccasional report generation

0-200 MB ! 1 Hybrid Controller *

! Process systems with up to 100CM/SCM/IOM

! SCADA systems with up to3,000 Points

Medium May consist of:

! 1 non-redundant Server andmultiple stations OR

! 2 redundant Servers with nomore than 2 additionalstations and 1 DSA Server.

! 1 or 2 stations

! Active monitoring withoccasional report generation

200-350MB

! 2-3 Hybrid Controllers *

! Process systems with up to 500CM/SCM/IOM

! SCADA systems with up to10,000 Points

LargeWorkstation

May consist of:

! 2 redundant Servers

! Multiple DSA Servers

! Up to 8 Stations

! Active monitoring frommultiple Stations

350-500MB

! More than 3 - 4 HybridControllers *

! Process systems with 500 - 600CM/SCM/IOM

! SCADA systems with more than10,000 points.

Large Server May consist of:

! 2 redundant Servers

! Multiple DSA Servers

! Up to 20 Stations (40 forSCADA

! Active monitoring frommultiple Stations

!

Greaterthan 500

MB

! 5 or more Hybrid Controllers *

! SCADA systems with more than10,000 points

! Process systems with more than600 CM/SCM/IOM

* Hybrid Controllers configured in a redundant mode should be counted as 1 Hybrid Controller.



Table 1.2. Minimum Platform Requirements based on System Configurations

Server Station

SystemConfiguration

Small Medium Large Small Med Large

Processor 266-400MhzPentium II

550 MhzPentium II

800 MhzPentium IIIor higher

200 MhzPentium Pro

300 – 400MhzPentium II

550 MhzPentium III orhigher

RAM

• Win 95/98 -- -- -- 64 MB 64 MB 96 MB

• Win NT Workstation

64 MB 1

96 MB 1 128 MB 64 MB 64 MB 96 MB

• Win NT Server 96 MB 1

128 MB 1 160 MB --

VideoResolution 2

1024 x 76865K colors






Hard Drive 2 GB 4.3 GB 9.1 GB 2 GB 4.3 GB 4.3 GB1

In these configurations, paging may occur on these systems.. Based on the intended usage of the platform, this configurationis acceptable. For better performance, users should upgrade the systems with an additional 64 MB of RAM.

2 The Video Memory required to support this resolution varies by Video Module type, PC Bus supported, and ManufacturersSpec. Please refer to Video Card Specifications for details. All systems should be set 1024 x 768 with 65K colors. Mhzsetting should be set to match the monitor

Table 1.3. Typical Platform Requirements based on System Configurations

Server Station

SystemConfiguration

Small Medium Large Small Med Large

Processor 266 - 400MhzPentium II

550 MhzPentium III


200 MhzPentium Pro


550 MhzPentium III orhigher

RAM

• Win 95/98 -- -- -- 64 MB 64 MB 96 MB

• Win NT Workstation

160 MB 192 MB 224 MB 80 MB 80 MB 112 MB

• Win NT Server 160 MB 224 MB 288 MB -- -- --

VideoResolution







Hard Drive 4.3 GB 4.3 GB 9.1 GB 2 GB 4.3 GB 4.3 GB

1 The Video Memory required to support this resolution varies by Video Module type, PC Bus supported, and ManufacturersSpec. Please refer to Video Card Specifications for details. All systems should be set 1024 x 768 with 65K colors. Mhzsetting should be set to match the monitor.



Table 1.4. High Performance Platform Requirements based on System Configurations

Server Station

SystemConfiguration

Small Medium Large Small Medium Large

Processor 300-400MhzPentium II

550 MhzPentium III


266 MhzPentium II



RAM

• Win 95/98 -- -- -- 64 MB 64 MB 96 MB

• Win NTWorkstation

160 MB 224 MB 256 MB 96 MB 96 MB 128 MB

• Win NT Server 192 MB 224 MB 320 MB -- -- --

VideoResolution

11024 x 76865K colors





1024 x768 65Kcolors

Hard Drive 4.3 GB 4.3 GB 9.1 GB 4.3 GB 4.3 GB 4.3 GB1 The Video Memory required to support this resolution varies by Video Module type, PC Bus supported, and

Manufacturers Spec. Please refer to Video Card Specifications for details. All systems should be set 1024 x 768 with65K colors. Mhz setting should be set to match the monitor.



Table 1.5. Application Usage Chart

From the prior tables, Server configuration memory allocations assume server services only. Station Clientmemory usage already includes the PlantScape Client Applications. However, most applications can be run oneither the Servers or Station Clients. On small to medium systems, these applications may be run on theServer Platforms. RAM should be upgraded on these systems to accommodate each of the applicationsintended to be used on a regular basis. 1

On large systems, the Servers should be dedicated to running only the Server Services. On thesesystems, when possible, all applications should be run from the client stations.

Application RAM Usage

NT Applications

Explorer 4 MB

User Manager 2 2 MB

Disk Administrator 2 2 MB

Event Viewer 2 MB

Task Manager 2 2 MB

Internet Explorer 6 MB

NT Backup 3 MB

PlantScape Applications

Station 3 5 MB

Control Builder 13 MB

Network Tools 2 3 MB

Quick Builder 2 10 MB

DB Admin 2 10 MB

Import Export Tool 2 7 MB

Knowledge Builder Adds 2 MB on top of Internet Explorer

Other Applications RAM Usage

Total Plant Batch

(Includes multiple NT Services and Applications)

128 MB

Microsoft Excel 7 MB

Microsoft Excel with Data Exchange 10 MB

Microsoft Word 13 MB

Upgading Options

Non-Redundant to Redundant SCADA 32 MB (per Server node)

Non-Redundant to Redundant Process 32 MB (per Server node)

Non-DSA to DSA Architecture 64 MB (per Server node)

10 Station SCADA to 20 Station SCADA (Server) 32 MBNotes:1 Application usage on Servers greatly effects the CPU resources. A CPU upgrade or platform upgradeshould be considered if your primary usage of the applications will be on the Servers. On Redundant Systems,primary application usage should be on the Backup Server.2 These applications are more for configuration and typically are not run all the time. They represent a one-time memory allocation when running. When considering additional RAM requirements, you should onlyinclude those applications in which you intend to run on a daily or constant basis.3 The “Station” application effects the Station and Server Node. The memory should be added on bothphysical boxes per application. For Example, if the server is going to support 5 Stations, then you would requirean additional 25 MBs. (5 x 5)



PlantScape is a U.S. trademark of Honeywell, 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 ofmerchantability 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.

Printed in U.S.A. — © Copyright 1999 - Honeywell Inc.Honeywell

Industrial Automation and Control16404 N Black Canyon Hwy

Phoenix, AZ 85023(602) 313-5000

Documents

Plants Cape Process System and Controller