1 Overview

Training Course Honeywell DCS (TDC3000)
SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

1
CONTENTS
TPS System (DCS)

 TPS architecture
 Network devices
 Operator/engineering stations
FTE
ES GU
-T S APP Serv
er
Cons
LC ole
NI HM HG
N M
HP CB
M
TPS

2
What is a network?
A network is nothing more than two or more

computers connected together by some kind of
cable so they can communicate.
Through a network you can:
 exchange files
 access to database
 share applications
 data acquisition in real time

3
Total Plant Solution - TPS
Honeywell Network (Distribuited

Control System DCS –TDC3000)
Physically composed by Cables and Modules

4
Local Control Network (LCN)
Overview
The LCN is a coaxial and, sometimes additionally, a fiber optic
network that provides the data path for communication
between the TPS system nodes.
Cable network
Physically, the Local Control Network is composed of modules
that represent address nodes on the LCN. The modules are
interconnected by dual coaxial and/or fiber optic cables for
remote applications. The dual cables offer the reliability of
redundancy for the network.

5
Functionality
The Local Control Network
 carries all information transferred between the modules on the

network (including information going to or from the modules, and
information going to or from process subsystems integrated into
the TDC 3000 System)
 ensures the timely exchange of information through an

efficient protocol and highspeed communication.
 provides highly secure communication through active and

backup cables, and message-integrity

6
LCN modules types

Many different types of modules are available, such as History Module,
Universal Station, Universal StationX, Application Module, Hiway
Gateway, or Network Interface Module to identify a few.
Modules can be added to or removed from the network without disrupting
ongoing operations.
Options
The maximum number of modules on a single LCN is 64 (software
limitation).

7
TPS architecture

8
TPS architecture
Network and module types
 UNIVERSAL CONTROL NETWORK - UCN

 NETWORK INTERFACE MODULE - NIM
 HISTORY MODULE - HM
APPLICATION MODULE - AM
 SAFETY MANAGER MODULE - SM
 GLOBAL USER STATION - GUS
 HIGH PERFORMANCE PROCESS MODULE - HPM

9
TPS architecture

10
TPS architecture - Universal Control Network (UCN)

11
Universal Control Network (UCN)
Overview
 The UCN is a high-speed, high-security process network.
 It is connected to single or multiple TPS Networks using Network

Interface Modules (NIMs)
 Up to 20 UCNs
 Devices can be added to, or removed from the UCN to adjust to

changing system requirements

12
UCN is a control
Network
Process-Connected
devices
The UCN support
process controllers
such as the Process
Manager (PM),
Advanced Process
Manager (APM), and
the Logic Manager
(LM).

13
Functionality
It does the following:
provides the I/O interface to field devices

provides platforms for implementing sophisticated control
schemes (HPM), and platforms that perform safety-related
functions (FSC)
supports of redundant devices for added security
 allows for peer-to-peer communication between devices on this
network.
 the UCN uses redundant cables as standard, and can
accommodate up to 32 redundant devices

14
TPS architecture - Network Interface Module NIM

15
Overview
The Network Interface Module (NIM) provides the interface
between the Local Control Network (LCN) and the Universal
Control Network (UCN).
Redundancy
The Network Interface Module is capable of redundant
applications.

16
Functionality
Information concerning the process, such as status and

configuration, is transferred through the Network Interface
Module from the UCN to the LCN.
The Network Interface Module provides the protocol

conversion necessary to efficiently exchange information
between the UCN controllers and the LCN modules, such as
Universal Stations, History Modules, Application Modules, and
Plant Network Modules.

17
Functionality
Provides for data access between the TPS Network and the
Universal Control Network devices
Converts data and protocol between the TPS Network and the
Universal Control Network
 Channels UCN events to the TPS Network for alarming
Synchronizes TPS Network and UCN time

18
TPS architecture - History Module (HM)

19
Overview
The History Module provides mass storage for information,
including historical data.

