You are on page 1of 70

PlantScape

Process System and Controller


Specification and
Technical Data

PS03-132
Release 320
Revision Date: 27 October 2000
Version 1.0

Release 320 Ver. 1.0


PS03-132 Ver 1.0
Page 2 Release 320

PlantScape Process System & Controller


Specification and Technical Data
Table of Contents Page
Introduction ..........................................................................................................................4
Product Overview.................................................................................................................4
System Overview .................................................................................................................6
Product Description .............................................................................................................9
Control Processor Modules...................................................................................................................9
Input/Output Modules..........................................................................................................................11
Control Processor Functions -- Control Builder and Control Solver....................................................12
Control Processor Load Performance ................................................................................................14
PlantScape System Overview ...........................................................................................16
PlantScape System Philosophy ..........................................................................................................17
PlantScape Server Key Features.......................................................................................18
Algorithms ...........................................................................................................................................21
Trending..............................................................................................................................................23
User Documentation ...........................................................................................................................30
Specifications.....................................................................................................................33
Controller Function Block Types in CB10 Control Builder ..................................................................33
PlantScape System Performance & Capacity Specifications .............................................................34
PlantScape Server Hardware Descriptions.........................................................................................42
PlantScape Server Sizing Specifications ............................................................................................43
C200 Control Processor Specifications ..............................................................................................44
Chassis Specifications ........................................................................................................................45
Power Supply Specifications...............................................................................................................46
Terminal Blocks, Cables and Connector Sizes...................................................................................46
ControlNet Specifications....................................................................................................................47
Honeywell-Recommended ControlNet Coaxial Trunk Cable Types ...................................................48
Topologies and Configuration Examples .........................................................................50
PlantScape Hybrid Controller Examples .............................................................................................50
Controller Redundancy Example ........................................................................................................52
FOUNDATION Fieldbus Example...........................................................................................................53
Model Numbers ..................................................................................................................54
Controllers, Racks, Power Supplies & Communications Modules......................................................54
Miscellaneous Hardware.....................................................................................................................55
Terminal Blocks, Cables and Connectors...........................................................................................56
Hybrid Controller Software ..................................................................................................................57
PlantScape Station Software ..............................................................................................................57
PlantScape Server/Station Hardware .................................................................................................58
Distributed Server Architecture (DSA) Licenses .................................................................................58
PlantScape Process Server Software.................................................................................................59
PlantScape Process Server Software – Redundancy Options ...........................................................60
PlantScape Software Options and Tools ............................................................................................61
SCADA to Process Server Conversion Software................................................................................63
PlantScape Documentation ................................................................................................................64
PlantScape Demonstration Unit..........................................................................................................65
Appendix A: Server Hardware Requirements .................................................................66

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 3

Revision Status

Revision Date Description


0.1 March 2000 Draft
1.0 27 October 2000 Final version; updated AIOM limits

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 4 Release 320

Introduction

ntroducing the Honeywell PlantScape family of process control solutions from Honeywell.
IPlantScape 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 and
PlantScape Vista. The award-winning PlantScape system sets a new standard in scalable hybrid
control systems by providing the highest level of performance, flexibility, and ease of use at the lowest
life-cycle cost of ownership.
The heart of the PlantScape family is a powerful, open Microsoft Windows NT-based client/server
system. Its advanced architecture encompasses a new, high-performance controller, advanced
engineering tools, and an open control network. PlantScape makes use of new technology that
includes:
• 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 industrial
process control applications call for a number of common elements, such as communications
protocols and control algorithms. PlantScape includes such elements in its standard operating
framework, 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 is
complete, with a minimum of system building required. With PlantScape, the user is up and running in
minimum time!

Product Overview
PlantScape enables increased engineering productivity through graphical object-based tools and a full
library of powerful process control functions. It addresses world-wide regulations and practices in the
process industries and adapts to local language and interfacing customs. The basic system
components 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

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 5
• 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 wide
variety of requirements, including continuous processes, batch processes, discrete operations, and
machine control needs. Compact and cost-effective, the C200 is ideal for integrated regulatory, fast
logic, sequential, and batch control applications. Control functions are provided through a library of
templates called Function Blocks (FBs). Strategies are easily built using a state-of-the-art graphical
engineering tool called Control Builder. Once built, control strategies can be loaded and monitored
using Control Builder.
LAN (TCP/IP, Ethernet, etc .)
PlantScape PlantScape PlantScape
Process Station Honeywell - S9000, SCADA
High Ala rm
Low Alarm
Comm . Err.
Server LCS620, TDC3000, Server
Server FSC, UDC, 7800, DPR
Control Builder Allen-Bradley
Knowledge Builder OPC Client & Server
Documentation Modicon(Modbus+)
GE Fanuc
FieldbusConfiguration Fieldbus
and many more!

C200 Hybrid ControlNet (redundant m edia)


Process A-B
A-B PLC5/C
Controllers Logix 5550

Control Solver
50msec and 5msec

Fieldbus
Linking Devices
H1
Analog
ControlNet

Digital
RTD & H1
ControlNet

Thermocouple
Chassis I/O - Serial H1
ControlNet

Series A Pulse
H1
H1

H1

Rail I/O - Series A


Fiber
FiberOptic
Optic
Isolation
Isolation

GI/IS Rail I/O -Series H FOUNDATIONFieldbusDevices


Hazardous Area

Figure 1. PlantScape System Architecture

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

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 6 Release 320

System Overview

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

Figure 2. PlantScape Features Object-Based Graphics with Powerful Features Like Display
Scripting and Active-X Support
PlantScape system features include:
• Integrated Database -- Control Builder configuration includes information for both the Controller and
PlantScape Server. Information is entered once, not repeated in several databases.
• Integrated Alarms and Events -- Alarms are configured by Control Builder, generated by the Controller
Processor, recorded into the event system, and acknowledged by operators on the PlantScape Operator
Station alarm summary display. Users do not have to separately configure process alarms in both the
controller and the supervisory system.
• Point Detail Displays – Standard Detail displays for points are an example of the 300 standard displays that
are included with the system. Users can operate from these displays or, if they choose, create custom
displays. PlantScape provides maximum usability and flexibility at the same time!
• Integrated On-line Documentation -- The PlantScape system gives users quick access to system
information and support using the latest Internet technologies. It features SafeBrowse, Internet-aware
HTML (hypertext markup language) documentation, on-line help and on-line technical support. Users won’t
need to search through multiple sets of documentation. SiteDocs allows users to add links to site specific
electronic documentation within Knowledge Builder.
• Integrated Network Support:
• ControlNet: a realtime open Deterministic process control Network , features deterministic data
delivery 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 server
with standard available technology.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 7
• Real-time Database – The server features a true Client/Server architecture where a real-time database on
the 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 be
integrated 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, such
as valves, transmitters and sensors.

Figure 3. Control Builder Supports a Powerful Set of Algorithm Libraries for Implementing
Process Control Strategies
• Distributed Server Architecture -- With PlantScape's Distributed Server Architecture, multiple PlantScape
systems can operate as one – within a single plant, or across the world - without any duplication of
engineering effort. Distributed Server Architecture has been designed to handle the most stringent remote
requirements over slower wide-area networks, and as a result, deliver extremely high performance over local
higher speed plant networks.
• Advanced System Infrastructure – PlantScape includes a complete infrastructure that includes, an
complete alarm/event management subsystem, easy to configure reports, extensive history collection and a
variety of standard system trends.

The PlantScape Process system provides a uniquely integrated system solution consisting of the
PlantScape Server, PlantScape Station and Hybrid Controller on ControlNet or Ethernet. Rather
than just another controller, the Hybrid Controller is the focal control engine of this highly integrated
system. Server, Station and Hybrid Controller components were designed to perform as a single
highly optimized system, providing functions and efficiencies which are not generally available in
loosely 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

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 8 Release 320
latter system functionality can also be purchased alone as PlantScape SCADA, where the application
does 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 from
single-user HMI for a few points up to full scale SCADA systems consisting of tens of thousands of
points and up to 40 connected Stations. The key elements of PlantScape SCADA are the PlantScape
Server and PlantScape Station. PlantScape Station can run in either Windows NT or Windows
95/98.

The PlantScape System includes a very powerful supervisory control and networking system, with
features 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

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 9

Product Description
Control Processor Modules

The Hybrid Controller with C200 Control


Processor option, shown in Figure 4, consists
of a Chassis (Rack), Power Supply, Control
1 2
Processor, ControlNet Interface, Redundancy
Module, Ethernet Module and I/O Modules. An 4 3
optional Battery Extension Module (not shown)
is also available. The Chassis is available in 5
sizes - 4, 7, 10, 13, and 17 slots. All modules
can be removed and inserted under power. All
components are available with conformal
coating for maximum environmental protection.

The Power Supply ❶ is separate from the 2 5


1
Rack and does not consume any slots. It is
mounted on the left end of the Rack. Both 3 3
120/240 VAC and 24 VDC supplies are
available. Figure 4. Hybrid Controller & Chassis I/O Format
The C200 Control Processor Module ❷ is a
double wide, two-board assembly featuring a 100 MHz PowerPC 603E processor and eight (8) Mbytes
of RAM with error detection and correction. It supports both non-redundant and redundant controller
configurations. Four (4) Mbytes of parity-protected Flash ROM is used for permanent program storage
and allows easy upgrades. A built-in lithium battery backs up the controller database, and an optional
one-slot wide Battery Extension Module provides a rechargeable option instead of replacing the lithium
battery.

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 Control
Networks. 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 which
the specification is owned and managed by ControlNet International, of which Honeywell is a founding
member. Data throughput is 5 Mbits/sec. via single or redundant media options and features
deterministic 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 on
number of taps and drops), and the maximum fiber network segment length is 3 km (dependent on
fiber grade). Each Supervisory/Peer Network segment supports up to 10 non-redundant or 10
redundant 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 Control
Network and provides a peer to peer network for interoperability. External devices can communicate
with the Hybrid Controller through the Ethernet network. This is an open network built with off-the-shelf
PC hardware and is a familiar and efficient mode of communication. It can easily overcome distances
between locations and currently requires a switched network topology for 10MB TCP/IP support. The
module provides a 10BastT Ethernet Cable connector and supports one segment as a supervisory
network (with no routers). Ethernet Modules are not used with Redundancy Modules.

