Professional Documents
Culture Documents
PS03-132
Release 320
Revision Date: 27 October 2000
Version 1.0
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 3
Revision Status
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!
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
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 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
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.
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.
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.
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.
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
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 & 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.
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:
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
• 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.
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:
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
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
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:
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
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:
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.
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 25
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.
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 26 Release 320
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:
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 31
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 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
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
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
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
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 38 Release 320
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.
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 40 Release 320
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)
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
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 43
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 44 Release 320
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 45
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 46 Release 320
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.
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 47
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
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 48 Release 320
(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.
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 49
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 50 Release 320
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)
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
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 51
Redundant
Second
PlantScape
Redundant
Server
PlantScape
Server
ControlNe t
PLC5/E
Ethernet
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
OK OK
Honeywell Honeywell
TC-FPCXX2 -- GN-KRRxx1 -- Redundancy
120/240 VAC Cable (Fiber
Power Supply
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 53
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
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
PT PT PT PT
FOUNDATION Fieldbus Device Networks
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
• 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.
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 56 Release 320
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 57
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 58 Release 320
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 59
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 60 Release 320
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 61
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 62 Release 320
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 63
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 64 Release 320
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 65
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.
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 66 Release 320
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.
PlantScape System & Controller Specification & Technical Data -- Release 320
Ver 1.0 PS03-132
Release 320 Page 67
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 68 Release 320
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
PlantScape System & Controller Specification & Technical Data -- Release 320
PS03-132 Ver 1.0
Page 70 Release 320
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.
PlantScape System & Controller Specification & Technical Data -- Release 320