20
Functionality
The History Module can communicate with all modules on the
Local Control Network and with the process-connected devices
on the Universal Control Networks and Data Hiways.
It stores process and system information that can be displayed

or printed.
History Module can store:

• Continuous process History (Sample Data– Averages)
• Event Journals (history) (Process Events-TDC 3000 System
Events – Sequence of Events)
• System Files
• General Files

21
Options
The number of History Modules needed for a specific system varies

according to system size and functionality.
Typically, one History Module is used for each Operator Console in a
TDC 3000 system so that the Operator Console and History Module
handle one process area.
Up to 20 History Modules can be configured on a Local Control

Network.

22
A History Module (HM) is structured in volumes and directories

Volume and directory names identify one of several partitions on the
HM
• Each volume can have up to 63 directories and up to 9995 files
• Data in the system is collected into named files that are stored in
named volumes and directories on HM
History Modules (HM) Volume Assignments and Sizes

•System Volumes
•User Volumes
•History Volumes
•Directories

23
2. TPS architecture – History Module (HM)
Pathnames, Volumes, Directories, and Files Relationships
• A volume can contain its own files and one or more directories. If a
volume does not have its own files, they are located in directories in
the volume.
• Directories can contain one or more files.
• Files contain the data that you enter and use as you configure a
system

24
2. TPS architecture – History Module (HM)
All volume and directory names are unique in an LCN
Some volume and directory names represent specific node pairs on

system

25
TPS architecture – History Module (HM)
 A volume often contains several directories (Directories are

subdivisions of Volumes).
 Files can be associated with volumes or with directories
A directory usually contains a

collection of related files. For
example, one system directory
(&ASY) contains the files related
to network configuration. A
common directory (CL) contains
files related to user programs
written in Control Language.

26
Pathnames, Volumes, Directories, and Files
Pathname form
A pathname is simply a description of the location of a file. That

description consists of these parts
• Device Identity
• Volume Directory Name
• File Name
• LCN
While directories are subdivisions of volumes, pathnames can include

either a volume name or a directory name in the volume/directory
field. When trying to access a file, the pathname must contain the
volume name or directory name where the file is located.

27
File names and suffixes
File names consist of one-to-eight characters. Suffixes (sometimes

called “extensions”) are one or two alphanumeric characters,
preceded by a period (dot).
Suffixes serve to identify the type of information contained in the file .
These are some of the more common system suffixes

CL=CL source file
DO=Schematic object file
DS=Schematic source file
EB=Exception-build file
EC=Execute Command file
KO=Button configuration object file
KS=Button configuration source file
LE=CL error listing file
LS=CL listing file

28
Pathname rules
It doesn't matter whether the letters in a pathname are capitals or

lowercase letters; each is treated as a capital letter.
The Device ID is always in one of these forms: $Fn, $Pn, PN:nn and
NET
• $Fn defines a floppy or cartridge drive number

• $Pn defines a printer device ID
• PN:nn defines a physical node number (LCN node number).
• NET indicates that the volume or directory is to be found in an on-
line History Module on the LCN

29
NET is the device name for any volume that is stored in an HM.
Only the HM with the named volume or directory responds
Summary
 Volume and directory names identify one of several partitions on
an History Module
 Each volume name and each directory name is unique
Files can be associated with volumes or with directories
The “&” or “!” which begin all system volume names are the
ampersand and exclamation point

30
TPS architecture - Application Module (AM)

31
Overview
The Application Module is one of the modules on the Local
Control Network (LCN).
Application Module (AM) communicates with other modules on
the same or other Local Control Networks (LCNs), and process
controllers on Universal Control Networks (UCNs) and Data
Hiways.

32
Functionality
Because of its position in the system architecture, the

Application Module can accept inputs from multiple process
controllers as well as other modules on different Local Control
Networks. (it communicates with other modules on the same or
other Local Control Networks and with process-connected
devices on the Universal Control Networks and Data Hiways) .
The Application Module can also provide control outputs to

control elements in the process or to other data points in
process control modules on other Local Control Networks.