For Control Processor redundancy, the Redundancy Module ❺ provides redundancy between two
controller 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 without
disrupting control of the user’s process. The following are some of the important features of the RM:

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 10 Release 320
• Transparency of Synchronization -- Control chassis synchronization does not cause any user perceived
control interruption. The redundant control system automatically synchronizes a secondary solely by
powering up a properly cabled and populated secondary control chassis.
• Transparency of Switchover -- The occurrence of switchover of the control chassis is unnoticeable to the
operator, 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) halts
normal operations to prevent memory corruption.
• Fault Isolation -- A single fault does not propagate from a control chassis to its partner to cause the control
system to cease to control properly.
• One Module Design -- C200 modules can be used either with or without the RM for both non-redundant and
redundant applications.
• Partner Failure Diagnosis -- The cause of a failure in one controller chassis can be diagnosed from the
RM 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 with
the PlantScape Hybrid Controller via ControlNet. This allows each Controller to access data and
control 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.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 11

Input/Output Modules
Honeywell offers three families of
I/O:
• CIOM-A: Chassis mounted CIOM-A (Chassis I/O Series-A)
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/Zone RIOM-A (Rail I/O Series-A)
1 Hazardous locations

Chassis – Series A I/O


modules are a rack-mounted
(chassis) family of I/O available in
a wide variety of densities. RIOM-H (Rail I/O Series-H)
Modules have a small form factor
(5” x 5”) and feature deterministic
I/O update rates, diagnostics Hazardous Area
features, local (front of module)
or remote terminations, and
software 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/O
Modules in any combination of AI, AO, DI, or DO types. The Modules are compact and can be
mounted horizontally or vertically. An optional bus extender cable allows for even greater mounting
flexibility. The RIOM-A line consists of ControlNet adapters, power supplies, terminal base units and
I/O modules, all designed to lower installation, wiring, and maintenance costs. Additional information is
available 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 of
I/O that can be mounted and operated in areas with potentially explosive (Ex) atmospheres. All Series
H components are certified and can easily be distributed throughout a given hazardous location. Refer
to PS03-531, Rail I/O Modules Series H Specification and Technical Data, for hazardous location
classification and I/O details. Corrosion protection to test level G3, according to ISA-S71.04-1985, is a
standard 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 in
harsh 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 - H
I/O modules and designated CIOM-A modules are conformally coated with a protective layer designed
to safeguard the electronic components against corrosion in harsh environments. Other system
components, such as racks, power supplies, controllers, etc., are available with or without optional
coating.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 12 Release 320
When the coated option is selected, all control and I/O components are capable of withstanding a G3
or Harsh environment. This Harsh environment is defined by ANSI/ISA-S71.04-1985, “Environmental
Conditions for Process Measurement and Control Systems: Airborne Contaminates,” as shown in
Table 1. The coating option will thus dramatically improve the system reliability in those situations
where a well-controlled environment is not possible.

Table 1. Definitions from ANSI/ISA-S71.04-1985 -- "Environmental Conditions for Process


Measurement and Control Systems: Airborne Contaminants"
Severity Level G1 G2 G3 GX
Mild Moderate Harsh Severe
Copper Reactivity Level (angstroms) < 300 < 1,000 < 2,000 ≥ 2,000

Contaminant Gas Concentration (parts/billion)

Group A H2S <3 < 10 < 50 ≥ 50


SO2, SO3 < 10 < 100 < 300 ≥ 300
Cl2 <1 <2 < 10 ≥ 10
NOX < 50 < 125 < 1,250 ≥ 1,250
Group B HF <1 <2 < 10 ≥ 10
NH3 < 500 < 10,000 < 25,000 ≥ 25,000
O3 <2 < 25 < 100 ≥ 100
Gas concentrations are for reference purpose only and are believed to approximate the reactivity levels
assuming relative humidity is less that 50%. For each 10% increase in relative humidity above 50%, or
change in relative humidity by greater then 6%/hr, the severity level can be expected to increase by one
level.

Conformal coating is recommended for any installations for which the ambient environment meets
either 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 added
level 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 in
a sealed enclosure. Purging adds an even greater degree of protection.

In the above specification, Copper Reactivity Level refers to the amount (thickness) of corrosion which
accumulates on a copper test coupon over a period of one month. Gas concentrations listed are for
reference purpose only and are believed to approximate the listed Severity Levels assuming a relative
humidity of less than 50%. The Severity Level of an area can only be measured by a copper coupon
test (or by a suitable corrosion monitor); it cannot be determined by measuring concentrations of
gasses and humidity. Note that an increase in relative humidity above 50% as well as a relative
humidity 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 PlantScape
C200 Controller system design, documentation, and monitoring. It provides a comprehensive set of
tools for handling I/O, continuous, logic, motor, sequential, batch and advanced control functions
through a library of Function Blocks (FBs). FBs are basic objects provided by Honeywell to execute
different control functions. Each block supports parameters that provide an external view of what the
block 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 of
sequential FBs, Sequential Control Modules (SCMs). SCMs greatly simplify batch logic
implementation by sequencing a group of process equipment through a series of distinct steps to
accomplish 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

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 13
illustrates a simple Control Module -- in this case a PID loop -- made up of basic FBs. Note that in this
example four FBs are “contained” within the CM named FIC105. Each Control Module may be
scheduled at its own execution rate from 5 msec to 2 sec, and the user can schedule Function Blocks
and Control Modules to execute in any desired order.

Control Builder enhances engineering productivity by enabling “top-down” implementation, enabling the
creation of reusable control strategies. Control Builder uses icons to represent control blocks which
can be “wired” together using simple point and click techniques. Control drawings can be used on-line
to monitor control execution and make changes to control parameters, thereby significantly simplifying
control strategy checkout. Control Builder also allows templates to be created, modified and reused so
that 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 the
Specifications 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 function
libraries are available as well. The
built-in capabilities of the Control
Solver execution environment enable
users to take advantage of these library
options.

Due to its rich set of standard features,


SCMs greatly simplify Batch logic
implementation. In addition, the SCM
implementation follows the S88.01
standard. Standard features include
abnormal handling, providing an
alternative sequence execution for user
specified abnormal conditions.
Abnormal handlers support restart
capabilities, re-starting the sequence
from the position it was left or any other
Step the process requires to continue.
Standard Abnormal handlers include:
Checking, Interrupt, Restart, Hold, Stop
and Abort. Each Sequence supports up
Figure 6. Simple Control Module Example
to 50 recipe parameters, each with a
range, material code and scale option
and 50 history parameters for actual dosed material or reached temperatures. The mode track option
allows for different operating philosophies. Devices, such as motors, pumps, and controllers, will
follow SCM mode changes allowing either operator or sequence device control. The devices can also
be pre-configured with the action required after an SCM start, abnormal situation or restart. This
reduces the SCM step configuration.

For example, a Common SCM can be implemented for a header dosing application. This is a special
SCM that can be operated on different equipment units depending upon the selected unit instance. It
saves implementation, test and maintenance time required to support the application. SCMs are fully
integrated 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/IP
and UDP/IP communication. For maximum security, access is password protected. Several users
can create, configure and load control strategies at the same time from different workstations. Multiple
users can have the same chart open, with full write access to the first user who opens a chart.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 14 Release 320
When multiple users open a chart for monitoring, all users can change controller values based on their
security level.

The Control Solver Control Execution Environment (CEE) is the execution and scheduling
environment 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 control
functions. It features:
• Individual per-module selectable execution rates of 50, 100, 200, 500, 1000 and 2000 msec for the 50
msec CEE and 5, 10, 20, 50, 100 and 200 ms for the 5 msec CEE. All Control Modules and Sequential
Control 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 the
ability to “load balance” a Control Processor.
• Peer-to-peer communication between C200 Control Processors. Implementation is transparent so that
peer-to-peer connections are configured in the same way as intra-controller connections.

The Fieldbus Configuration Tools integrate the Hybrid Controller with Fieldbus devices. Key
features 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 of
control at different execution speeds. To determine how much control can be performed by a
Processor, Processor Usage and Memory Usage are considered. The number of modules or
blocks 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 Capacity
Specifications are given in the Models and Specifications section. These specifications should be
reviewed to ensure that PlantScape will meet the application requirements. Table 2 represents an
example non-redundant C200 configuration (not necessarily typical). Refer to Table 7.14 for a
description of the Function Block content of each module type.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 15

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


Configuration
Module Type No. of Period, Module Module Total PUs* Total
Modules sec PU MU MUs
I/O Module (64 max) 40 0.05 0.3 0.6 240 24
Analog Data Acquisition CM 20 1 2.9 7.4 58 148
Small Analog Data Acq. CM 10 2 0.47 1.0 2.35 10
Regulatory Control CM 100 0.5 2.8 3.9 560 390
Auxiliary Function CM 10 0.5 4.2 13.1 84 131
Digital Data Acquisition CM 20 0.1 1.2 3.1 240 62
Small Digital Data Acq. CM 10 0.1 0.22 0.6 22 6
Device Control CM 140 0.1 1.3 3.1 1820 434
Logic Control CM 10 0.1 1.0 3.5 100 35
Sequential Control Module (SCM) 50 1 2.0 55 100 2750
Total 3226 3990
Max 3600/1600** 4000
PU = Processing Unit per Control Cycle; MU = Memory Unit, Kbytes
PUs 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 Communication
CEE to CEE peer-to-peer allows data to be shared among separate Control Processors irrespective
of controller location within a Server domain (i.e., within a Supervisory/Peer ControlNet). If a
connection can legitimately be formed between two function blocks within the same controller, then
that same connection is permitted between two of the same type of function blocks, which are in
separate controllers. All data connections are done via data “pulls.” The only data “push” allowed in
PlantScape is the output expression of a Sequential Control Module Step function block. PlantScape
provides end point fail safe data protection and handling. Connections are protected against
failures 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 Processor
and PLC’s or other devices. The Exchange FBs support both the PCCC (Programmable Controller
Communications Commands) and CIP (Control and Information Protocol). The data is stored in the
exchange FBs and can be used in any control strategy. The Exchange FBs can also be used to
exchange data between two Control processors, which are not within the same name space of a single
PlantScape system, because these protocols support direct ControlNet addressing.

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

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 16 Release 320

PlantScape System Overview

PlantScape is a modular, supervisory control and networking


system designed around a high performance, Microsoft Windows
NT-based operating system. All components of this system are
fully integrated. For example, when a user-built Control Module is
loaded, appropriate data is automatically loaded to both the C200
Control Processor and the PlantScape Server database. A Server
database point is built for each named block. Features like
navigation tools and integrated alarming give the system a
consistent look and feel from the controller to the Operator Station.
Consistent tag names are used in the Hybrid Controller and in the
PlantScape Server. A dynamically scheduled cache in the
Server gathers all data requests into request lists, providing optimal
data access performance and memory utilization while minimizing
the data access load on the Hybrid Control Processor. Figure 7.
PlantScape Process Server
The PlantScape System incorporates leading edge, open-system
technologies, such as Microsoft Windows NT, Ethernet, TCP/IP
and standard Intel-based PC hardware to provide comprehensive facilities in an economical and easy
to use package. By optimally combining a comprehensive set of supervisory functions with the control
capabilities of the Hybrid Controller, the PlantScape architecture enables simplified operation and
engineering in a fully integrated system environment.

