Download plantscape distributed server architecture–elevating

PLANTSCAPE DISTRIBUTED SERVER
ARCHITECTURE –ELEVATING DISTRIBUTED
CONTROL TO THE HIGHEST PLATEAU
PlantScape offers the most flexible, high
performance architecture of any distributed
control system on the market today.
With the introduction of PlantScape Distributed Server Architecture, Honeywell
has achieved yet another industry first.
Unique to Honeywell, Distributed Server
Technology elevates distributed control
to a level not previously imagined, by allowing multiple PlantScape systems
to operate as one - within a single plant,
or across the world, without any duplication
of engineering effort. Distributed Server
Architecture embodies Honeywell’s unique
experience in the full breadth
of applications, from process control to
true SCADA.
Features
• Truly Distributed Architecture
– Plant-wide systems
– Geographically distributed
systems – SCADA or inter-plant
• Global Database
– Absolutely no duplicate engineering
– Highest performance from
Dynamic Cache and publish/
subscribe technology
– Global alarming and messaging
– Global real-time data access
– Trending of real-time and historical
system-wide data on a single trend
– Global security model makes
configuration easy
• Engineered for maximum robustness
– Transparent redundant server support
– Redundant network support – local
or wide area
– Predictable handling and recovery
from network or server outages
PlantScape’s Distributed
Server Architecture will
change the way you think
of control system design
Features
• Truly Distributed Architecture – plant-wide,
Truly Distributed
Architecture
PlantScape’s foundation is based upon
Honeywell’s rich Process Control and
SCADA heritage. 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. Combine
the capability of Distributed Server Architecture for distributed operations with the
built-in remote support of PlantScape
engineering and monitoring tools, and the
result is a truly distributed system.
inter-plant and SCADA
• Global Database – systemwide alarming, real-time
and historical data access
• Highest performance
from Dynamic Cache
and publish/subscribe
technology
• Maximum robustness –
redundant server and network support
Geographically Distributed
Systems – SCADA
Or Inter-Plant
A geographically distributed system
gathers data from a wide area, allowing
the system to be viewed and/or controlled
locally and remotely. Examples of this
type of architecture include multi-segment pipelines, and oil and gas fields,
with a number of wells controlled either
from the platform, or from a central
control room onshore. Another common
scenario is inter-plant, where multiple
PlantScape sites can be integrated. With
geographically distributed architectures,
the communication bandwidth of the
network between the remote locations
is typically less than that available
within a plant site.
Figure 1 shows an example of a
geographically distributed system with
a wide area network connecting the
servers. 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 exchange information with each other.
The servers may be PlantScape SCADA
servers connected to controllers, such
as RTUs and PLCs, or PlantScape
Process servers connected to PlantScape
hybrid controllers.
Master Control Center
Process/SCADA
Server
Wide Area Network
Site A
Site B
Process/SCADA
Server
Site C
Process/SCADA
Server
Process/SCADA
Server
Figure 1 – Geographically Distributed System
Global Database
A global database is the pinnacle for
all true distributed control systems.
Many systems are unable to offer a
global database for a single control
engineering effort to implement and
maintain a particular application is
assessed, the weaknesses are exposed.
Utilizing PlantScape’s Distributed
Server Architecture, configuration is
performed only once for any process
Plant Network
Plant/Process A
Plant/Process B
Process/SCADA
Server
Process/SCADA
Server
Plant/Process C
Process/SCADA
Server
Plant-Wide Systems
A plant-wide system exchanges data
between logically separate PlantScape
systems located in different parts of the
plant. Each part of the plant typically
has its own control room. The communication bandwidth of the network between the servers is typically high, for
example, at least 10MB Ethernet.
Figure 2 shows an example of a plantwide system. There is a high-speed,
plant-wide network connecting the
servers. Each server is accessing a subset
of the information from one or more of
the other servers. The servers may be
PlantScape Process servers connected
to PlantScape hybrid controllers, or
PlantScape SCADA servers connected
to controllers, such as PLCs.
Figure 2 – Plant-wide System
application, let alone for a flexibly
connected set of semi-autonomous
systems. Systems without global databases typically suffer from heavy duplication of data, high network loads,
mis-matched configuration and duplicate alarms. This results in poor operational performance, lower reliability, and
very high cost of engineering and
maintenance. With Distributed Server
Architecture, PlantScape has raised the
bar to new heights with transparent
global data access that spans multiple
PlantScape systems.
Absolutely No Duplicate
Engineering
Many control system architectures
may look alike on paper, but when the
information. All other servers in the
Distributed Server Architecture may
then directly access information, subject
to security settings, without any additional
configuration effort. For example, changes
to point, alarm, or custom displays are
available throughout the Distributed
Server Architecture automatically.
Highest Performance From
Dynamic Cache And Publish/
Subscribe Technology
Traditional flat control architectures,
where operator stations and applications
draw data directly from the controller,
suffer from an inherent performancelimiting bottleneck, as both load on the
data owner, and networks increase
steadily with increased demand for data.
Honeywell achieved a first when the
Dynamic Cache was implemented and
patented as part of the core PlantScape
architecture in 1997. The cache allows
maximum leverage of the extensive
operational and diagnostic information
in the hybrid controller, while retaining
maximum scalability.
PlantScape was designed so that only
data that is currently being subscribed
by operator stations or applications,
will automatically be published on-change
to the Dynamic Cache in the requesting
PlantScape server. All data consumers,
local or remote, access the Dynamic
Cache of their associated server for all
their data needs, thus ensuring a minimal
and predictable load on the control network and controllers.
Distributed Server Architecture naturally
extends the use of the Dynamic Cache
to achieve never-before possible levels
of efficiency in intersystem global data
transfer. Just as data subscribed from a
hybrid controller is automatically entered
into the Dynamic Cache, so is data subscribed from one PlantScape server to
another. The result is that data is always
accessed the minimum number of times
from the ultimate data owner. Distributed
Server Architecture results in a dramatic
reduction in system and network loading,
analogous to the revolution of collapsedbackbone networking where network
switches, have replaced flat, busconnected networks. Data within a
server is exchanged at computer memory
speeds for maximum performance
within the local process domain. Data
transferred between servers is published
on-change and only to those servers
currently subscribing, making optimal
use of available network bandwidth.
For example, in figure 3, data consumers
at Systems A, B, and C wishing to access
FIC101.PV from System C, will all be
sharing a dynamically cached value
available from their local servers. New
data is only transmitted over the network
once to each subscribing system, no
matter how many data consumers require
that data on each system.
Applications
Applications
FIC101.PV
FIC101.PV
Dynamic Cache
Dynamic Cache
PlantScape Server A
PlantScape Server B
Legend:
= Publish On Change
PlantScape
Server C
FIC101.PV
Applications
Dynamic Cache
FIC101.PV
Hybrid Controller
Figure 3 – Example of Dynamic Cache
Global Alarming And Messaging
For many systems, global alarming
across multiple nodes within the same
system is a challenge. PlantScape
achieves global alarming, not only
within a single PlantScape system, but
also across all systems in a Distributed
Server Architecture.
Alarms and messages from subscribed
areas, local and remote, are all time
synchronized and integrated into global
alarm and message summaries for
display. Alarm and message acknowledgement is also fully supported between
servers. Acknowledgement can be on
a global basis, or a per-server basis,
depending on the application requirement. Alarms may be enabled or disabled
by point or area, which is standard for
any PlantScape system.
Global Real-Time Data Access
Custom displays may be created to access
data across all systems with Distributed
Server Architecture. The same display
may be accessed transparently via any
PlantScape system within the architecture. Standard group and point detail
displays may also access data directly
from anywhere in the system.
Third party applications enjoy the same
global data access as core PlantScape
sub-systems. For example, an OLE for
Process Control (OPC) client application
hosted on System A requires access to
all data in System A, plus data from re-
mote plant areas. Rather than having to
go to System A, System B, and System C
through separate OPC connections, the
OPC client application is unaware of
where the data resides, and can simply
access all the data as if it were resident
in System A. Distributed Server Architecture takes care of the rest. This type of
data access has additional benefits, such
as automatic, redundant communications
handling with configurable timeouts,
features not available with OPC and
DCOM. Data access is not limited
to OPC clients. Packages such as
TotalPlant® Batch, that directly integrate
via PlantScape’s public Application
Programming Interfaces, experience
the same benefits. No special configuration is required. Efficient global data
access, with full security is provided.
Trending Of Global Real-time And
Historical Data On A Single Trend
Viewing history from a remote PlantScape
server is as simple as dropping the tag
and parameter name into a standard or
custom trend display. The PlantScape
system does the rest, automatically
retrieving the historical data for on-line
display. A PlantScape trend display can
display real-time and historical data
from PlantScape servers anywhere in
the Distributed Server Architecture.
Just as real-time data and alarms are
globally available to applications, so is
historical process and event data, via
Open Database Connectivity (ODBC).
Global Security Model Makes
Configuration Easy
Transparent Redundant
Server Support
Distributed Server Architecture naturally
extends the powerful area-based security
model that PlantScape users are already
familiar with, featuring a complete
security system to protect the process
and valuable associated information.
Distributed Server Architecture provides
transparent support for PlantScape
server redundancy. Whether all, some,
or none of the servers in a Distributed
Server Architecture are redundant, the
publish/subscribe infrastructure will get
the job done without requiring complex
configuration.
Each PlantScape server can be partitioned
into a maximum of one thousand plant
areas. Distributed Server Architecture
enables a local server to simply reference
remote areas on other servers to which
it requires operational access.
Having identified the remote areas of
interest, security is configured for each
PlantScape system. Point, alarm and
display access then behave across the
architecture for all configured areas as
if it were a single PlantScape system.
It’s that simple. Where user’s choose to
leverage the extra security offered by
PlantScape control levels, the operator’s
control level is automatically passed to the
remote server to ensure that operator’s are
only able to control assigned points.
Engineered for
Maximum Robustness
Flexible architectures alone are not
sufficient to deliver value to users. Day
in, day out, architectures must be dependable. PlantScape’s Distributed Server
Architecture is engineered to be rugged
and dependable.
Redundant Network
Support – Local Or Wide Area
Whether your application is based around
a local high-speed Ethernet, wide area
links, ranging from leased circuit to
microwave, or a combination, communications have to be reliable. Any or all
communications links in a Distributed
Server Architecture may be redundant.
As you’d expect, redundant network
links are all handled automatically and
seamlessly.
Like all other system-level networking
functions in PlantScape, Distributed
Server Architecture requires only that
network links support TCP/IP. As a
result, the user has unlimited flexibility
to implement network architectures which
best support the application. Unlike
some more restrictive systems, these
networks are open and can be shared with
other applications.
Predictable Handling And
Recovery From Network Or
Server Outages
It is always possible that a network
or server computer will experience a
fault. Distributed Server Architecture is
designed to diagnose, report, and recover
from such failures, automatically. Where
remote servers are unavailable, due to
network or server computer outages, the
local server will signal an alarm accordingly. Likewise, when networks or servers are recovered, communications and
normal system functions, such as global
alarming, data and history access, will
automatically recover along with them.
And, of course, utilizing PlantScape’s
high performance remote dial-up operator
station, and engineering tools capability,
a backup connection to a remote system
for trouble shooting is only a phone
call away.
To learn how PlantScape’s Distributed
Server Architecture can meet your
specific needs, call 1-800-288-7491 in
the U.S. or access our public web site
at http://www.iac.honeywell.com.
Industrial Automation and Control
Honeywell Inc.
http://www.iac.honeywell.com
U.S.A.: Honeywell Industrial Automation and Control, 16404 North Black Canyon Hwy., Phoenix, AZ 85053
Canada: The Honeywell Centre, 155 Gordon Baker Rd., North York, Ontario M2H 3N7
Latin America: Honeywell Inc., 480 Sawgrass Corporate Parkway, Suite 200, Sunrise, Florida 33325
Japan: Industrial Operations Tokyo, 4-28-1 Nishi-Rokugo Ohtu-ku, Tokyo 144, Japan
Asia: Honeywell Asia Pacific Inc., Room 3213-3225, Sun Hung Kai Centre, No. 30 Harbour Road, Wanchai, Hong Kong
Pacific Division: Honeywell Pty Ltd., 5 Thomas Holt Drive, North Ryde NSW Australia 2113
Northern Europe and Southern Africa: Honeywell Ltd., Honeywell House, Arlington Business Park, Bracknell, RG 12 1EB, U.K.
Central Europe: Honeywell A.G., Kaiserleistraße 39, 63067 Offenbach, Germany
Western and Southern Europe: Honeywell S.A., Avenue du Bourget 1, 1140 Brussels, Belgium
Eastern Europe: Honeywell Praha, s.r.o., Budejovicka 1, 140 00 Prague 4, Czech Republic
Middle East: Honeywell Middle East Ltd., Khalifa Street, Sheikh Faisal Building, Abu Dhabi, U.A.E.
SL-53-655 (1M) 6/99
©Honeywell Inc.
Printed in U.S.A.
Recycled Paper