33
Functionality
 Each Application Module data point can have multiple inputs

and outputs from many devices, and a single Application
Module can handle many data points
 The Control Language that executes in the Application

Module makes it easy to develop custom point processing and
special algorithms.
 The Application Module provides full cascade functionality

between an AM point and any process data point resident in
modules on different LCNs.

34
Data Point
 The Application Module contains a process database made up

of data points that the process engineer builds and assigns to it
during configuration.
 Each data point is a collection of fixed and dynamic

parameters that performs a specific function and is identified by
a point name.
 Datapoint processing can use either preprogrammed or

custom algorithms to calculate required information and/or
initiate specific control action.

35
TPS architecture - Safety Manager Module

36
The FSC Safety Manager (FSC-SM) is a process-connected

device which resides on the Universal Control Network (UCN) of
the TotalPlant Solution (TPS) system as a peer to the Process
Manager (PM, APM, HPM) and Logic Manager (LM).
It provides standard UCN node functionality, and can

communicate with the field devices directly or through connected
FSCs.
The FSC Safety Manager also supports the FSC networking
capability.

37
As illustrated in Figure, the FSC
Safety Manager (FSC-SM)
consists of two key components
mounted in one or more
standard FSC cabinets:
· FSC, a fail safe control system

from Honeywell Safety
Management Systems
· FSC Safety Manager Module

(FSC-SMM), a Honeywell Safety
Management Systems module
providing peer-to-peer
communications with other
process-connected devices
residing on the TPS system's
Universal Control Network

38
Human interfaces
As shown in Figure, two human interfaces
are used in conjunction with the FSC
Safety Manager:
1) Operating Work Station (named

Universal Station - US) is a user interface
and can be used to:
· monitor and control the process,
respond to alarms, print reports, and
change the equipment status
· set up the TPS process database,
displays and reports, and load FSC-SMM
system software
· diagnose and maintain both control
room and process-connected equipment.

39
FSC user station, with the FSC Navigator
software (R500), is used to interface with
the FSC to:
· configure FSC hardware and variables
· create and load the FSC control
program,
· diagnose FSC system faults,
· force variables for loop check-out and
maintenance of field devices,
· view FSC control program execution,
· print engineering documentation,
· log FSC sequence of events (SOE),
· verify the configuration and control
program of the FSC component.

40
FSC Navigator software

41
Point types associated with the Safety Manager
FSC-SM points are linked to FSC variables via alias addresses

For FSC variables, the alias address is referred to as the DCS address.
A DCS address is a five-digit number assigned to a variable in the FSC that
allows nodes on the UCN to reference that variable. The DCS address of an
FSC variable is the counterpart of the PLC address of an FSC-SM point.
ANALOG INPUT
ANALOG OUTPUT
DIGITAL INPUT
DIGITAL OUTPUT
DIGITAL COMPOSITE
NUMERIC
LOGIC
FLAG
TIMER

42
TPS architecture - Safety Manager Module 1
Example SM analog input

form configuration

43

form configuration

44

form configuration

45
4
form configuration

46
SM consists of two key

components mounted in one or
more standard TPS cabinets:
• TRICON Programmable Logic
Controller (a triple-redundant
PLC and associated subsystems
from Triconex Corporation)
• Safety Manager Module (SMM)
(a Honeywell option module
providing peer-to-peer
communications with other
process-connected devices
residing on the TPS Universal
Control Network.)

47
TPS architecture – Global User Station

48
The Global User Station module (GUS) provides a window to the
process, or processes, that the Local Control Network controls.
GUS connects operators directly to the process through
 preconfigured standard displays

 custom-built displays
and it lets them access information coming from anywhere else in

the plant.

49
The Global User Station communicates with other modules in

the Local Control Network:
 Modules in remote LCNs through the Network Gateway
 Process devices on Universal Control Networks through the

Network Interface Module
 Process devices in Data Hiways through Hiway Gateways.
The maximum number of Global User Station in a single console is 10