Figure 8. Hybrid Controller Points Built Using Control Builder


Become Immediately Accessible to the Operator via Standard Displays

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 17
The PlantScape architecture ensures that the user has complete and transparent access to
Hybrid Controller database. PlantScape also integrates with a wide range of other Honeywell and
third-party devices, thereby leveraging existing control investments and enabling complete integration
of process information. Process information is accessible by operators, process engineers and
MIS 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 at
providing 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 common
elements are required for most systems. PlantScape simply includes such elements in its standard
operating 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 hardware
configuration is complete, with no further system building required. Once PlantScape is populated with
the 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 or
extend standard functionality where required. All standard displays, for example, are modifiable by the
user. This means the user is up and running in minimum time!

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 18 Release 320

PlantScape Server Key Features

Standard facilities include:

• Windows NT-based server and Windows NT or Windows 95/98 based human machine
interface
• 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, object
based graphics provide
a powerful interface for
the user. The use of
industry standards,
such as Microsoft
Windows NT, Windows
95/98, and the Internet,
minimizes operator
training by providing a
familiar operating
environment.

Extensive use of user


configurable pull-down
menus and toolbars
allow easy, intuitive
navigation and fast
access to key process
data. The usability of
the operator interface is
further enhanced with
features such as last
command recall, copy
and paste, live video
integration, ActiveX
documents, scripting,
launching applications
and support for Figure 9. PlantScape Main Menu
standard peripherals
such as:
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 19
• sound cards,
• touch screens,
• dual screens video cards, and
• trackballs.

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

Standard system displays make it easy for operators to learn and use the system. An extensive
range 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 not
only allows the operator to view live video from remote locations but also provides the ability to switch
cameras, and pan, tilt or zoom the camera to focus in on a particular area. An alternative to live video
is WebCam. WebCam allows a CCTV camera to be connected to the Ethernet, and is therefore
available to all operator stations via SafeBrowse.

SafeBrowse allows the user to securely browse either the Intranet or Internet. This allows the system
to view corporate documents, such as Standard Operating Procedures from across the world, or to
keep 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 a
preconfigured number of connections to a PlantScape system. This allows a large number of users on
a 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 referenced
relative to a single tag name or ‘composite point’.

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

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 20 Release 320

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 eight
possible 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 will
provide 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 a
group of logically associated points into a single point structure. The parameters of a container point
are 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

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 21

User Defined Structure


In order to support other types of data such as user entered or calculated data from application
programs, 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 the
use of standard algorithms that may be attached to an analog, status or accumulator point. Functions
provided by these algorithms include:
• arithmetic calculations
• boolean calculation
• maximum/minimum value
• integration
• run hours totalization
• group alarm inhibit
• report request
• application program
request

Alarm/Event
Management
The PlantScape System
provides comprehensive Filters
alarm and event detection, Most recent,
management, and highest priority,
reporting facilities. One of unacknowledged
alarm
the keys to operator Annunciator
effectiveness is presentation
of alarm information. Many
tools are provided to quickly
target the process problems,
including:

• Multiple alarm priorities


• Dedicated alarm zone Figure 10. Standard Alarm Summary Display
• 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 by
supporting filters. Alarms may be filtered by:
• Area
• Acknowledge Status

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 22 Release 320
• Priority

Alarms on the Alarm Summary display can be acknowledged either individually or per page. On
custom graphics, alarms can similarly be acknowledged on an individual or per page basis. The
standard point alarm behavior is the alarm will flash red if unacknowledged and in alarm and be steady
red 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. In
addition to the configurable alarms PlantScape supports, a range of other point alarms including
Control 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 option
enables up to one million events to
be stored online, in addition the
events can be archived to removable
media for access at a later date.

Historization
History collection is available over
a wide range of frequencies in both
average and snapshot/production
formats. A large amount of history
can be retained on line, with
automatic archiving allowing
retention of and access to unlimited
quantities of historical data.
The default history collection
intervals are:
• 5 second snapshot
• 1 minute snapshot
• 1 hour snapshot
• 8 hour snapshot Figure 11. Standard Multiplot Trend Display
• 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

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 23

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

Trending
Flexible Trend Configuration allows trends to be configured on line as necessary by simply entering
the point and selecting the parameter from the database. Any of the history collection intervals may be
used 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 temporarily
disabled for clearer viewing without requiring reconfiguration of the trace. Trends may be easily
configured on line through standard trend displays, without the need to build displays. Real-time and
historical data are presented together on the same trend. Archived history may be accessed
automatically by simply scrolling to, or directly entering, the appropriate time and date.

Reporting
The supervisory system provides many built-in reporting functions. Standard report descriptions
include:
• Alarm/Event Log reports all alarms and events in a specified time period. By using filters, this report
provides an operator and/or point trace facility.
• Alarm Duration Log reports the time of occurrence and elapsed time before return-to-normal for specific
alarms in a specified time period.
• Integrated Excel Report provides the ability to launch a report built using Microsoft Excel in a similar way
to all other standard reports. Microsoft Excel can access the PlantScape database using the Open Data
Access option.
• Optional Downtime Analysis provides reports of downtime events sorted by category and/or reason
codes.
• Free Format Report Writer generates reports in flexible formats, which may include math and statistical
functions such as Max/Min and standard deviation.
• Point Attribute Log reports on points displaying specific attributes, such as off-scan, bad data, and alarm
inhibit.
• Point Cross-Reference determines database references for specified points to enable easier system
maintenance 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 configured
on line. Report output may be directed to screen, printer, file, or directly to another computer for
analysis or viewing electronically.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 24 Release 320

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

Level 1: Signed-off mode


Level 2: View only mode with alarm acknowledge
Level 3: Level 2 plus control of field parameters
Level 4: Level 3 plus field parameters of level 4, configure standard system infrastructure such
as reports
Level 5: Level 4 plus user configured field parameters
Level 6: Unlimited access
Operator sign-on/sign-off security provides up to 255 control levels to limit operator control of individual
items of plant and equipment. Any actions initiated by an operator are logged in the Event database by
an operator identifier. In addition any control actions to a given point is only allowed if the control level
configured in the operator profile exceeds the level assigned to the point.
An operator password consists of 5-6 alphanumeric characters and is encrypted. Operators may
change their own passwords, however a new password can’t be the same as the last 10 passwords
used in the previous 3 months. When signing on, three unsuccessful attempts will lock the operator out
for a lock-out period. Once signed on (logged on), an operator can sign off (log off) at any time or will
be 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, control
levels 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 of
controllers 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 automatically
calculating 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 the
scanning 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 those
operating remotely via dial-up modem links.
Diagnostics -- Once a controller or RTU is configured and placed in service, PlantScape automatically
performs diagnostic scanning of the device. Additionally, PlantScape performs checks on data integrity
of all data acquired from the controller. Should an invalid or timed-out response be received, the data is
ignored and the transaction is recorded as an error. Statistics are kept and displayed by the system on
communication errors by means of a communications barometer. The barometer increments for every
failed call and decrements for each successful call. In addition, the system alarms separate marginal
and 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 the
reporting sub-system or custom displays. If a controller fails, all point parameter values that are
sourced from it are indicated as bad to the operator.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 25

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 Flame Serial
Safeguard
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 Bradley Serial/Ethernet/DH+/ControlNet
ControlLogix
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 Honeywell Serial
MA500
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 be
mapped into SCADA point parameters in the PlantScape Server. This information is then able to be
displayed, alarmed, historized and controlled. The OPC Client is based on V1.0a of the OPC
specification. For more information on the wide range of OPC Servers available see
www.opcfoundation.org.

Allen-Bradley Integration Interface - PlantScape is tightly integrated to the PLC5/SLC range of


controllers. For example, PlantScape provides standard diagnostic displays that are automatically
generated by the system. In addition any alarms, such as rack faults, major or minor faults, are
automatically 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 Smart
Transmitter files by simply building a single point.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 26 Release 320

Server Redundancy Screen Updates

The PlantScape server can Database


be optionally redundant. Primary Checkpoints
Backup Client
The PlantScape Server Server Station
Redundancy subsystem
provides a high availability
platform by enabling a pair
of similarly configured
PlantScape servers to Data
support each other in a Acquisition
primary/backup fashion.
Should the Primary fail, a
fully functioning Backup
assumes the Primary role.
Primary refers to the specific Figure 12. Redundant PlantScape SCADA Example
PlantScape server which is
actively acquiring data from the controllers/RTUs and serving data to the clients. The Primary
propagates all database transactions to the Backup over a redundant network so that both databases
remain in complete synchronization.

Distributed Server Architecture


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

Figure 13 shows an example of a distributed system connected using a wide area network. The master
control center accesses data from the servers at each remote site. It may or may not have its own
locally connected controllers. The servers at the remote sites may also ex-change information with
Master Control Center
each other logically
creating a global database
including:
• Global real time data
Process/SCADA access
Server • Trending of real time
and historical system
wide data, on a single
Wide Area Network trend
• Global alarming
Site A Site B Site C
• Global system
messages

Further details on
Process/SCADA Process/SCADA Process/SCADA Distributed Server
Server Server
Server Architecture are available
in the PlantScape
Distributed Server
Architecture – Elevating
Distributed Control to the
Figure 13. PlantScape Distributed Server Architecture Highest Plateau document
SL-53-655.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 27

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

Recipe Management -- PlantScape Recipe Management provides facilities to create recipes and
download them to nominated process units. Each recipe may have up to thirty items, with recipes
chained 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 individually
enabled for scaling.

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

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

SPQC -- The SPQC(Statistical Process & Quality Control) option provides powerful statistical
processing capabilities for real-time data collected by the system. Facilities include on-line generation
of 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 the
system are required to be archived for later review. Storage capacity is dependent upon media
capacity, but storage of over 1 million events is easily achievable. Approximately 60 Mb of hard disk
space is required for every 100,000 events archived.

Alarm Pager -- Point alarms may optionally be sent to an alarm paging or messaging system. Up to
100 pagers can be configured, and each pager has a schedule of operation so that users are only
paged when they are on call. The information they receive is what normally appears on the alarm
summary. For each phone number configured, the user may specify the days of the week and times of
the 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 PlantScape
Server database and an ODBC-compliant local or network third-party database. It uses standard
Structured Query Language (SQL) commands. The PlantScape Server acts as a client application in
this 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, and
Sybase 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.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 28 Release 320
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 ODBC
client applications, such as Microsoft Access. The Server database is exposed as a number of
read-only ODBC tables including Points, Event History and Process History. Driver features
include:
• 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 application
to read/write PlantScape point parameters. The OPC server is based on Honeywell's HCI server
toolkit, which in turn is based on OPC specification V1.0a. It supports all mandatory OPC
interfaces.

Network Server – The Network Server provides extremely efficient, access to the PlantScape
database for network based applications such as Microsoft Excel Data Exchange, Network Node
Interface 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 one
or 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 point
data to another PlantScape server.
• Applications executing on other network connected platforms may easily access PlantScape
real-time data over the network using the Network API. The API provides high level
subroutine calls in Visual C/C++ or Visual Basic to allow read/write access to PlantScape data
in a networked environment.

Application Toolkit
Two types of application programming interface (API) are available. The first is for applications written
on the PlantScape server and the second is for applications that are required to run on network based
clients (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 the
following 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

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 29

Engineering Tools
Quick Builder -- Quick
Builder, allows users to
configure points,
controllers/RTUs, stations
and printers. Quick Builder
leverages a relational
database engine (Microsoft
Jet Engine) to provide
greater productivity through
capabilities such as filtering
user views of the database,
multipoint edit facilities and
the intuitive Windows style
interface. Other features that
the relational database
provide are the user-defined
fields that can be used for
termination schedules, wire
numbers, etc., and a
standard set of reports.
Additions and modifications
to the PlantScape database Figure 14. QuickBuilder Example
can be made while the
system is on-line.

Display Builder -- Display Builder is an object-based, fully integrated custom display builder for
development of application specific graphics. Animation of displays is completed quickly and easily with
simple point and click type
configuration. A library of
commonly used plant
equipment such as vessels,
piping, valves, tanks, motors,
etc., is supplied with Display
Builder to further speed
graphic development. In
addition, Template Displays
may be used to reduce
configuration time where
similar displays need to be
repeated throughout the
system. Process objects and
color palettes allow quick and
easy creation of custom
objects with or without 3D
effects. Graphic displays can
also be significantly enhanced
through the use of Visual
Basic Scripting and ActiveX
components. Effects such as
high-speed animation, tool
tips, and control of a station Figure 15. Display Builder Example
from an application are
possible with VB Scripting. Additionally, a wide array of ActiveX component types, such as playing
sound and video can be invoked.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 30 Release 320

User Documentation
PlantScape documentation
is available in three basic
forms to the user:
• Printed
documentation (see
below)
• On-line Help (F1
function key from
within several
applications)
• Knowledge Builder
Electronic On-line
Documentation using
HTML Frame
Browser (see below)
The following is a listing of
components in the
electronic PlantScape
Figure 16. Knowledge Builder embedded in an Knowledge Builder
Operator Station window Document 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 the
PlantScape Display Building Guide.
Start-up and Shutdown Guide Procedures for normal start-up, shutdown, and restarts, including
controller, networks and SCADA.
Troubleshooting and Maintenance Procedures for troubleshooting and maintenance, with diagnostic
Guide information.
Rail I/O Implementation Guide Provides information about the RIOM-H (GI/IS) components as a
supplement to existing procedures.
Fieldbus Implementation Guide Procedures for interfacing FOUNDATION Fieldbus devices with
PlantScape’s Hybrid Controller.
Server and Client Installation Guide Procedures for installing Server and Clients.
Server and Client Configuration Procedures for configuring Server devices, points, reports etc.
Guide
Operators Guide Procedures for operating Station, including monitoring and
controlling, managing alarms, and generating and viewing reports.
Administration Guide Procedures for system administration, including topics such as
security and system back-ups. Incorporates SCADA and Process
System administration information.
Statistical Process & Quality Control Procedures for implementation of SPQC

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 31

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, which
define how system items, such as Stations and points, are set up.

PlantScape Reference
Control Builder Component Reference General information on control module components (how they
work).
Control Builder Parameter Reference Detailed information on Control processor module and function
block 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 and
points.
Controllers Reference Comprehensive reference guide to all SCADA drivers.

PlantScape Theory
Communications Theory Covers all aspects of PlantScape communications, including
Controller peer-to-peer.
Control Builder Components Theory General information on control module components (how they
work).
Notifications Theory General notifications theory information (how it works).

PlantScape General Information


Supporting Information
Frequently Asked Questions Answers to frequently asked questions about the PlantScape
System.
Global Notices and Trademarks Copyright and license information.
Honeywell Contacts Lists identifying important contacts within Honeywell.
References Identifies non-PlantScape Honeywell documents that may be
sources of reference for the material discussed in Knowledge
Builder.
Other Resources
WWW Resource Links Provides links to important web sources of information.
Getting Started A complete guide to getting the PlantScape system up and
running.
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 electronic
documentation within Knowledge Builder. A trial version of Site
Docs 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 outlines
and more!

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 32 Release 320
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 – Control Functions
– Peer-to-Peer Functions – Notifications Theory
– Controller Redundancy – 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 SCADA
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 System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 33

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 " PV Calculator
" Totalizer " Dead Time
" General Linearization " Lead / Lag
• Regulatory Control Algorithms
" Proportional, Integral, Derivative (PID) " Regulatory Calculator
" PID with Feedforward " Ratio Bias
" Override Selector (4 inputs) " Ramp / Soak
" Remote Cascade " Positional Proportional
" Auto Manual " Pulse Length
" Switch (8 input single pole) " Pulse Count
" Fanout Block (1 input/up to 8 outputs)
• Device Control (Motor Control)
• Discrete Logic (per IEC 1131 standard)
" 2oo3 (2-out-of-3 Voting) " MIN (Minimum) " QOR (Qualified OR)
" AND " MINPULSE (Minimum Time " ROL (Rotate Left)
" CHECKBAD Limit Pulse) " ROR (Rotate Right)
" DELAY " MUX (8-Input Multiplexer) " RS (Reset-Dominant Flip-
" EQ (Compare Equal) " MUXREAL (8-Input Flop)
" FTRIG (Falling-Edged Multiplexer, Real Number) " RTRIG (Rising-Edged
Trigger) " MVOTE (Majority Vote) Trigger)
" GE (Compare Greater Than " NAND " SEL (Selector Function)
or Equal) " NE (Compare Not Equal) " SELREAL (Selector Function,
" GT (Compare Greater Than) " nOON (n-out-of-N Voting) Real Number)
" LE (Less Than or Equal) " NOR " SHL (Shift Left)
" LIMIT " NOT " SHR (Shift Right)
" LT (Compare Less Than) " OFFDELAY " SR (Set-Dominant Flip-Flop)
" MAX (Maximum) " ONDELAY " TRIG (Change Detect Trigger)
" MAXPULSE (Maximum Time " OR " WATCHDOG
Limit Pulse) " PULSE (Fixed Pulse Output) " 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) " Digital Input (DI)
" Analog Output (AO) " Digital Output (DO)
" Pulse Width Modulation (PWM) " Serial Interface Array (Numeric, Flag, Text)
" Rail I/O Series A (Input & Output) " Fieldbus Analog & Digital (Input & Output )

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 34 Release 320

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, 100 < 2 sec
Parameters Per Display, Single Station/Server (Station
configured for 1 sec. update)
Typical Display Call Up Time, 100 Parameters Per Display, < 2 sec
Single Station/Server (call up time dependent on display
complexity; excludes initial call up)
Maximum number of concurrent users connected to one 10 for Process Server (20
Server with 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 to
report 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 the
operation 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 and
one 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 for 128KB
each multi-user CB Client.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 35
Table 7 (cont’d). PlantScape System Performance & Capacity Specifications
Table 7.5.a. Distributed Server Architecture Performance Specifications
DSA Process Server, Publishing Communications Performance
Available Max Network Max Throughput / Maximum
Network Throughput (Param / Server (Param / Subscribing Servers
4 1 2, 3
Bandwidth Second) Second)
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


Available Max Network Max Throughput / Maximum
Network Throughput (Param / Server (Param / Subscribing Servers
4 1 2, 3
Bandwidth Second) Second)
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 Network Max Network Throughput Max Publishing Servers
4 1
Bandwidth (Param / Second)
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/sec
3. 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 network
traffic. Absolute maximum number of subscribing Stations/publishing Server is 20
4. “Available Network Bandwidth” means dedicated continuously available bandwidth for DSA use
between the Servers, and not shared bandwidth with other applications such as Station access
or Control Builder Multi-User access.
Maximum alarm/notification rate is 20/sec/server.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 36 Release 320
Table 7 (cont’d). PlantScape System Performance & Capacity Specifications

Table 7.6. Supervisory Process Control Network


Ethernet (R320) ControlNet
Supervisory Networks per non-redundant 1 non-redundant 1 redundant or non-
or redundant server network redundant network

Note: Mixed Supervisory ControlNet &


Ethernet on same Server is not
supported.
Allowable Combinations of Controllers * 10 or less Non- 10 (whether redundant or
per Server Redundant only non-redundant)

Network Topology Switched Conjoined

Data Rate 10 Mbits/sec 5 Mbit/sec


Media Redundancy Non-redundant only Single cable or redundant
media operation
supported.
*Controller Definitions including PLCs Non-Redundant: Redundant:
Note: Multiple Controllers per chassis is 1 C200 2 C200s in a Chassis Pair
NOT supported. 1 CL5550 with 2 RMs
1
1 PLC5/C or E
1 SLC (Ethernet only)
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, 5, 10, 20, 50, 100,
1000, 2000 ms 200 ms
Configurable Peer-to-Peer Update Rates (Period) 100, 200, 10, 20, 50, 100,
(Rate at which a CEE can subscribe to data from other CEEs 500, 1000 ms 200,
through peer-to-peer communications.) 500, 1000 ms

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 37
Table 7 (cont’d). PlantScape System Performance & Capacity Specifications
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 Server 4000 PPS 4000 PPS
from all Controllers combined.
(Includes Display updates, Fast/Slow History, Excel I/ODBC Exchange, and CB
Monitoring)
Overall Communications Performance per CEE/CPM
Maximum Total Parameter Access Response Rate 2000 PPS 2000 PPS
(Includes all Server Data Requests and peer communications)
CEE to CEE Peer-to-Peer Communications Performance per CEE/CPM
Maximum Initiator Node Pull/Get Request Rate (to all target nodes). 500 PPS 500 PPS
(Based on the number of requests for peer data and the peer update rate.)

ControlNet ControlNet
50 @ 100 ms 5 @ 10 ms
100 @ 200 ms 10 @ 20 ms
250 @ 500 ms 25 @ 50 ms
500 @ 1 sec 50 @ 100 ms
100 @ 200 ms
250 @ 500 ms
500 @ 1 sec
Ethernet Ethernet
250 @ 500 ms 250 @ 500 ms
500 @ 1 sec 500 @ 1 sec

Maximum Target Node Response Rate to Pull/Get Requests (from 500 PPS 500 PPS
all initiator nodes).
Maximum Initiator Node Push/Store Request Rate (to all target 50 PPS 50 PPS
1
nodes)
Maximum Target Node Response Rate to Push/Store Requests 50 PPS 50 PPS
(from all initator nodes).
CEE to PLC – Peer-to-Peer
Supported Protocols and commands
PCCC (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)

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 38 Release 320

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 blocks 8 8
per CEE/CPM.
DHRIO Module only counts as 1 Target Device even when communicating with
2
multiple PLCs on either DH+ network
Maximum Number of DHRIO Modules per CEE/CPM 2 2 (local chassis only)
Target communication performance 2 2
500PPS 500PPS
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 Block
2
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 Switchover 120 sec
and Completion of Initial Synchronization
Maximum Elapsed Time Between Switchover Due to 150 sec
Power Cycle of the Primary and Completion of Initial
Synchronization

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 39
Table 7 (cont’d). PlantScape System Performance & Capacity Specifications
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 2 2
(Each FTA connected counts as 4 IOMs in the 64 Max IOM calculation above and
the 24 IOMs/CNI calculation below.)
Maximum Number of Remote I/O Racks + Rail Adapters 8 0
(combined) per CEE/CPM. (local I/O
only)
Maximum Number of IOMs per ControlNet CNI -- Rack + Rail 24 0
Modules in any combination (except SIM & PIM as noted) (local I/O
(Each Pulse Input Module counts as 1.5 IOMs in the 24 IOM/CNI calculation, each only)
DHRIO Module counts as 1 IOM.)
Maximum number FF Linking Devices per CEE/CPM 8 0 (local I/O
only)
Note: Each Linking Device counts as 1 IOM in the 64 IOMs/CPM calculation
above.
Maximum number FF Linking Devices per Non-Redundant Server 8 0 (local I/O
only)
Maximum number FF Linking Devices per Redundant Server 16 0 (local I/O
(NI-FBUS Service and NI Configurator must be run on the Backup Server only)
only)
Maximum number FF Linking Devices per NI Configurator Project file (i.e., 1 0 (local I/O
use one project file per LD) only)
Maximum Number of H1 segments per FF LD 2 N/A
(Each segment is defined as a FOUNDATION 31.25 kbaud H1 network)
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-NTIF15
interface. NZ-NTIF15 is a valid option with any other PlantScape Process System. It is
also valid with any PlantScape SCADA system or any PlantScape VISTA system.

Table 7.11. Input Module Sampling Period Specifications


Sampling Period
Typical Input Modules 25 ms
(Includes CIOM-Series A and RIOM-H Modules, with exceptions noted below)
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) 50 ms
Can vary slightly depending upon the frequency setting and upon the number of points
Serial Interface Module (CIOM-Series A) 250 ms

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 40 Release 320