50
TPS architecture –Global User Station
The Global User Station is a Microsoft Windows NT-based
station
It consists of:
 Native Window
 Display Runtime - the Display Runtime component executes GUS

displays
 Safeview - is a window manager that allows a user to define where

types of windows can appear, move to, resize or overlap other windows

51
GUS is intended for use by operators and engineers to monitor and control the
process, Honeywell TPS components, and applications.

52
TPS architecture – Console
A console is a logical collection of Global User Stations and their

associated peripherals for use by one operator.
A console is associated with one process area
The maximum number of consoles per LCN is 10

53
TPS architecture – Icon Station
Engineering/operating Station

54
Global User Station Keyboard

55
GUS stations can include
Operator Keyboard
Engineer Keyboard
Integrated Keyboard (that combines predefined operator keys, 80

configurable operator keys, and a standard PC-type keyboard)

56
Global User Station Operator Keyboard

57

58
Global User Station
To meet different needs, the Global Universal Station has been

designed to serve three types of users.
 Operator
 Maintenance technician
 Engineer

59
Global User Station
Restricted access to network (to avoid dangerous actions on the

system)
4 level access to the DCS:
 View only: no access to database process
 Operator level: limited access to database
 Supervisor level: restricted acces to network
 Engineering level: all network

60
Global User Station
4 level access to the system

61
Global User Station Keyswitch
There is a 3-position keyswitch on the Operator’s keyboard:
• Operator’s key: no access to database entries

• Supervisor’s key: access to database entries – it unlocks
certain functions such as changing an alarm limit
• Engineer’s key: access to database entries – it unlocks all
functions
Note: if you try to access a function without the proper key, the
message “ACCESS LEVEL ERROR” appears.

62
TPS - Distribuited Control System
Engineering access to network
Tools for Process Engineer Functions
 to design and implement the control system database
 to design and implement the control operating displays
 design Control Language programs

63
TPS architecture - High Performance Process Manager

64
TPS architecture – High Performance Process Manager
The High-Performance
Process Manager (HPM)
is the control platform for
the TPS system

65
TPS architecture – Data Hiway
Data Hiway performs the first level of process control, consist of

data-acquisition units, controllers, and other interfaces to
specialized types of equipment

66

1 Overview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1 Overview

Uploaded by

Copyright:

Available Formats

Training Course Honeywell DCS (TDC3000)

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

TPS System (DCS)

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

A network is nothing more than two or more

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

Honeywell Network (Distribuited

Physically composed by Cables and Modules

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

The Local Control Network

 carries all information transferred between the modules on the

 ensures the timely exchange of information through an

 provides highly secure communication through active and

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

LCN modules types

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

Network and module types

 UNIVERSAL CONTROL NETWORK - UCN

 SAFETY MANAGER MODULE - SM

 GLOBAL USER STATION - GUS

 HIGH PERFORMANCE PROCESS MODULE - HPM

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

 It is connected to single or multiple TPS Networks using Network

 Devices can be added to, or removed from the UCN to adjust to

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

provides the I/O interface to field devices

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

Information concerning the process, such as status and

The Network Interface Module provides the protocol

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

 Channels UCN events to the TPS Network for alarming

Synchronizes TPS Network and UCN time

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

It stores process and system information that can be displayed

History Module can store:

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

The number of History Modules needed for a specific system varies

Up to 20 History Modules can be configured on a Local Control

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

A History Module (HM) is structured in volumes and directories

• Each volume can have up to 63 directories and up to 9995 files

History Modules (HM) Volume Assignments and Sizes

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

• Directories can contain one or more files.

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

All volume and directory names are unique in an LCN

Some volume and directory names represent specific node pairs on

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

 A volume often contains several directories (Directories are

A directory usually contains a

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE

A pathname is simply a description of the location of a file. That

While directories are subdivisions of volumes, pathnames can include

SARAS RICERCHE E TECNOLOGIE – HONEYWELL DCS TRAINING COURSE