Table 7.12. CEE/CPM Processing Resources


PU = Processing Unit. The PU represents a platform-independent amount of processing resource (time) required to
complete 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 per 1000
CPM/CEE
Maximum number of component blocks per CM 40
Note: This maximum number is achievable under nominal operating and
monitoring conditions. The following items may lower the maximum number
of 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
Maximum number of Steps & Transitions (in all handlers) per 160 (80 Step/Transition
SCM pairs)
Maximum number of process history points per CEE/CPM 500

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 41
Table 7 (cont’d). PlantScape System Performance & Capacity Specifications
Table 7.14. Typical IOM/CM/SCM Processing and Memory Resource Requirements
Typical Module Types Memory
Processing Resource Consumption Resource
(FB Content in Parentheses)
Consumption
Total Processing Consumption (PU/sec) per module 50/5 ms CEE 50 ms CEE All CEE
type = Processing Resource Consumption (PU/module Non-Redundant Redundant
execution) / Execution Period (sec/module execution)
Configuration
(PU/Module (PU/Module s
* Number of Modules
Execution) Execution) (MU/Module)
Typical I/O Module 0.3 0.19 0.6
(Average consumption of available IOM’s)
Analog Data Acquisition CM 2.9 3.8 7.4
(10 AI, 10 DataAcq FB’s)
Small Analog Data Acquisition CM 0.47 0.43 1.0
(1 AI, 1 DataAcq FB’s)
Regulatory Control CM 2.8 2.8 3.9
(1 AI, 1 DataAcq, 1 PID, 1 AO, 6 Logic FB’s)
Auxiliary Function CM 4.2 5.1 13.1
(10 Aux. FB’s, such as AuxCalc, Totalizer)
Digital Data Acquisition CM 1.2 1.2 3.1
(10 DI, 10 Flag FB’s)
Small Digital Data Acquisition CM 0.22 0.14 0.6
(1 DI, 1 Flag FB’s)
Device Control CM 1.3 1.3 3.1
(2 DI, 2 DO, 1 DevCtl, 5 Logic FB’s)
Logic Control CM 1.0 1.0 3.5
(20 Logic FB’s)
Sequence Control Module (SCM) 2.0 3.0 55
(1 each of Main, Hold, Stop and Abort Handlers, 10
Steps with 8 Outputs each, 10 Transitions with 5
Conditions each, 10 Recipe items, 5 History items)
Sequence Control Module with an alias 2.0 3.0 150
table of size 45 rows by 100 columns
(1 each of Main, Hold, Stop and Abort Handlers, 10
Steps with 8 Outputs each, 10 Transitions with 5
Conditions each interspersed in all the handlers, 10
Recipe items, 5 History items)

Sequence Control Module with an alias table 2.0 3.0 146


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

The following Block Libraries consume the following ! Exchange (PLC5 & Logix5550) – 70 MUs
extra memory when the first block is loaded to the ! Pulse Input IOM – 100 Mus
C200 Controller: ! GI/IS Series R IOMs – 125 MUs

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 42 Release 320

Table 8. PlantScape Server Hardware Descriptions


Table 8.1. MZ-NTPC02 – PlantScape Performance Server PC With Windows NT
Workstation
Description:
PC suitable for providing PlantScape Server Platform for medium to large applications (e.g., over
5 stations, databases over 2000 points, advanced control or other applications, extra high-speed
data acquisition) or for users who want a platform with the longest life before obsolescence. For
customers purchasing their own PCs, see Appendix A for guidelines.
Includes: Special Notes:
• Current "best-performance" Pentium III processor • Monitor not included - ordered
suitable for PlantScape for WINDOWS NT server separately
support • COM1/COM2 may be used for
• 256 MB Memory minimum serial communications
• 8x SCSI CD-ROM Drive minimum • If more than 2 serial ports
• 9 GB Hard Disk minimum required, or RS-422/485, use
• Keyboard Multi-port Serial Communications
• Mouse board
• Mini-Cartridge Tape Drive • Required for any new PlantScape
• Microsoft Windows NT Workstation 4.0 with Service Process system
Pack 6a

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: Special Notes:
• Current "best-price" processor suitable for • Monitor not included - see
PlantScape Windows NT Station mini server and Hardware Options
client 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

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 43

Table 9. PlantScape Server Sizing Specifications


Database Item Default Size Maximum
Point Count 20 65,000
PlantScape SCADA points use a 50
composite point structure. A status point 100
contains a PV, OP and a Mode. An analog 300
point contains a PV, SP, OP, Mode and 4 650
auxilliary parameters. 1,000
Total number of PlantScape Process 2,000
points = 2 * Number of Processors + 5,000
Number of IOMs + Number of CMs + 10,000
Number of SCMs. 15,000
The total Server point count = total 20,000
PlantScape SCADA point count + total
PlantScape Process point count.
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

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 44 Release 320

Table 10. C200 Control Processor Specifications


TC-PRS021, TK-PRS021
Parameter Operative and Storage Limits Transportation Band
1
Ambient Temp Range 0 to +60°C no fans -40 to 85°C
Temp. Rate of Change ≤ 1°C/min. ≤ 5°C/min.
2
Relative Humidity 5 to 95% (non condensing) 5 to 95% (non cond.)
Uncoated (TC-PRS021) Mild (G1) G1
Coated (Tk-PRS021) Moderate (G2) or Harsh (G3) G2 or G3
Vibration (3 axes)
Frequency 10 to 60 Hz 10 to 60 Hz
Acceleration 0.5 g max. 1 g max.
Displacement 0.1 inches 0.1 inches
Mechanical Shock
Acceleration 5 g max. 20 g max.
Duration 30 ms max. 30 ms max.
Barometric Pressure
1
Altitude -300 to +3000 m Any
3
Corrosives G2 std, G3 option (ISA S71.04) G3
Module Power Requirements +5 VDC +/- 5% @ 1.5 A
+3.3 VDC +/- 5% @ 1.0 A
4
Module Battery Backup Time
Lithium Battery (standard, built in) 144 hours (non-rechargeable, Lithium battery is
replaceable) - 6 days disconnected during
Battery Extension Module (BEM) 120 hours (rechargeable) - 5 days shipment.
Removal/Insertion under power NOT PERMITTED when equipment is
(RIUP) installed in a Class I, Division 2,
Hazardous (Classified) Location.
PERMITTED when equipment is
installed in ordinary, non-hazardous,
locations (I/O modules reload
automatically)
CE Conformity (Europe) 89/336/EEC, EMC Directive N/A
EN 50081-2, Emissions, Industrial
EN 50082-2, Immunity, Industrial
Certifications
UL (Unclassified Locations) UL 508, Industrial Control Equipment

CSA & FM Class I, Div. 2, Mounting (Maintenance may require a


Groups A, B, C, & D hot work permit)
(see Table 12 for agency symbols)
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 door
provides that warning.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 45

Compliance and Certification Specifications


Compliance to European Union Directives. This product has the CE mark and is approved for
installation within the European Union and EEA regions. It has been designed and tested to meet the
following directives:
• EMC Directive. This apparatus is tested to meet Council Directive 89/ 336/ EEC Electromagnetic
Compatibility (EMC) using a technical construction file and the following standards, in whole or in
part:
• 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 Low
Voltage, 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 Susceptibility
CSA C22.2 No. 142-M1983 Process Control Equipment
C22.2 No. 0-M1982 General Requirements Canadian Electrical Code, Part II
C22.2 No. 4-M1982 Bonding and Grounding of Electrical Equipment
FM ISA S12.12 Nonincendive Electrical Equipment for Use in Class I & II, Div. 2
and Class III, Div 1 & 2 Hazardous (Classified) Locations
UL 508 Industrial Control Equipment

Table 11. Chassis Specifications


TC-FXX041, TC-FXX071, TC-FXX102, TC-FXX132, TC-FXX171, TK-FXX101, TK-FXX131
Model Module Dimensions (with mounting tabs Approx. weight
slots & power supplies) W x H x D (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 mount
Environmental Conditions Agency Certification Same as Power Supply Specifications
Minimum 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 to
the customer, or it may be supplied separately (not installed in cabinets) such that the customer is
responsible for suitable mounting and interconnection/test. Note that in order to comply with applicable
regulations and codes, the controller and I/O racks may have to be located in a room, vault, or
enclosure that is accessible only to qualified persons. Please refer to NEC 110-17, part 1 (1996
National Electrical Code, Copyright 1995 NFPA) or to the appropriate local or national electrical
standards for more information.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 46 Release 320

Table 12. Power Supply Specifications


TC-FPCXX2, TC-FPDXX2, TK-FPCXX2, TK-FPDXX2
Model Uncoated: TC-FPCXX2 TC-FPDXX2
Coated: TK- FPCXX2 TK- FPDXX2
1
Input Voltage Range 85-132 VAC or 19.2-32 VDC
170-265 VAC (selectable)
4
Input Power 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 °C
2
Backplane Output Current, Maximum 1.5 A @ 1.2 V
4 A @ 3.3 V
10 A @ 5.1 V
2.8 A @ 24.0 V
3
Fuse Protection 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 Conditions
Operating Temperature 0 to 60 °C (32 to 140°F)
Storage Temperature -40 to 85°C (-40 to 185°F)
Relative Humidity 5 to 95% noncondensing
Uncoated (TC-FPCXX2, TC-FPDXX2) Mild (G1)
Coated (TK-FPCXX2, TK-FPDXX2) Moderate (G2) or Harsh (G3)
Agency Certification
(when product is marked)

marked for all applicable


directives

Class I, Div 2, Groups A, B,


C & D Hazardous locations

1
Input may drop to 16 V for a maximum of 2 minutes each hour for motor starting.
2
The combination of all output power (5 V backplane, 24 V backplane, 3.3 V backplane and 1.2 V backplane) cannot exceed
70 W.
3
This fuse is intended to guard against fire hazard due to short circuit conditions and may not protect the power supply from
damage under overload conditions.
4
Note 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 Blocks
I/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)

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 47

Table 14. ControlNet Specifications


9904-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, cable
connectors, terminators, segments, repeaters, and bridges.
Cable Type and Topology RG-6 Quad Shield cable, BNC connectors, trunk & drop, bus
topology. See next page for recommended cable types.
Cable Type by Application
• Light industrial applications • Standard PVC CM-CL2
• Heavy industrial applications • Lay-on Armored and Interlocking Armor
• High and low temperature applications, • Plenum FEP CMP-CL2P
as well as corrosive (harsh) areas
• Moisture Resistant (direct burial, • Flood burial
flooding, etc.)
Maximum Distance and Total Number • Maximum Coax plus Fiber length of 10 km
of Repeaters Between any two (2) • Maximum of 5 Repeaters (6 Segments)
Nodes
• Maximum Coax Segment Length • 1000 m (3280 ft.) - 16.3 m (53.4 ft.) x [Number of Taps - 2]
• Maximum Fiber Segment Length • See Repeater Specifications below
Maximum Total Length Differential • 800 m (2624 ft.) (total link)
Between A and B Trunk
Fiber Optic Repeater Specifications – TC-RPA001, TC-RPRS01, TC-RPFM01
Mounting DIN rail mountable (35 mm wide rail)
Maximum Number of Fiber Modules Four (2 ports/module)
per TC-RPA001 ControlNet Module
Adapter
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 dB
Cable wavelength specification 650 ηm (red) 1300 ηm
Fiber Type 200 µm glass (HCM) 62.5 µm
Fiber 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.
Local ControlNet Trunk Remote ControlNet Trunk

Tap Tap

TC- RPA001 TC- RPFM01 TC- RPA001 TC- RPFM01 TC- RPFM01
24 Vdc 24 Vdc
R1
R 1 T1
T1 R2
R 2 T2
T2 R1
R 1 T1
T1 R2
R 2 T2
T2 R1
R 1 T1
T1 R2
R 2 T2
T2

TC- RPA001 TC- RPFM01


24 Vdc R 1 T1
T1 R 2 T2
T2
R1 R2

Fiber Segments -- 3 Km max each

Figure 17. ControlNet Fiber Optic Example -- Use of 2 Fiber Segments to


Interconnect 2 Non-Redundant-Media ControlNet Trunk Segments

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 48 Release 320

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


Honeywell Supplier Field NEC / Jacket Jacket Dielectric Electrical Compatible Comments
Part and Part Usage CEC color material Type Properties Connector
Number Number Rating
(15)

(10)
51192416 Belden riser-rated CMR Black PVC Foam PE ControlNet 51192417- Standard Honeywell
(7)
3092A(4) network- 100 ControlNet raw trunk
tested by cable (sold as TC-
Honeywell KCC900).
(2) (10) (5) (8)
CommScope riser-rated CMR Black PVC Foam PE CommScope version of
5060R Belden 3092A cable
above.
(10) (5) (8)
CommScope general CMG Black PVC Foam PE
(3)
5060 purpose
(6) (9)
CommScope plenum- CMP Natural Kynar Foam
5061 rated FEP
(6) (9)
Belden plenum- CMP Gray fluoro- Foam Belden states this cable
3093A rated copolymer FEP is suitable for Outdoor
and Direct Burial
applications.
(5) (8)
CommScope direct-burial Black PE Foam PE Not armored
5060B
(5) (8)
Belden interlocked Black PVC Foam PE See note 13
123092A aluminum
armor
(5) (8)
Belden interlocked Black PVC Foam PE See note 13
133092A steel armor
(5) (8)
Belden corrugated Black PE Foam PE See note 14
543092A aluminum
armor
(5) (8)
Belden corrugated Black PE Foam PE See note 14
553092A steel armor
(10) (5) (8)
CommScope corrugated Black PVC Foam PE Armor layer plus outer
(11)(16)
5060A aluminum PVC jacket. Jacket also
armor available in PE.
(10) (5) (8)
CommScope continuous Black PVC Foam PE Jacket also available in
(11)
5060C cast armor PE.
(10) (6) (8)
Belden messenger Black PVC Foam PE Separate messenger
1191A wire.
(10) (5) (8)
CommScope messenger Black PVC Foam PE Separate messenger
(11)
5060M wire. Jacket also
available in PE.
(10) (6) (8)
Belden hi-flex CM Black PVC Foam PE More flexible center
YR-28890 conductor and shields.
(10) (6) (8)
CommScope hi-flex CMG Black PVC Foam PE More flexible center
(3)
5060F conductor and shields.

See Notes next page…

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 49

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 less
distance 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 same
as (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 smaller
than standard 51192416 cable
10. Cables with PE (polyethylene) jacket last longer outdoors than cables with PVC jacket. Protect PVC cables outdoors by
placing 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 electrical
characteristics for ControlNet networks
13. Belden states this armored cable can be used outdoors (without conduit protection) but not for direct burial. Basically it is
Belden 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 moisture
immunity 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 Canadian
applications
16. CommScope states that the armor is also available in interlocked aluminum or steel

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 50 Release 320

Topologies and Configuration Examples

PlantScape Hybrid Controller “Models at a Glance” Example


Based upon ControlNet

TC- PRS 021 -- C2 00


TC- CCR013 -- Control Processo r
ControlNetIn ter face
(CNI), Re dundan t TC- FXX 102 -- 10-slot r ack
Media (O ptio nal) TC-CCR01 3 - -
CNI to conne ct to other
I/O r acks

Main Controller
Rack
TC- FPCXX2 --
120 /24 0 V AC
Power Sup ply LAN Co nnectio n - -
Ethern et, TCPIP, e tc.

PlantScape Server
(sta tions not
shown)
Taps - - 9 904-TPS, R,
YS, and YR ( 4 kinds)

ControlNet Cable (TC-KCCxxx) - Supervisory

C
Terminators -- TC- PCIC01 - - ControlNet
o TC- TCXBNC Communicatio n Interface
n TC- CCR013 -- CNI, Module for PC ( redund ant
t Redund ant Media media) (in server)
r
o
l Additional or
N Remote I/O Rack
e
t

I/O mod ules an d


terminal blocks

Figure 18. Model Number Example


The above example is meant to illustrate typical component model numbers necessary for a small
system. It does not include software components and is not intended as the basis for placing a
PlantScape System order. A power supply always attaches to the left-end of a rack and does not use
any 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 as
peer-to-peer messages between controllers. The I/O ControlNet carries messages between controllers
and IOMs. A ControlNet Tap consists of two BNC connectors for trunk line cable connection, an
integral 1-meter drop cable, and a BNC connector for ControlNet Interface (CNI) connection. Several
physical models are available to accommodate different mounting layouts.
Other PlantScape operator stations connect to PlantScape via a LAN above the Server, not via the
Supervisory ControlNet.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 51

PlantScape Hybrid Controller “Models at a Glance” Example


Based on Ethernet

Ethernet (TCP/IP) Ethernet (TCP/IP)

Redundant
Second
PlantScape
Redundant
Server
PlantScape
Server

PlantScape Stations ControlNe t


TC-CEN011 - Ethe rne t Interf ace M odule Switch

TC-CEN011 - Ethe rne t


Interface Module
Ethernet

ControlNe t
PLC5/E

Ethernet

Figure 18. Ethernet Topology Example


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

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 supervisory
messages between the PlantScape Server and Controllers as well as peer-to-peer messages between
controllers. The I/O ControlNet still based on ControlNet, carries messages between controllers and
IOMs.

The above diagram depicts a basic Ethernet topology implementation. Key Configuration Rules
include:
• 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, where
the Ethernet is in a Control Rack. However, you can use the Ethernet Module with Redundant
C200 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 same
Server is not supported in R320.
• A downlink ControlNet segment must be used to support remote I/O. An Ethernet Module, located
in 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 in
the PC. A separate PC Ethernet Interface card is required between the Server and the Stations.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 52 Release 320

“Controller Redundancy at a Glance” Example


TC-PRS021 -- C200 TC-CCR013 -- CNI to TC-FXX072 -- 7-slot Chassis
Control Processor connect to I/O chassis
Redundant Chassis
TC-CCR013 -- CNI, TC-PRR021 -- Identical Configuration
Redundant Media Redundancy (module-for-module)
Module

OK OK

Honeywell Honeywell
TC-FPCXX2 -- GN-KRRxx1 -- Redundancy
120/240 VAC Cable (Fiber
Power Supply

ControlNet Cable -- I/O Comm

ControlNet Cable (TC-KCCxxx) -- Supervisory


Terminators -- to
TC-TCXBNC Server
NO IOMs or ETHERNET MODULES
PERMITTED IN CONTROLLER
NO IOMs PERMITTED CHASSIS
IN CONTROLLER
CHASSIS FORCONFIGURATION!!
FOR REDUNDANT
CONFIGURATION!!
to
Chassis

Figure 19. Redundant Controller Configuration Example


The above example illustrates some key configuration rules and requirements for Controller
Redundancy. These include:
• Specific models that support redundancy must be used in both chassis of a redundant chassis pair: C200
Control 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 support
redundancy at this time.
• Both chassis of a redundant chassis pair must have identical slot-for-slot configurations (i.e., same location
in 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 supported
per CNI. Note that support for 64 IOMs (the maximum per controller) only requires 3 CNIs. All I/O
CNIs may share a single ControlNet trunk cable, or individual cables may be used as needed. As an
example, a controller with 3 I/O CNIs could use a single I/O ControlNet cable, two I/O ControlNet
cables or three individual cables. All three configurations would be valid.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 53

“FOUNDATION Fieldbus at a Glance” Example

Ethern et (TCP/IP)

Hig
Lowh Ala
Alarm
rm
Redundant
Com.mErr.
High Ala rm
Low Alarm
Comm. Err.
PlantScape
Servers
TC-NIFB01 - NI Configurator Software
MZ-NTTP02 - RSLINX Software
PlantScape Stations
ControlNet, Redunda nt Media
Redundant Non-Redundant
Control Control
Processor Processor

TC- CCR01 3, ControlNet

ControlNet
ControlNet

1757-CN2FF -
Linking Devices
24 VDC
(DIN Rail Mounted)
Condit ioned
Power
H1 Network (1) H1 (2) H1 (2) H1 (2) Remote I/O Ch assis - Se ries A

H1 (1) H1 (1) 24 VDC


H1 (1) Condit ioned
Power
H1 Network (2)

PT PT PT PT
FOUNDATION Fieldbus Device Networks

Figure 20. FOUNDATION Fieldbus Integration Example

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

! Support for FOUNDATION Fieldbus requires the Linking Device (1757-CN2FF). Each Linking Device
supports up to two (2) FOUNDATION 31.25 kbaud H1 networks. Each network is permitted to
support no more than 10 FOUNDATION Fieldbus devices. Up to eight (8) Linking Devices can be
used on a single I/O ControlNet segment.
! Each Linking Device requires separate 11-30 VDC power (nominally 24 VDC) at 270 mA. A
Linking Device does not provide power to the H1 network. Power, conditioning and network
termination must be provided separately. Refer to Fieldbus FOUNDATION Specifications for
detailed rules and topology.
! PlantScape Process software version R310 or greater is required. The National Instruments
Fieldbus Configuration Package (TC-NIFB01) configures the Foundation Fieldbus devices. Allen-
Bradley RSLINX Software (MZ-NTTP02) is required for the NI Configuration Package to function
correctly.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 54 Release 320

Model Numbers
Table 16. Controllers, Racks, Power Supplies & Communications Modules
Model Description Uncoated Model Coated Model
1
Number Number
Hybrid Controller
2
C200 Control Processor TC-PRS021 TK-PRS021
Battery Extension Module TC-PPD011
Redundancy
Redundancy Module TC-PRR021 TK-PRR021
Redundancy Cable 1 Meter GN-KRR011
Redundancy Cable 3 Meter GN-KRR031
Redundancy Cable 10 Meter GN-KRR101
Racks
4 Slot Rack TC-FXX042
7 Slot Rack TC-FXX072
10 Slot Rack TC-FXX102 TK-FXX102
13 Slot Rack TC-FXX132 TK-FXX132
17 Slot Rack TC-FXX172
Power Supplies
120/240 VAC Power Supply TC-FPCXX2 TK-FPCXX2
24 VDC Power Supply TC-FPDXX2 TK-FPDXX2
Communication
3
ControlNet Interface (single media) TC-CCN013
3
ControlNet Interface (redundant media) TC-CCR013 TK-CCR013
Ethernet Interface Module TC-CEN011
Allen-Bradley Fieldbus Linking Device 1757-CN2FF
4
ControlNet ISA Interface 9904-KTCX15
4
ControlNet PCI Interface TC-PCIC01
1
Conformal coating optional except as noted.
2
Each operating Control Processor or Redundant Control Processor Pair requires purchase of one
Control Solver license, TC-SWCS11 or TC-SWCS21. Note that the actual software is included with
the PlantScape Process Server Software, MZ-PSPBxx. TC-SWCS11 and TC-SWCS21 consist of the
license to use this software.
3
The Series “D” (Tx-CCx013) ControlNet Interface Modules ship with R310 and later. They displace
their corresponding model numbers from Series “C” (Tx-CCx012). The Linking Device requires the
use of either the new Series CNIs or the previous Series “C with updated R310 firmware.
4
9904-KTCX15 and TC-PCIC01 are used with both dual and single ControlNet media. 9904-KTCX15
will be replaced in R320 by TC-PCIC01. 9904-KTCX15 is only available for R310 and earlier systems
and replacements.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 55

Rack Configuration Services


Model 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 their
original factory containers. Customers are then responsible for making sure all Controllers, RMs, IOMs, CNIs, and
KTC cards have the appropriate firmware and loading if necessary (instructions are included with the system). If a
Server is purchased, PlantScape Server software is loaded and the ControlNet Interface card is configured regardless
of 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 9904-TPR 9904-TPYS 9904-TPYR


(straight) (right angle) (straight) (right angle)

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 56 Release 320

Table 18. Terminal Blocks, Cables and Connectors


Model 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-KCC200 200 meters
TC-KCC500 500 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.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 57

Table 19. Hybrid Controller Software


Model Number Model Description
1
TC-SWCS11 CS01 Control Solver (license only)
1
TC-SWCS21 CS02 Control Solver 5 msec CEE (license only)
2
TC-SWCB11 CB10 Control Builder
- CL01 Continuous Library
- SL01 Sequential Library
3
TC-SWCB31 CB10 Control Builder Client License
TC-NIFB01 National Instruments Fieldbus Configuration Package
(required, along with MZ-NTTP02, RSLINX, to configure FF devices)
1
One CS01 or one CS02 license is required to be purchased for each individual operating Control
Processor or Redundant Control Processor pair. Software is provided as a part of PlantScape
Base Server System Software, MZ-PSPBxx, but the license is not included.
2
One license is included as a part of PlantScape Base Server System Software, MZ-PSPBxx.
Must purchase an individual license for each separate usage.
3
TC-SWCB31 allows ControlBuilder access to engineering databases via TCP/IP and UDP/IP
communications. It can be run in clients loaded with Station or Server. A login dialog provides
access restriction. Each database can be accessed simultaneously by up to four (4) clients. A
license is required for each accessing client.

Table 20. PlantScape Station Software


Model Number Model Description
MZ-NTUL04 PlantScape Process Station - 1 User
MZ-NTUL05 PlantScape Process Station - 5 User
MZ-NTUL06 PlantScape Process Station - 10 User

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 58 Release 320

Table 21. PlantScape Server/Station Hardware


Model Number Model Description
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
1
MZ-PCDU03 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 Overlay
1
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 GUS
documentation for product details.

Table 22. Distributed Server Architecture (DSA) Licenses


Model Number Model Description
Base Server System (Software & License)
1
MZ-NTDS00 DSA Enabling License (Required for DSA)
MZ-NTDS01 DSA License, Maximum 2 Remote Servers
MZ-NTDS02 DSA License, Maximum 5 Remote Servers
MZ-NTDS03 DSA License, Maximum 10 Remote Servers
MZ-NTSE01 DSA License Expansion, Max 2 To Max 5 Servers
MZ-NTSE02 DSA License Expansion, Max 5 To Max 10 Servers
1
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.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 59

Table 23. PlantScape Process Server Software


Model Number Model Description
1
MZ-PSW320 PlantScape Media and Documentation for R320
1
MZ-PSW310 PlantScape Media and Documentation for R310
Base Server System Software (License Only)
MZ-PSPB02 Process Base Server Software 50 Cont Mods/Points
MZ-PSPB03 Process Base Server Software 100 Cont Mods/Points
MZ-PSPB04 Process Base Server Software 300 Cont Mods/Points
MZ-PSPB05 Process Base Server Software 650 Cont Mods/Points
MZ-PSPB06 Process Base Server Software 1,000 Cont Mods/Points
MZ-PSPB07 Process Base Server Software 2,000 Cont Mods/Points
MZ-PSPB08 Process Base Server Software 5,000 Cont Mods/Points
MZ-PSPB09 Process Base Server Software 10,000 Cont Mods/Points
MZ-PSPB10 Process Base Server Software 15,000 Cont Mods/Points
MZ-PSPB11 Process Base Server Software 20,000 Cont Mods/Points
Server Database Point Count Expansion Software (License Only)
MZ-PSBE02 Process Base Server Software 50 to 100 Point Expansion
MZ-PSBE03 Process Base Server Software 100 to 300 Point Expansion
MZ-PSBE04 Process Base Server Software 300 to 650 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-PSBE07 Process Base Server Software 2,000 to 5,000 Point Expansion
MZ-PSBE08 Process Base Server Software 5,000 to 10,000 Point Expansion
MZ-PSBE09 Process Base Server Software 10,000 to 15,000 Point Expansion
MZ-PSBE10 Process Base Server Software 15,000 to 20,000 Point Expansion
MZ-PSPBxx includes Controller & System Documentation, Control Solver software (licenses must
be purchased separately), Control Builder (one license included), and Station (one license
included). MZ-PSBExx allows Base System Server size expansion. Note that MZ-PSPBxx
includes all components of the SCADA Development Base System Software, MZ-NTBDxx, except
for the one included driver, and performs all SCADA functions as well.
1
MZ-PSW320 and MZ-PSW310 contain release-specific software, documentation, mouse pad,
overlay, promotional CD and packaging. They cannot be ordered separately. When ordering
through e.BOB or the TPC, one copy is included with MZ-PSPBxx.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 60 Release 320

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-PSPR03 Process Server Redund Software - 100 Point
MZ-PSPR04 Process Server Redund Software - 300 Point
MZ-PSPR05 Process Server Redund Software - 650 Point
MZ-PSPR06 Process Server Redund Software – 1,000 Point
MZ-PSPR07 Process Server Redund Software – 2,000 Point
MZ-PSPR08 Process Server Redund Software – 5,000 Point
MZ-PSPR09 Process Server Redund Software – 10,000 Point
MZ-PSPR10 Process Server Redund Software – 15,000 Point
MZ-PSPR11 Process Server Redund Software – 20,000 Point
Server Expansion Redundancy Software Adder (License Only)
MZ-PSRX02 Process Server Redund Software 50-100 Point Expansion
MZ-PSRX03 Process Server Redund Software 100-300 Point Expansion
MZ-PSRX04 Process Server Redund Software 300-650 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
MZ-PSRX07 Process Server Redund Software 2,000-5,000 Point Expansion
MZ-PSRX08 Process Server Redund Software 5,000-10,000 Point Expansion
MZ-PSRX09 Process Server Redund Software 10,000-15,000 Point Expansion
MZ-PSRX10 Process Server Redund Software 15,000-20,000 Point Expansion
Redundancy Option does not include a Station License and must match base Server size.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 61

Table 25. PlantScape Software Options and Tools


Model Number Model Description
Third-Party Communication Interface Software
1
MZ-NTTP01 Allen-Bradley RSLINX Software, Ver 1.7 (for R130 and earlier)
1
MZ-NTTP02 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
2
MZ-AUIF01 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 the
Linking Device (1757-CN2FF). Only version 2.1 (currently being shipped) is supported for Fieldbus
Integration.
2
Required for MZ-NTIF10.
All models above are Licenses only.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 62 Release 320

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.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 63

Table 27. SCADA to Process Server Conversion Software


Model 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-PSSU04 SCADA to Process Conversion, 300 Points
MZ-PSSU05 SCADA to Process Conversion, 650 Points
MZ-PSSU06 SCADA to Process Conversion, 1,000 Points
MZ-PSSU07 SCADA to Process Conversion, 2,000 Points
MZ-PSSU08 SCADA to Process Conversion, 5,000 Points
MZ-PSSU09 SCADA to Process Conversion, 10,000 Points
MZ-PSSU10 SCADA to Process Conversion, 15,000 Points
MZ-PSSU11 SCADA to Process Conversion, 20,000 Points
*Conversion to 100 Point Process System
Model Number Model Description
SCAN 3000 or PlantScape SCADA to PlantScape Process Redundancy (License Only)
MZ-PSRU01 SCADA To Process Redundancy, 20 Points
MZ-PSRU02 SCADA To Process Redundancy, 50 Points
MZ-PSRU03 SCADA To Process Redundancy, 100 Points
MZ-PSRU04 SCADA To Process Redundancy, 300 Points
MZ-PSRU05 SCADA To Process Redundancy, 650 Points
MZ-PSRU06 SCADA To Process Redundancy, 1,000 Points
MZ-PSRU07 SCADA To Process Redundancy, 2,000 Points
MZ-PSRU08 SCADA To Process Redundancy, 5,000 Points
MZ-PSRU09 SCADA To Process Redundancy, 10,000 Points
MZ-PSRU10 SCADA To Process Redundancy, 15,000 Points
MZ-PSRU11 SCADA To Process Redundancy, 20,000 Points

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 64 Release 320

Table 28. PlantScape Documentation


Model 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)
1
TC-DCSX21 Getting Started With PlantScape
TC-DCSX31 PlantScape Software Installation and Upgrade Guide
2
TC-DCDX11 PlantScape Knowledge Builder Documentation (CD-ROM for 1 Server)
TC-SDOC01 PlantScape Site Docs
TC-DPQ001 PlantScape Product Qualification Handbook
1
One copy included with each PlantScape Process Server system shipped.
2
Included with Process Base Server Software MZ-PSPBxx.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 65

Table 29. PlantScape Demonstration Unit


Model Number Model Description
TC-DEMO11 PlantScape Demonstration System
TC-DEMOC1 PlantScape Demo System Case
1
TC-DSW320 PlantScape Demo Media and Documentation for Release 320
2
TC-SWDEMO PlantScape Demonstration Software License
1
Contains release-specific software, documentation, mouse pad, overlay, promotional CD and packaging. Once
copy is included when the license,TC-SWDEMO, is ordered. The latest release is always assumed unless
otherwise specified.
2
Can 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 be
used for demonstrations and training purposes. It does not include the server or monitor, but
includes all needed hardware components, including a simulator panel which interfaces with the
controller 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 for
PlantScape 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

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 66 Release 320

Appendix A: Server Hardware Requirements

Honeywell offers the latest PCs for optimal server performance. Should a PlantScape customer need
to purchase their PC independently, the following requirements must be followed. Honeywell does not
support customer-purchased PC hardware nor PC operating software. However, with Carbon Copy 32
software 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 complex
process is being considered, this will effect the size of the database. For example, a configuration may
require 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 the
small system. Use the table below to approximate your database size.

Table 1.1. Database Sizing Chart


System Definition Database Configuration Examples
Suggestion Size
May consist of: 0-200 MB ! 1 Hybrid Controller *
Small
! 1 non-redundant Server ! Process systems with up to 100
! 1 station CM/SCM/IOM
! Passive monitoring and ! SCADA systems with up to
occasional report generation 3,000 Points
May consist of: 200-350 ! 2-3 Hybrid Controllers *
Medium
! 1 non-redundant Server and MB ! Process systems with up to 500
multiple stations OR CM/SCM/IOM
! 2 redundant Servers with no ! SCADA systems with up to
more than 2 additional 10,000 Points
stations and 1 DSA Server.
! 1 or 2 stations
! Active monitoring with
occasional report generation
May consist of: 350-500 ! More than 3 - 4 Hybrid
Large
! 2 redundant Servers MB Controllers *
Workstation
! Multiple DSA Servers ! Process systems with 500 - 600
CM/SCM/IOM
! Up to 8 Stations
! SCADA systems with more than
! Active monitoring from
10,000 points.
multiple Stations

May consist of: Greater ! 5 or more Hybrid Controllers *


Large Server
! 2 redundant Servers than 500 ! SCADA systems with more than
MB 10,000 points
! Multiple DSA Servers
! Up to 20 Stations (40 for ! Process systems with more than
SCADA 600 CM/SCM/IOM
! Active monitoring from
multiple Stations
!
* Hybrid Controllers configured in a redundant mode should be counted as 1 Hybrid Controller.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 67

Table 1.2. Minimum Platform Requirements based on System Configurations


Server Station
System Small Medium Large Small Med Large
Configuration
Processor 266-400 550 Mhz 800 Mhz 200 Mhz 300 – 400 550 Mhz
Mhz Pentium II Pentium III Pentium Pro Mhz Pentium III or
Pentium II or higher Pentium II higher
RAM
• Win 95/98 -- -- -- 64 MB 64 MB 96 MB
1 1
• Win NT 64 MB 96 MB 128 MB 64 MB 64 MB 96 MB
Workstation
1 1
• Win NT Server 96 MB 128 MB 160 MB --
Video 1024 x 768 1024 x 768 1024 x 768 1024 x 768 1024 x 768 1024 x 768
2 65K colors 65K colors 65K colors 65K colors 65K colors
Resolution 65K colors
Hard Drive 2 GB 4.3 GB 9.1 GB 2 GB 4.3 GB 4.3 GB
1
In these configurations, paging may occur on these systems.. Based on the intended usage of the platform, this configuration
is acceptable. For better performance, users should upgrade the systems with an additional 64 MB of RAM.
2
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 with 65K colors. Mhz
setting should be set to match the monitor

Table 1.3. Typical Platform Requirements based on System Configurations


Server Station
System Small Medium Large Small Med Large
Configuration
Processor 266 - 400 550 Mhz 800 Mhz 200 Mhz 300 – 400 550 Mhz
Mhz Pentium III Pentium III Pentium Pro Mhz Pentium III or
Pentium II or higher Pentium II higher
RAM
• Win 95/98 -- -- -- 64 MB 64 MB 96 MB
• Win NT 160 MB 192 MB 224 MB 80 MB 80 MB 112 MB
Workstation
• Win NT Server 160 MB 224 MB 288 MB -- -- --
Video 1024 x 768 1024 x 768 1024 x 768 1024 x 768 1024 x 768 1024 x 768
Resolution 65K colors 65K colors 65K colors 65K colors 65K colors 65K colors

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 Manufacturers
Spec. Please refer to Video Card Specifications for details. All systems should be set 1024 x 768 with 65K colors. Mhz
setting should be set to match the monitor.

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 68 Release 320

Table 1.4. High Performance Platform Requirements based on System Configurations


Server Station
System Small Medium Large Small Medium Large
Configuration
Processor 300-400 550 Mhz 800 Mhz 266 Mhz 300 – 400 550 Mhz
Mhz Pentium III Pentium III Pentium II Mhz Pentium III
Pentium II or higher Pentium II or higher

RAM
• Win 95/98 -- -- -- 64 MB 64 MB 96 MB
• Win NT 160 MB 224 MB 256 MB 96 MB 96 MB 128 MB
Workstation
• Win NT Server 192 MB 224 MB 320 MB -- -- --
Video 1024 x 768 1024 x 768 1024 x 768 1024 x 768 1024 x 768 1024 x
1
Resolution 65K colors 65K colors 65K colors 65K colors 65K colors 768 65K
colors
Hard Drive 4.3 GB 4.3 GB 9.1 GB 4.3 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
Manufacturers Spec. Please refer to Video Card Specifications for details. All systems should be set 1024 x 768 with
65K colors. Mhz setting should be set to match the monitor.

PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 69

Table 1.5. Application Usage Chart


From the prior tables, Server configuration memory allocations assume server services only. Station Client
memory usage already includes the PlantScape Client Applications. However, most applications can be run on
either the Servers or Station Clients. On small to medium systems, these applications may be run on the
Server Platforms. RAM should be upgraded on these systems to accommodate each of the applications
1
intended to be used on a regular basis.
On large systems, the Servers should be dedicated to running only the Server Services. On these
systems, when possible, all applications should be run from the client stations.
Application RAM Usage
NT Applications
Explorer 4 MB
2
User Manager 2 MB
2
Disk Administrator 2 MB
Event Viewer 2 MB
2
Task Manager 2 MB
Internet Explorer 6 MB
NT Backup 3 MB
PlantScape Applications
3
Station 5 MB
Control Builder 13 MB
2
Network Tools 3 MB
2
Quick Builder 10 MB
2
DB Admin 10 MB
2
Import Export Tool 7 MB
Knowledge Builder Adds 2 MB on top of Internet Explorer
Other Applications RAM Usage
Total Plant Batch 128 MB
(Includes multiple NT Services and Applications)
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 MB
Notes:
1
Application usage on Servers greatly effects the CPU resources. A CPU upgrade or platform upgrade
should 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 only
include 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 both
physical boxes per application. For Example, if the server is going to support 5 Stations, then you would require
an additional 25 MBs. (5 x 5)

PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 70 Release 320

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 of
merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written
agreement with and for its customer.

In no event is Honeywell liable to anyone for any indirect, special or consequential damages.
The information and specifications in this document are subject to change without notice.

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


Honeywell
Industrial Automation and Control
16404 N Black Canyon Hwy
Phoenix, AZ 85023
(602) 313-5000

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

You might also like