FAST/TOOLS

Product Overview
 FAST/TOOLS
Product Overview

© Yokogawa ISS

FAST/TOOLS is a registered mark of Yokogawa Industrial Safety Systems. All other brand or product names are trademarks of
their respective owners.
Information in this document is subject to change without notice and does not represent a commitment on the part of Yokogawa
1 Industrial Safety Systems.
 Table of contents

Chapter 1 Executive Summary 4

Chapter 2 Introduction 5
Chapter 3 FAST to Succes 6
3.1 Scalable Client/server architecture 6
3.2 Availability 8
3.3 Performance 8
3.4 Redundancy 8
3.5 Security 9
3.6 Web Enable 9
Chapter 4 FAST/TOOLS Concept 10
4.1 FAST/TOOLS internal structure 10
4.2 Operator actions log 11
4.2.1 Configuring the audit trail 11
4.2.2 Retrieval of information 11
4.3 Communication with IO-devices 11
4.3.1 Scan- or event based data acquisition and I/O handling 12
4.3.2 Adding a new I/O-driver 12
4.3.3 Standard supported communication protocols 13
4.4 Alarming 13
4.4.1 Alarm presentation 13
4.4.2 Historical presentation of alarms 14
4.4.3 Filtering of alarms 14
4.4.4 Sequence of Event recording 15
4.4.5 Printing of alarms 15
4.4.6 Alarm reports 15
4.4.7 Audible alarming 15
4.4.8 Alarm handling by pager and/or SMS 15
4.5 Specifics of ALARM/FAST 15
4.5.1 Acknowleding of alarms 16
4.5.2 Acknowledge sequences 16
4.5.3 Delayed alarms 16
4.5.4 Repeated alarms 17
4.5.5 Alarm collections 17
4.5.6 First alarm annunciation 18
4.5.7 Operating System alarms 18
4.5.8 Jump on alarm 18
4.5.9 Re-routing of alarms 18
4.5.10 Time scheduled routing of alarming 18
4.5.11 Change of priority 18
4.6 Object Oriented Engineering 19
4.6.1 Configuration of the process model in the SCADA system 19
4.6.2 Configuration of the process display in the SCADA system 19
4.6.3 Configuring classes and objects 19
4.6.4 Triggering objects 20
4.6.5 Distributed Object Execution 20
4.6.6 PROCESS/FAST language 20
4.7 Reporting 21
4.7.1 Some unique features of REPORT/FAST 21
4.8 Data Analysis 21
4.9 Data Archiving 22
4.10 Operator Controls 22
4.11 Trending 24
4.12 Connectivity 24
4.12.1 Data Set Services layer 24
4.12.2 DSS Application Programmers Interface 24
4.12.3 ODBC Interface 25

2
 Chapter 5 Configuration 26
5.1 The FAST/TOOLS Explorer 26
5.1.1 USER/FAST 26
5.2 Symbols 28
5.3 Diagnostic Tools 28
5.3.1 Equipment manager diagnostic tool 28
5.3.2 Internal data traffic diagnostic tool 29
5.3.3 Process variable related diagnostics 29
5.4 The FAST/TOOLS Setup File Editor 29
5.5 Application Specific data 30
5.5.1 Quickloading 30
5.6 FAST/TOOLS Online help 31
Chapter 6 Product support 32
6.1 Documentation 32
6.2 Training 32
6.2.1 FAST/TOOLS Process Operations 32
6.2.2 FAST/TOOLS System Management 32
6.2.3 FAST/TOOLS Architecture and Internal Structure 32
6.3 Consulting 32
6.4 Software licensing 33
Chapter 7 Technical Review 34

3
 1. Executive Summary

This document is designed to provide a

reader with an overview of the capabi-
lities and functionality of the
FAST/TOOLS software package. A
technical reader will gain an introduc-
tion of how the package is structured to
give the foundations for further rea-
ding. It gives the reader an apprecia-
tion of how a high performance, techni-
cally advanced package such as
FAST/TOOLS, can be implemented
easily with a minimum of engineering
effort.
It provides a summary of the software
functionality itself as well as of key
common implementations of applica-
tion independent software – such as
redundancy, web access and security.
Also there is an introduction to some of
the configuration, engineering and
diagnostic tools commonly used when
building applications. These tools are
used to speed up the engineering pro-
cess and to ensure the delivery of relia-
ble systems.
More application-oriented information
can be found in the various application
notes that are available. These notes
give examples of actual FAST/TOOLS
solutions in various industries and
locations around the world.
More detailed technical information
can be found both in the system manu-
als and in the on-line help functionality
of FAST/TOOLS itself.

4
 2. Introduction

The FAST/TOOLS package is a power- FAST/TOOLS provides solution possi-

ful, up-to-date, flexible, distributed ope-
rations information and control soft-
ware package. It is available in three
languages - English, French and
German
It is a leading system package for ope-
rations control and information integ-
ration with business systems and is
available on a wide range of industry
standard platforms.
FAST/TOOLS has been developed over
the past twenty years by combining our
expertise in Supervisory Control And
Data Acquisition (SCADA) with requi-
rements from users and industry
leaders.
Many industries and utility companies
with a need for data integration and
guaranteed data integrity use
FAST/TOOLS from Yokogawa in their
applications.
bilities in a wide range of control exe-
cution applications where, for example:
• Multiple Process Site environments
• PLC based control systems
• Wide area communication
• Closed loop control performed by
subsystems
• Relatively high content sequential
(logic) control
These characteristics are often seen in,
for example Oil & Gas production and
transport, infrastructure, utilities
monitoring and control and high per-
formance manufacturing applications
It also allows the flexibility of combi-
ning different types of systems to pro-
vide hybrid solutions, both on new and
existing sites (green and brown field
development).

FAST/TOOLS is successful in critical

applications due to its very stable
design, support of redundant and non-
stop systems and its very high performan-
ce on-line configuration possibilities.
These properties contribute to high
efficiency and high quality production
processes.

FAST/TOOLS has been developed with

a number of key issues in mind, one of
which is to provide a
system that can start small and which
can easily grow with client needs, both
in the short and long term.
This philosophy guarantees against
premature obsolescence. The commit-
ment to be a hardware independent
supplier means commitments to stan-
dard operating systems, standard
network protocols, standard user inter-
faces and standard software develop-
ment tools.

5
 3. FAST to Success

A thumbnail view of FAST/TOOLS: (figure 3.2) client/ server and front-end architecture

3.1 Scalable Client/server

architecture
FAST/TOOLS has a true client/server
architecture, not limited to stand-alone
stations, and allowing distributed func-
tionality. Front-end nodes give the pos-
sibility to reduce the load of the host by
pre-processing data on remote locations
and passing through only relevant
data. Configuration of these stations is
done on the host system (server) and
the configuration is automatically sent
to the front-end. There is no need for
the engineer to visit the remote host.
Host or front-end systems can run one
or more I/O-drivers per node, e.g. a
configuration could be an application
running up to 70 I/O-drivers at the
same time on one node, with e.g. only (figure 3.3) client/server architecture
three telephone lines available to con-
nect to the 70 remote PLC devices.
Where system availability is a prime-
issue FAST/TOOLS can be configured
to run in a redundant configuration.
Several redundancy concepts are avai-
lable, illustrating the flexibility of
FAST/TOOLS.
Networking can be configured redun-
dantly eg, redundant networks
between server and clients and/or
between server and PLC’s or RTU’s.
Here are some examples
(figure 3.1) of architecture concepts
client/server we have realised.
architecture

FAST/TOOLS is built up around modu-

les. This means that you can configure
according to functionality (the modules)
you need. Other modules can be easily
added when your application expands.

6
 (figure 3.4)
FAST/TOOLS
modular
structure
Here are some features of
FAST/TOOLS:
• Multi-page alarming functionality
with sorting options based on priority
or time, adjustable
acknowledging/reset options, rerou-
ting of alarms, paging use for alar-
ming
• Object oriented engeneering; make
one class and use it as many times as
needed (objects)
• Object oriented graphics; no need to
update symbols separately, one
change in a symbol updates all copies
• Predefined trend-pages for most com-
mon trending configurations
• On-line editing (adding/removing) of
7 graphics, item (tag-) definitions,
reports, I/O-drivers
• Communication scheduling, based on
time or availability of communication
lines for distant PLC/RTU-stations
• Automatic data-archiving of histori-
cal data on tape and clean-up of disk-
space
• Unlimited I/O-count (the largest wor-
king system has over a million data-
base items). Up to 255 different I/O-
drivers can run in parallel on one
machine
• Open interfaces (OPC and ODBC)
e.g. used for reporting/ MIS-functio-
nality/Web-enabling
• Report distribution to remote loca-
tions
• Fine-tuning tools to optimise perfor-
 mance e.g. coping with bursts
• Communication links via traditional
copper wires, high-speed optical
fibers, radio or satellite
• Time synchronisation from GPS or
PLC/RTU including time distribution
to other nodes
3.2 Availability
FAST/TOOLS currently runs on UNIX
platforms like AIX, Solaris and HP-UX
and on Windows-NT/2000.
FAST/TOOLS has run on many plat-
forms over the years, with many sys-
tems still running on other platforms
and still being supported. Constant
attention is given to new operating sys-
tems that may be appropriate.
Availability can be increased but
depends on several factors.
Furthermore availability is not a single
issue, but can be graded from low to
high. FAST/TOOLS has corresponding
redundancy concepts that meet your
availability demands.
3.3 Performance
We have written FAST/TOOLS oursel-
ves making best use of in-house resour-
ces and best of market solutions and
over the last two decades. It has evolved
in a professional environment, used in
a wide range of utilities, process manu-
facturing and infrastructure industries.
It means FAST/TOOLS is optimised
for UNIX-platforms and the Windows
platforms. UNIX systems and Windows
NT/2000-system can co-operate without
problems. So, the best system concept
for your application is possible, e.g. a
UNIX server for availability and stabi-
lity in combination with Windows-
NT/2000 for the operator interface.
With the fine-tuning tools we can tune
the application for really FAST execu-
tion. For example, bandwidth restric-
tions in I/O-driver data transport can be
optimised for speed (which, in addition,
gives you low I/O-driver load on your
system).
3.4 Redundancy
FAST/TOOLS has outstanding redun-
8 dancy support. There is no single con-
cept that suits redundancy in all cases,
therefore we have several concepts that
suit your needs and budget.
Some aspects to bear in mind that in-
fluence the redundancy concept, are:
• Reading field devices. Does your field
device support a second channel to
read data from?
• Changing setpoints. Do setpoints
need to be updated on the redundant
system or is reading from the field
device, after switching over, good
enough?
• Decision rules; At which point does
your primary system need to switch
over to the redundant system and
when does it need to switch back?
• Decision ruler; Do you want to decide
to switch over (and back) or does the
system need to decide that? Be aware
that a manual switch-over has its
advantages.
• How are configuration changes done
and consistency maintained between
the primary and redundant system?
• Is your process critical? Perhaps a
cold standby with manual cable-
switchover is enough, which saves
money and is less complex.
• Perhaps you want to use the redun-
dant system to develop and test new
displays or other configurations.
• Do you want your redundant system
in the same room as the primary sys-
tem or somewhere in a different
geographical location because of phy-
sical security considerations. This
immediately influences interconnec-
tion aspects.
These are all things you have to take
into account when defining redundancy.
Redundancy improves availability, but
is on the other hand complex. Every
concept has its advantages and disad-
vantages. A good way to compare soft-
ware effort (read: complexity = costs)
against type of redundancy (see figure
3.5)
The following redundancy concepts are
supported:
A. Fault tolerant hardware
B. 100% parallel systems
C. <100% parallel systems
 (figure 3.5) redundancy versus software effort
3.6 Web Enable
Today web-technologies are
used more and more. Instead
of specific client programs,
simple Web browsers become a
user interface, an HMI, to an
application.

FAST/TOOLS is web-enabled,
which means that, for exam-
ple, the Microsoft Internet
D. Hot Standby Explorer or Netscape can be used as an
E. Warm Standby interface to the system.
F. Lukewarm Standby Security is used to control access to dis-
G. Cold Standby plays and limit the user’s ability to set
control points. There is no
3.5 Security FAST/TOOLS software required on the
Apart from the standard operating sys- user’s system, only a browser is needed.
tem login account, FAST/TOOLS has The System Managers interface en-
its own security mechanism. ables the System Manager to configure
You can define users who have privile- the FAST/TOOLS system and to create
ges ranging from view-only up to full the operator’s interface. The operator
system configuration. During a interface enables the operator to con-
FAST/TOOLS session in a single trol the process via the Web. The web-
FAST/TOOLS environment, several screen can be made screen filling, so
users with different privileges can all that no escape is possible to the opera-
have access to the application via user- ting system or other software.
name and password concur-
rently.
For controlling functions the
mechanism is that you define
‘process-areas’ for each type of
user (1 to 999). Per item you
define the process area (read:
user or group of users) it
should belong to. This privile-
ging mechanism prevents
operators from accidentally
operating equipment.
Key combinations can be bloc-
ked so that access to the
Windows-environment is
shielded off. The advantage of using the Web-tech-
Per user an initial start-up display can nology is that only one server system
be defined and if the user is allowed to has to be configured and clients are
do configuration the possibilities can be relatively cheap, which means low
limited. So, for example, for a certain engineering, maintenance and license
type of user you can set privileges to costs.
change the low and high alarm, but
exclude him from changing the Low-
Low and High-High limits.
Additionally, you can have all these
operator actions being logged on disk.
9
 4. FAST/TOOLS Concept
4.1 FAST/TOOLS internal
structure
FAST/TOOLS is built up of modules
that connect to the communication
data bus called BUS/FAST.
The real-time database is one of the
modules that connects to the internal
bus.
All FAST/TOOLS modules are event-
based and submit their events to the
bus.
The bus passes these events to modu-
les that are subscribed to these events.
(figure 4.1) This means that a running system nor-
FAST/TOOLS mally has a low CPU-load.
internal commu-
nication bus
A programmers support
library with ready-to-use func-
tions comes with FAST/TOOLS,
which emphasises its open structure.
With this library you are able to build
your own applications which connect
directly to the FAST/TOOLS data bus
and thus seamlessly integrates with
FAST/TOOLS. Diagnostic and debug-
ging tools are available to support this.
BUS/FAST connects over Ethernet,
X25, serial-line or wireless radio to other
FAST/TOOLS systems or your applica-
tion, meaning that the transport medium
is transparent for the FAST/TOOLS
10 system and your application.
Besides data exchange, BUS/FAST pro-
vides time synchronisation, routing of
events and re-routing on time-out.
The minimal configuration of a
FAST/TOOLS system comprises the
following modules:
• BUS/FAST
• ITEM/FAST (module that manages
the real-time database)
• DATABASE/FAST (module that
manages all item/history/alarm
definitions)
• EQUIPMENT/FAST (module that
manages all I/O-driver actions)
Additionally other modules can connect
to the bus in order to enhance the func-
tionality of FAST/TOOLS:
• ALARM/FAST (the module that
handles all alarming functions)
• HISTORY/FAST (the module that
takes care of saving item data,
alarms, reports, audit data)
• AUDIT/FAST (the module that
manages audit definitions and the
data to be audited)
• PROCESS/FAST (the module that
allows object oriented engineering of
tasks)
• REPORT/FAST (the module that
manages all report definitions and
generations)
• ACCESS/FAST (the module that
manages the ODBC/OPC interface)
• USER/FAST (the module that sup-
plies the configuration and operator
interface to the user)
 4.2 Operator actions log
Some configuration changes or control
actions can greatly influence the beha-
viour of the system that is being con-
trolled and monitored. It must be possi-
ble to retrieve this type of information
afterwards to be able to trace the cause
of problems or to be able to improve
operational procedures. AUDIT/FAST
offers the possibility to define in a flexi-
ble way the events that must be stored,
together with information like:
• Who?
• The operator name or the application
program making the change
• Where?
From which location was the change
invoked
• When?
The date and time that the change
took place
• What?
The detail of what was changed, the
old and new value if applicable
• Why?
An operator can add additional text
for explanation
Examples of actions that may be logged:
• Change of setpoints
• Change of alarm limits
• Acknowledgement of alarms
• Opening/Closing valves
• Login/logout actions (successful and
not successful)
All these events may be logged and
retrieved locally, but may also be
distributed to other nodes on the
network for example the workstation
of the system engineer.
4.2.1 Configuring the audit trail
In fact, any event in the SCADA sys-
tem could be trailed, from a simple
item set point change to the change of
a system configuration file. The mecha-
nisms to do so have been implemented
throughout the FAST/TOOLS software
modules. Even your own application
programs can report their own events
to AUDIT/FAST to log events genera-
ted by these programs.
11 The system manager configures
AUDIT/FAST using "event selection"
from the configuration menus. So only
relevant information is trailed to make
optimal use of system resources.
The events to be logged are defined
using "event classifications". A basic set
of event classifiers is provided as stan-
dard. In addition, the system manager
can define his own event classifiers.
4.2.2 Retrieval of information
To support selective retrieval of
AUDIT/FAST information, the system
manager defines a selection group.
This selection group has its own selec-
tion group criteria allowing him to
filter which events to see.
The information stored in the database
can be retrieved and presented on an
operator display or in a report via
REPORT/FAST. In the display the ope-
rator can filter audit trail information
to select particular information.
4.3 Communication with
I/O-devices
The part of FAST/TOOLS that takes
care of communication with I/O devi-
ces, like RTU’s, distributed I/O, and
PLC’s, is called EQUIPMENT/FAST.
It uses device specific I/O-drivers, polls
the equipment and updates the real-
time database. However, it has featu-
res that go beyond the traditional way
of data collection. For example:
• It processes timestamping coming
from your equipment (giving correct
alarming order in alarm overviews).
• An EQUIPMENT/FAST I/O-driver
can be configured to be time-master
or time-slave for your equipment.
• Up to 255 different I/O-drivers can
run at the same time on one
FAST/TOOLS host.
• A special I/O-driver is available for
GPS-time-synchronisation.
• Modem scheduling is available for
equipment at distant locations. You
can use this to poll, for example, 70
devices while you only have three
modems available. One emergency
call-in modem connection is available.
• Event based data handling. Devices
may initiate the data exchange with
 an I/O-driver.
• History collection is supported. If
your (distant) device is able to build
up history when it is unable to com-
municate with the host because of
line disturbances, this history can be
collected after reconnection and mer-
ged into the existing history files.
• Predictable (pre-settable) behavior on
loss of communication. For example
Ethernet is the preferred line (fast
communications). The serial line
takes over and switches back upon
(figure 4.2)
Redundant
serial line
recovery of the preferred line.
• Predictable (pre-settable) behavior
after restorion of connection (for
example, do a ‘total scan’ first to
update the real-time database with
latest data).
• Pre-settable behavior on
fast toggling bits (due to
a faulty transmitter for
example) and fast chan-
ging analogue values.
• On-line insertion of items
(tags), on-line adding of
I/O-drivers without stop-
ping FAST/TOOLS.
• Per I/O-driver the status
of primary and redun-
dant line is available via
items. This is useful for
12 display in alarm over-
views for example.
While the FAST/TOOLS I/O-drivers are
transport-layer driven, the connection
layer may vary from serial line via
optic-fiber, radio-communications to
Ethernet connections.
4.3.1 Scan- or event based data
acquisition and I/O handling
EQUIPMENT/FAST has extensive
capabilities in the scheduling of the
scanning of external signals. Either
external signals will be scanned at
regular intervals or unsolicited exter-
nal signals are handled. When the
external signals are scanned, the scan
intervals may differ for each process
variable, even if they stem from the
same equipment. The SCADA system
will process events in the order in
which they occur.
4.3.2 Adding a new I/O-driver
While your SCADA system is up and
running, extensions can be made. New
I/O drivers, called stations, can be
added on-line without stopping the
SCADA software.
Once the station is defined, items can
be created on-line and connected to I/O
points in the station. Some of the para-
meters available for I/O related items
are:
• Address of the item (this may be a
real address but also a logical name)
• Direction of the communication (from
station, to station or both directions)
 • Scanning method (scan based, event
based)
• Conversion method (linear conver-
sion, boolean, BCD, floating point,
etc.)
• Input filtering (protect against too
rapidly changing analogs and digitals)
4.3.3 Standard supported commu-
nication protocols
The following is a list of some of the
standard protocols for PLC’s, RTU’s
and telemetry systems that are suppor-
ted by FAST/TOOLS (alphabetic):
• Allen Bradley PLC (SCL503)
• ABB ANSI
• ABB Areadat
• Bristol Babcock BSAP
• Datawatt D01
• GE-Fanuc S90
• Honeywell DCC Exel
• IEC 870-5-101
• J-Bus
• ModBus RTU
• Modicon Quantum Series
• Moore QuadLog
• OMRON Sysmac (serial)
• OMRON Sysmac FINS (Ethernet)
• Sattcontrol COMLI
• Siemens 3964R (serial)
• Siemens SINAUT ST1, IEC 870-5
• Siemens SINEC H1-AP (Ethernet)
• Siemens SINEC H1-htb (Ethernet)
• Triconex NCD (Ethernet)
• Yokogawa DAQstation
• Yokogawa ProSafe-PLC
• Yokogawa ProSafe-SER
• Yokogawa ProSafe-SLS
When a particular commu-
nications protocol that you
require is not listed here,
please contact Yokogawa
ISS or your FAST/TOOLS
representative. Also it is
possible to build custom
specific equipment
driver(s).
13
4.4 Alarming
One of the important aspects in
Supervisory Control systems is alar-
ming. In this section we will show you
the sophisticated way FAST/TOOLS
processes alarms. ALARM/FAST is the
tool that handles alarming in
FAST/TOOLS.
This section describes first of all the
way alarms are presented to the user
and secondly some unique features of
alarming which are typical for
ALARM/FAST.
Alarms must be distinguished from
events. In FAST/TOOLS, events are
alarms with no alarm functionality.
That is, they are not acknowledged or
reset but appear in a historical over-
view and have the same configuration
possibilities as alarms.
4.4.1 Alarm presentation
ALARM/FAST allows alarms to be pre-
sented on a number of different devi-
ces, like:
• Workstations
• Printers
• Paging systems (pagers, SMS, tele-
phone)
• Accoustic devices (horns)
On workstations the alarm presentation
will, in most cases, be a screen with
lines of text (the alarms) containing
significant information for the operator.
Additionally, graphical objects to which
the alarms apply, can be configured to
 change colour, shape, position etc.
In ALARM/FAST the alarm informa-
tion can be customised for each device.
Generally speaking the alarm text line
will contain information regarding:
• Alarm priority (0-15)
• Alarm status (Alarm, Event,
Acknowledged, reset, normal, etc)
• Date and time of the alarm (genera-
ted by FAST/TOOLS or via the time-
stamp received from the PLC or
RTU, down to milliseconds)
• Item name, -value, -description and
alarm description
• Alarm status text (Low, Low-Low,
High, High-High, normal, under-
range, overrange, offline, blocked, etc.)
Alarms are presented in two ways:
• Dynamically on display and/or prin-
ter (current alarms)
• Historical (chronological in time) on
display and/or printer
Historical alarms can be archived on
disk or tape.
4.4.1.1 Dynamic presentation of
alarms
Current alarms are presented in a
separate current alarm display or in,
for example, a three line banner at the
bottom of the page. This overview is
dynamic by nature; if an alarm no
longer exists and is acknowledged
(manually or automatically) then the
alarm disappears from the screen.
If there are no alarms active,
this display or banner is
empty.
Current alarms can be sorted
in:
• Priority base order
• Time base order
Alarm line layout configura-
tion:
• Colour presentation
Every alarm status (Alarm,
acknowledged alarm, repe-
ated alarm, delayed alarm,
normal, etc) can have its
own distinct fore and
background colour or no
14 background colour.
• Format of the alarm line
The format of the alarm line can be
freely defined
• Scrolling
Scrolling through the historical
alarms can be done:
• Per alarm line (up/down)
• Per display page (up/down)
• Go to top/bottom
4.4.2 Historical presentation of
alarms
Every current alarm and its progress
over time (acknowledge, reset, normal)
is logged in historical log-files which
are shown in the historical displays.
4.4.3 Filtering of alarms
A lot of filtering types do allow to
filter alarms on-line in current- and
historical alarm displays.
For example, alarms can be subscribed
to up to 16 Areas-of-Interest (i.e. field
devices or installations). The alarm dis-
plays filter on this ‘Area-of-Interest’ In
addition, special items (or group of
items) can be left out from display.
Filtering can be maked user dependent.
If user one logs in he gets ‘his’ alarms,
if user two logs in he sees the alarms
that ‘belong’ to him.
The presentation of historical alarms
can, but need not, be the same as for
the current alarms.
 4.4.4 Sequence Of Event recording
Both current and historical alarm dis-
plays allow the display of Sequence Of
Event data coming from specialised
equipment that is able to record and
time-stamp events. Data is shown in
the right time-stamped order with a
resolution down to millisecond if the
equipment supplies that resolution.
Alarm lines can have colour- and line
formatting specific for this purpose.
Events are different from alarms and
should be shown separately.
4.4.5 Printing of alarms
Alarms can be directed to a printer. A
printer allows alarms to be printed on
a per alarm base. The format of the
alarm line to be printed can be set
independent from the format used in
the current- or historical alarm dis-
plays. Alarms can be printed with a
header per page or as one long list.
4.4.6 Alarm reports
Reports can be made of current and
historical alarms including filtering. In
addition, reports can be defined that
will print-out alarms that meet special
criteria. For example, a report can be
made that prints all alarms one minute
before a trip up till two minutes after
the trip. Hence, the trip itself can trig-
ger the report, not knowing in advance
which tag caused the trip.
4.4.7 Audible alarming
A separate process takes care of audi-
ble alarming. Audible alarming can be
done by:
• playing sound files (e.g. wav-files).
These files can be standard horn-sig-
nals or tailor made to represent for
example spoken text or to distinguish
alarms from other acoustic signals in
the control room.
• Re-routing the audible alarm signal
to the RTU/PLC, which on its turn
activates a horn.
A setup file is used to define which
situations (items) subscribe to this
audible alarming process.
15 Individual items can subscribe but also
a status item that represent a group of
alarms. If one of the items in this
group goes into alarm, regardless
which one, the audible alarm will go off.
More than one group can subscribe.
4.4.8 Alarm handling by pager and
or SMS
Maintenance engineers can be notified
of alarms by means of a pager or SMS.
An escalation mechanism is used to
determine which engineer is to be cal-
led if the previous one doesn’t answer.
Different telephone numbers can be
inserted in this table, or an interface
with a database to retrieve information
like; who is responsible for the alarm,
telephone numbers of the maintenance
personal, maintenance follow up etc.
4.5 Specifics of ALARM/FAST
The way alarms need to be handled by
the operator depends on a variety of
factors, mostly determined by customer
specific alarm procedures. The follo-
wing summary lists the features
ALARM/FAST supports.
• Alarm acknowledgement. Some
alarms require acknowledgement,
others don’t (manual/automatic).
• Sometimes, for example, at starting
up a process, it is known that certain
alarms will be raised which should
then be suppressed (delayed).
• Repeating alarms. If alarms are not
acknowledged within a time limit a
repeat can be set on these alarms.
• Alarms can be grouped. One ‘overall’
item represents this group.
Acknowledging this item acknowled-
ges this group. Resetting this item
resets the group.
• First up alarming for cases where the
user is interested in the item that
caused the first alarm within a group
of alarms.
• First –out alarming for which the
first alarm within a group suppresses
successive alarms.
• For fast access to displays the opera-
tor can click on the alarm line. This
makes the current display switch
immediately to the display the tag
belongs to.
 • Re-routing of alarms to another
workstation if alarms are not ack-
nowledged within a time limit
• Re-routing of alarms after workday-
hours.
• Filtering is used if the operator is
interested in alarms coming from a
particular process-area.
• Dynamic priority: Priority changes
when alarms last for a certain time
or are not acknowledged within a cer-
tain time.
Some of the features are
Status
described below in more
Underrange
detail. Low
Low-Low
4.5.1 Acknowledging of Normal
alarms High-High
Blocked
The Current Alarm
Overrange
Overview allows the opera- Offline
tor to manually acknowled-
ge alarms.
He can acknowledge:
• Individual alarms by
clicking on the particular alarm line
• Acknowledge alarms per group of
alarms (See paragraph
Alarm collections 4.5.5)
• A function key
• The Acknowledge-All but-
ton in the current alarm display
Apart from manual acknowledging it is
possible to automatically acknowledge
alarms. For this purpose there are two
possibilities:
• Automatic (system)
Acknowledgement
The alarm (or alarm group) is auto-
matically acknowledged by
FAST/TOOLS itself.
This feature can be used
to distinguish events or
‘silent-alarms’ from
alarms.
• Process
Acknowledgement
The changing of the value
of an item can be defined
as the acknowledgement
mechanism.
16
4.5.2 Acknowledge sequences
All field I/O-signals that are configured
for alarming can have a status (High-
High, High, Low etc). You decide the
alarm annunciation for that status. For
example a low-alarming can be shown
on the alarm screen for which no ack-
nowledging is required, while Low-Low
requires acknowledging.
The following table shows some of the
possible statuses (for specialised purpo-
ses other statuses can be desired by
users):
Comment
For example, if signal < 4 mA (open connection)
Can be an alarm state too!
Item blocked by the system engineer
Ex. > 20 mA (Short circuit)
Communication loss with RTU, PLC
ALARM/FAST uses ‘alarm-states’ for
defining the alarm annunciation if the
alarm status changes from one (alarm-)
status to another:
N No Alarm
A1 Alarm state 1
A2 Alarm state 2
A3 Alarm state 3
The following figure shows the relation
between states and the status of an
alarm signal.
In addition to these states an acknow-
ledgement table is used that defines
how acknowledgement takes places if a
signal (to be more precise, its status)
goes from one state to the next state.
(figure 4.3) relation between states and the status
of an alarm signal
You define whether alarms are acknow-
ledged manually or automatically.
 The following acknowledgment types
are defined:
• Automatic
The alarm is automatically acknow-
ledged by the FAST/TOOLS system
• Manual
The alarm has to be acknowledged by
the operator
Next state
Current state N A1
Nack A A
Nnack A A
A1ack A A
A1nack A A
A2ack A A
A2nack A A
For example, if the current status of
the signal is High and not acknowled-
ged (A1nack) it will automatically be
acknowledged if it goes to Normal (N).
However, it must manually be acknow-
ledged if the next state is A2.
Now it is possible to give each alarm
item its own acknowledgment matrix.
The advantage of using this way of
defining alarm acknowledging is its
flexibility. For example items (or groups
of items) that normally don’t require
acknowledging and that go off-line or
become under- or overranged now
require attention of the operator and
need acknowledging.
4.5.3 Delayed alarms
Quite often, it is desired that, although
the item is in alarm, alarming itself
should be delayed because it is known,
for example when starting up a system.
If after a certain time the item is still
in alarm, alarming should take place
but if the alarm state changes back to
normal during that period no alarm
must be raised. Therefore an alarm
delay time can be set by the system
manager.
(figure 4.4) Delayed alarms
17
4.5.4 Repeated alarms
Sometimes it is desired to repeat an
alarm if the alarm state continues to
exist after the operator has acknowled-
ged it. A so called repeat alarm can be
defined for this situation. The repeat
time can be configured by the system
manager. The repeated alarm can be
given a separate colour.
A2 (Figure 4.5) Repeated alarms
M
M
M
M
M
M
4.5.5 Alarm collections
Items that are logically related to each
other can be grouped into an Alarm-col-
lection group representing a distinguis-
hable unit, area or field device.
This group has its own status-item
representing that group (see figure 4.6).
Acknowledging this status-item ack-
nowledges the group. In addition, this
item can be used to reset the group
(freeing the unit, area or field device).
If one of the items in the group goes
into alarm the group goes into alarm,
regardless of successive alarms in this
group. Additional alarms after acknow-
ledging the group make the group go
into alarm again (flashing on the cur-
rent alarm screen, for example).
The status-item shows the alarm sta-
tus of the group and can be connected
to a graphical object. For example, in a
range of area-buttons on a topview-
page an area-button can be coloured
red if one of the items in this group
goes into alarm, indicating to the ope-
rator there is something wrong in this
area. Clicking on the button will bring
up the area display.
This status item itself can be displayed
in the alarm overview to show the sta-
tus of the group, area or field-device.

(figure 4.6)
Alarm collections
4.5.6 First alarm annunciation
In many situations, an alarm in a pro-
cess results in a large number of deri-
ved alarms and it will not be clear from
the alarm list what caused the fault
(read: which alarm was first).
ALARM/FAST has two standard possi-
bilities to filter the alarms for the ope-
rator, first-out and first-up.
4.5.6.1 First-out
The first-out function enables alarms
that come after the first alarm to be
suppressed to prevent a ‘snowball’
effect. Only the first-out alarm is
shown in the alarm display. In addition
First-out groups can be organised in a
hierarchical structure with parent and
child relations - the behaviour of the
child first-out group being controlled by
its parents.
This feature can be used, for example,
to prevent one device to make subse-
quent devices, which have their own
First-out alarm group, go into alarm.
4.5.6.2 First-up
The first-up function offers the possibi-
lity to separate the item that caused
the first alarm in the group from all
(subsequent) other alarms in the group.
This function allows these presentation
opportunities:
• The actual alarm that first caused
the alarm collection group to go into
alarm. Additionally this first-up item
can be given a special colour and pri-
ority, that makes it easy for the ope-
18 rator to distinguish the first-up alarm
from all others.
• The first-up status-item. In the cur-
rent alarm overview this item can be
displayed until all alarms in the
alarm collection have been acknow-
ledged (and reset if this option is set).
This status item can also be used to
colour a graphical object showing the
status of an area, a unit, a zone or
item of equipment.
Alarm collections can be assigned an
acknowledgement type as mentioned in
paragraph 4.5.2.
4.5.7 Operating System alarms
ALARM/FAST allows to direct system
messages coming from your operating
system to the alarm overview or prin-
ter. For example, a pre-alarm can be
set on percentage of disk-usage.
Crossing this limit will generate the
pre-alarm in the alarm screens.
4.5.8 Jump on alarm
For fast access an operator need not
find out on which screen the item is
that is in alarm. When he sees an
alarm popping up in the three line
alarm banner or the current alarm
overview, he can right-click on the
alarm line in alarm. This will bring
directly the screen up with the item it
associated with, showing him the actu-
al situation. This feature can be confi-
gured on a per item basis.
4.5.9 Rerouting of alarms
If alarms are not acknowledged within
a certain time they can be rerouted to
another destination.
4.5.10 Time scheduled routing of
alarming
If at the end of the workday the opera-
tors leave the office, alarms can be
scheduled in time to re-route to anot-
her destination.
4.5.11 Change of priority
Alarms that are not acknowledged
within a certain time limit can be con-
figured to change to a higher priority.
This priority change can, for example,
 be coupled to rerouting or acoustic
alarming.
4.6 Object Oriented
Engineering
PROCESS/FAST is used as the Object
Oriented Programming tool to add user
defined functions in the FAST/TOOLS
environment. These can be very simple
like summing the value of two tags and
putting the result in a third tag up to a
full set of flow calculations or a func-
tion which describes the behavior of a
pump. A function can to be defined
once (called a class) and used multiple
times (called objects).
(figure 4.7)
relation
between Class
and Object
With PROCESS/FAST your are able to:
• Shorten the configuration time of the
SCADA environment because functio-
nality is defined once as a class and
is automatically available in all deri-
ved objects.
• Create alarms that only a
program can detect via calcu-
lations or logic and let these
alarms appear in alarm dis-
plays thereby notifying the
operator of special conditions.
• Shorten the configuration
time of the SCADA environ-
ment because the SCADA
19 system is configured on a
functional level rather than on a tag
by tag basis.
• Apply global functional changes easi-
ly by changing the class. After a class
reset all derived objects will have the
new functionality.
• Program functions in an easy to learn
PROCESS/FAST language.
• Automatically create and remove tags
related to an object.
4.6.1 Configuration of the process
model in the SCADA system
With PROCESS/FAST it is possible to
configure the SCADA system on a func-
tional level using functional building
blocks rather than configuring each
individual I/O tag. Consider the follo-
wing example of a valve class:
Derive an object from this class, define
the valve specific parameters like name
and location and the related tags are
automatically created. When removing
the valve object the related tags are
also automatically removed.
4.6.2 Configuration of the process
display in the SCADA system
The mechanism of classes and objects
gets even more powerful when coupling
a class to a graphical representation
(called a symbol). Copies of this combi-
nation can be used as many times as
wanted in process displays. In this way
the SCADA system for both the process
model and the graphical representation
i.e. process displays on a functional
level is made.
4.6.3 Configuring classes and
objects
A class is configured using the
USER/FAST Explorer:
 A class is programmed with an easy to
learn PROCESS/FAST language. The
colour sensitive editor provides easy
recognition and prevents you from
making syntax errors.
Like a class an object is configured
using the USER/FAST Explorer:
An object can be assigned a priority to
ensure that objects with higher priority
are executed first.
Objects and classes can be loaded
manually (as shown above) or loaded
via the quickload mechanism (see
chapter 5.5.1).
20
4.6.4 Triggering objects
Objects are activated by triggering
them. Triggering is done:
• Periodically on a time basis, for exa-
mple to calculate an average value
every ten minutes
• On event basis: for example on a tag
value change or status change or a
time out
• Mix of the above
Assigning a trigger group is done via
the USER/FAST Explorer:
4.6.5 Distributed Object Execution
To balance the load of all the objects
they can be distributed over more then
one FAST/TOOLS node. When defining
the object you have to specify where
the object is to be executed: either on
the server node (default) or on a front
end node.
4.6.6 PROCESS/FAST language
A class is programmed with the
PROCESS/FAST language.
This language contains all functions
you can expect from a high level langu-
age. In case a function is not available
own functions either in the PROCESS/
FAST language itself or in a C-function
can be added.
The PROCESS/FAST language con-
tains the following functionality:
• Arithmic operators
• Bitwise operators
• Boolean operators
• Relational operators
 • String operators
• Transitional operators
• Functions like ABS(), SIN(), SQRT(),
etc…
The transitional operators are used to
detect e.g. the first time a value crosses
a limit and start appropriate actions
like shutting down an inlet valve.
4.7 Reporting
REPORT/FAST is the tool for generating
reports of configuration , alarming,
actual or historical data.
REPORT/FAST enables to generate
reports:
• Scheduled on time base (e.g. daily
production or shift reports, or every
first day of the month)
• On an event (item-change, e.g. to
make a report of prior- and post shut-
down events)
• On ad-hoc base
• By pushing a button and start a pre-
defined report (e.g. a current alarm
report)
• By on-line defining a new report and
start generating it immediately (for
example, to show all analog items
with their physical high and low limit
values)
Reports are shown on screen, printed
on a report printer or saved to disk
(and can be scheduled to be deleted
after the lifetime has expired). Reports
on disk are in readable ASCII-format.
Any text editor to view, edit and print
these reports can be used.
4.7.1 Some unique features of
REPORT/FAST
REPORT/FAST uses an SQL dialect to
generate reports, but has a lot more
features than just that.
For example:
• The report layout (margins, header,
footer, paper size) can be defined on a
per report base
• Reports can be assigned a priority
When more than one report is sche-
duled for generation at the same
time, the order in which they are
generated depends on their priority
21 (0 – 9).
• Data to be retrieved for the report
can be input for:
• Arithmetic operations (calcula-
ting averages for example).
• Functions for special purposes,
e.g. production per shift or running
hours of a pump.
• In a report conditions (based on
calculations for example) which upda-
te the value of an item or its status
can be defined.
• Reports can be routed to other desti-
nations
For example. A report on a daily basis
to a remote office it can be sent via
local telephone lines to this destina-
tion. Or it can be rerouted when a prin-
ter went off-line due to e.g. ‘out-of-
paper’.
4.8 Data Analysis
Standard functions for data-analysis
and presentation are available in
FAST/TOOLS. In addition you can use
PROCESS/FAST, the object oriented
programming language of
FAST/TOOLS, to create specific calcu-
lations.
The standard presentation of data
includes a range of charts to display
and analyse the data.
In addition a range of built-in functions
available in PROCESS/FAST can be
used for data-analysis or statistical
process control.
But statistical analysis is not restricted
to the graphical environment only.
REPORT/FAST has a lot of statistical
functions available that can be used in

(periodical) reports, like Count, Sum,
Avg, Max (of a range of values), Min,
StdDev, Variance, etc.
For example, an application required a
flow calculation program that calcula-
tes the position of individual valves
based upon the throughput of a main
valve. This main valve is controlled via
the total of the individual flow relative
to by the individual valves. Positions of
these valves are based on complex sta-
tistical formulas.
4.9 Data Archiving
FAST/TOOLS supports storing data on
disk with the lifetime you think is ade-
quate. Data is kept on disk to be avai-
lable for on-line trending or historical
alarm displays with a storage life time
that can range from hours up to weeks
or even years.
In addition there is the possibility to
transfer relevant historical data to tape.
The reasons why data is kept on tape
could be:
• Predict disk usage. After the specified
time, historical data will be moved to
tape, preventing the disk becoming
full. For example historical data will
be moved to tape when it is 30 days
old. So every new day the 30-days-
ago day is moved to tape and remo-
ved from disk.
• Offline statistical analyses of data
over longer time periods in order to
find trends in production parameters
or defects
• Offline processing of data for mainte-
nance purposes
• Statutory or fiscal traceability rea-
sons may force the user to keep rele-
vant data available for several years
in order to clarify responsibility
Data can be stored on tape:
• Manually, on an ad-hoc basis
• Automatically, done by the schedu-
ling mechanism of the tape archiving
process. In most cases automatically
tape archiving is time based.
• For incidental manual storage of
data, you can take out the tape for
automatic storage, store the data,and
22 put the automatic tape back
(figure 4.8)
FAST/TOOLS keeps record
of all the data that is stored on
tape. It shows a list of all tapes that
have been used up till now. To restore
data the name of the tape to insert into
the tape drive after specifying the start-
and end-date of data to be restored will
been shown.
In addition the type of data to restore
can be selected. This could be, for
example, analog data only for trending
in the past.
Both actual and restored data can exist
on the same system.
4.10 Operator Controls
Supervisory Control Systems must be
able, as the term implies, to apply con-
trol to the process it monitors. These
systems normally apply Control on two
levels: on the SCADA dataprocessing
level and on the HMI level.
On the HMI level, FAST/TOOLS has
graphical operator controls that range
from simple buttons, via sliders up to
complete faceplates. See the examples.
Many animation features of
FAST/TOOLS are available to extend
the dynamic behavior.
If these predefined controls don’t suit
what is want own controls can be made.
Because the graphic part of
FAST/TOOLS is object oriented, you
make a control symbol once and use it
many times. ‘Behind’ the graphical con-
trol can be added programming logic to
give the symbol a specific behavior.
 button which starts the application
be defined.
• Network status can be imported in
displays. This allows the operator to
warn system engineers about commu-
nication problems.

Accessing the operating system from

the displays can be blocked for opera-
tors, but allowed for the System-
Engineer.

Here are a few examples of how to defi-

ne controls:
• Clicking on a symbol pops-up a con-
trol display that shows e.g. valve sta-
tus information and valve control
buttons. The control pop-up may
block other display actions.
The pop-up is used for all symbols of
the same type.
• A function key pops-up an info dis-
play showing specific data of a tag or
e.g. production data
• It can be decided how operators chan-
ge process values in the display: text
entry, predefined values, via a slider
or with up-down keys. In addition a
‘bumpless’ process value change can
be made when switching over from
manual to automatic mode or back.
• The alarm line can be provided with
a ‘jump-on-alarm’-function. Clicking
on the active alarms makes the
screen switch over directly to the dis-
play where the tag in alarm belongs.
This fast access means avoiding time
consuming searching for the right
display.
• When working with more
than one client station, you
can block symbols on other
displays if an operator has
activated the one on his
display. This prevents mul-
tiple operators from con-
trolling the same device.
• Assign system functions to
buttons on the screen. For
example if a text editor
must be available in the
23 SCADA application a
 4.11 Trending
FAST/TOOLS has an extensive library
of ready-to-use trend templates. You
only have to couple the item to the pen
and the trend is ready to run. Besides
the trend templates you can make your
own trends or adjust the trends from
the library.
The two types of trends in
FAST/TOOLS are:
• Real-time trends
• Historical trends. Even ‘old’ data res-
tored from tape archives can be trended
Some parameters you can set for a trend:
• The pen appearance (continuous line,
dashed line, points)
• Start-time and stop-time (can be
changed on-the-fly)
• Min and Max scaling value of the
process variable that is trended
• The process variable to connect to a
pen
• Starting and stopping the trending-
process
• The number of samples to show on
the display
• A hairline can be activated to read
value and time at a sampled point
• The sampling rate with which the
trend screen is updated
• Different time scales by varying
start- and end-time
The trending features of
FAST/TOOLS also allow make an X/Y-
plot.
Up to ten process variables can be plot-
ted against another variable.
24
4.12 Connectivity
FAST/TOOLS has an open interface to
connect to 3rd party products like
management information systems,
batch tracking and leak detection sys-
tems, etc. This open interface is based
on the FAST/TOOLS Data Set Services
(DSS) layer. On top of the DSS layer
the following industry standard inter-
face protocols are available:
• ODBC
• OPC
Beside these industry standard interfaces
your own client can be edit via the easy
to learn Application Programmers
Interface (API) of the DSS layer. (This
interface could be programmed in for
example Visual Basic).
The FAST/TOOLS explorer used for
configuring the SCADA environment
also runs on this DSS layer.
4.12.1 Data Set Services layer
Via the DSS layer all configuration
data like tag definitions, alarm definitions,
(figure 4.9)
Data Set
Services layer
class definitions, etc. are accessible.
Data Set Services encapsulate
FAST/TOOLS databases allowing all
configuration data to be accessed via a
single interface.
4.12.2 DSS Application
Programmers Interface
To add a DSS client to FAST/TOOLS
the DSS Application Programmers
Interface is available. Via a simple set of
routines access to most of the
FAST/TOOLS data stores is available.
The DSS API has the following functions
 is available:
• Retrieving information about Data
Set properties
• Synchronous I/O (read, write, update)
• Asynchronous I/O
• Notification when "something" changes
Each DSS client on top of the DSS
layer can be a relatively thin client
because the DSS layer takes care of the
most common data access problems.

4.12.3 ODBC interface

Integration of the FAST/TOOLS
SCADA system with other applications
like Enterprise Resource Planning sys-
tems, MS-Excel™ applications or
RDBMS applications can be done with
standard interfaces. Access to the
FAST/TOOLS system is provided via
Open Data Base Connectivity standard
‘ODBC’. The application can perform
SQL requests on all FAST/TOOLS
data. The data collected can be used in
reports, overviews, or stored in other
databases. Via ODBC data can be writ-
ten back to FAST/TOOLS. Not only
data but also for configuration data(e.g
add new items).
The ODBC interface enables you to
easily make reports in MS-Access™ or
overview in MS-Excel™, as shown in
the example below.

25
 5. Configuration

5.1 The FAST/TOOLS

right are the fill-in-the-blanks forms
Explorer
displayed. These are context sensitive.
The FAST/TOOLS Explorer gives you
For example, see figure above, if you
access to all configuration data of
select alarming for a tag an extra tab
FAST/TOOLS with the Windows look
will appear in the item-form. The navi-
& feel.
gate buttons at the bottom of the form
let you quickly walk through the list of
This environment, called USER/FAST, items.
runs on top of the FAST/TOOLS system.
It allows on-line editing of configuration
data like item definitions, alarm defini-
tions, displays, etc. The USER/FAST
environment can be used both for con-
figuring the application and creating
and modifying displays. From the
USER/FAST environment you can start
your displays and test the functionality
on-line and go-back while FAST/TOOLS
keeps running in the background.

5.1.1 USER/FAST
USER/FAST has the Windows look &
feel. Navigating through USER/FAST
looks very familiar and your way in
USER/FAST will be found intuitively.
On the left you find an explorer like
folder structure that brings you to all
26 the entities to be configured. On the
 Per Explorer entity context sensitive
functions are available, making editing
more easy. Additionally:
• Filter on items displayed using wild-
cards, block the items from scanning
the PLC, update the value of the
item, etc
• Update more than one entity at the
same time. For example: switch on
the audit trailing function for a num-
ber of items in one go
• A list of items to be examined with
their values and status can be made
• USER/FAST has the familiar drag
and drop features
• USER/FAST doesn’t need to run on
the server, but can run on clients too,
hence it can run on more clients at
the same time, allowing to work in
parallel
• When running USER/FAST on a
client you are able to configure the
server regardless if the server is
WIN2000 or UNIX based
Additionally, with USER/FAST make
reports on-line or archive to tape can
be done.
5.1.1.1 Configuration Editor
• With the Editor all items can be defi-
ned, I/O-driver configurations,
reports, graphics, etc. by hand using
USER/FAST, the graphical configura-
tion interface with FAST/TOOLS.
• Reports and configuration data
Developing the data separatly from the
FAST/TOOLS environment (offline)
means that you are able to do version
27 management on the data.
All configuration entities can be
Quickloaded. In addition, graphics (e.g.
templates) can be converted to readable
ASCII-files and processed by scripts in
order to generate additional graphics.
5.1.1.2 Graphical editor
The graphical editor, as part of
USER/FAST, is an easy to use editor.
All graphic displays and symbols are
sorted in folders in the Explorer.
Clicking on a display opens a window
that gives a preview of the display.
From this window the editor can be
started or activate the display and
have an on-line view on the process.
The scroll-buttons at the bottom let you
scroll through (and preview) the dis-
plays. Editing display actives the dra-
wing Toolbar. A few typical features
are:
• The properties window of the display
allow you make up a history of major
editing changes.
• Display actions can be blocked for the
operator when a popup is shown.
This feature prevents the operator
from opening more then on popup
window at the same time and thus
obscuring the view on the process.
• Popups for controlling for e.g. a valve,
can be blocked on other workstations
when it is active. This ensures that
only one operator at a time can con-
trol the valve.
• An extensive library of more than
3000 symbols including standardised
ISA-symbols, is available as well as
predefined displays (alarm displays,
trend displays).
• If you have images of your production
site or equipment, then they can be
inserted into the display and dressed
 up, for example, with tag-value indi-
cators.
• A range of chart types is available to
display process data in a statistical
way.
• You can create a display or symbol on
one node and distribute it to other
nodes, wherever that node is on the
network.
• Graphic displays can be exported to
ASCII-format. With scripts that alter
the contents you can make new dis-
plays. For example with Find &
Replace you can make similar dis-
plays that show other ranges of items.
• Actions can be triggered via
Function-keys, Alt/Ctrl-combinations
or right-mouse clicks. These actions
need not be FAST/TOOLS related but
can start for example non.
FAST/TOOLS executables.
• Displays can be coupled to a user-
type. At login it is determined which
display hierarchy will be active.
• Graphical objects can be connected to
the programs you make, creating
powerful interactions with the user.
5.2 Symbols
FAST/TOOLS provides a large number
of symbols. Currently as standard
more than 3,000 industrial and manu-
facturing symbols are included, but you
can add your own symbols.
A symbol consist of primitives like
lines, squares and circles. If the library
28 doesn’t have the symbol you want, you
create your own symbol. Symbols can
be designed once and used many times
in displays.
You can make the (copies of the) sym-
bol animated by directly coupling items
to it or make the symbol more univer-
sal and connect a class to it. This
means that programming logic behind
it makes the symbol behave in the way
you want it, lifting your SCADA sys-
tem on to a process model level instead
of individual I/O level. All the objects
you derive from the class, connect the
tags they use to the symbol.
5.3 Diagnostic Tools
FAST/TOOLS comes with a complete
set of diagnostic tools for every module
which allows on-line monitoring of:
• Configuration settings
• Real-time values of items, communi-
cation statistics, process-load
• Time related issues
• Status values
• And other module specific parameters
These diagnostic tools are used to loca-
te suspicious faulty situations in your
SCADA system and to optimize the
performance of your SCADA system.
Performance optimisation can be done by:
• Balancing network traffic between
e.g. a server and workstation in a
redundant network
• Preventing queue overflows by adap-
ting queue sizes of FAST/TOOLS pro-
cesses
• Optimizing scan times of external
process variables
In addition some diagnostic tools allow
logging diagnostic data to a file on
disk, which can be used for analyses
later on.
The diagnostic features are impressive
and go as far as byte- and bit-informa-
tion. The following are three examples
of diagnostic tools:
5.3.1 Equipment manager dia-
gnostic tool
For example, if you have problems with
a data connection with a special equip-
ment, the equipment diagnostic tool
 which is part of EQUIPMENT/FAST, sages transferred
allows you to see: • Block a message queue
• What data is passing through the • Influence the order of messages in a
line queue
• Which items are involved • Selective flush messages from a
• Information about the gaps in the queue
data stream • Overview of maximum queue use
• Error response in data since system start-up
• Timing issues
• The amount of poll-request per time
interval
• Time synchronisation
• Several communication failure counts
(statistics)

The figure below gives you an impres-

sion of the information which one
option of the equipment diagnostic tool
gives you.

5.3.3. Process variable related

diagnostics
On process variable level the following
information can be collected:
• Statistics about all actions related to
process variables since system start-
up
• Overview of event streams between
process variables and processes
• Detailed information about all history
samples stored

5.3.2. Internal data traffic

diagnostic tool
A lot of information can be gathered
related to the internal data traffic in
the SCADA system. Looking into the
main data streams will give you infor-
mation how to tune the system. By
examining the data traffic between
processes a problem can easily be bro-
ken down into a single process. Some of 5.4 The FAST/TOOLS Setup
the optimisation possibilities are: File Editor
• Overview of total message traffic As Integrator you have the ability to
• Overview of message traffic per pro- change the default behavior of certain
cess functions within the FAST/TOOLS
• Show outstanding number of messa- environment. This behavior is parame-
ges per process terized via so called setup files. To
• Overview of all time related actions change these parameters a Setup File
(clock queue) Editor is available.
• Overview of traffic to other systems
29 • Logging of the data contents of mes-
 The Setup File Editor gives you an
overview in one window of all available
setup files and their current status: all
default or non default parameters,
whether default settings are used or if
they are changed. After selecting a
setup file you are able to:
• Change the parameter settings via a
popup window
• Change in one action all parameter
settings back to their default value by
clicking on the Default-button
5.5 Application Specific data
A unique feature of FAST/TOOLS
allows you to keep your application
specific data apart from the
FAST/TOOLS environment.
Loading this data in one turn is a
quick way of loading the entire confi-
guration, without using
USER/FAST. Even while your
FAST/TOOLS application is
running you can use this feature
to load additional data.
The big advantage of developing and
keeping the data apart from the
FAST/TOOLS environment is that you
can perform version management on
the data.
5.5.1 Quickloading
You can configure an application by
30 hand, but a lot of it can be done by cre-
ating so called ‘quickloads’. All data to
build up a specific application is stored
in csv-files (the ‘Quickload-files’). They
are readable files that you can make
with MS-Excel™, MS-Access™ or wha-
tever application that is able to deliver
readable text.
Below is an example of a Quickload
definition of an item.
"BOILER1","GENERAL","50HZ_311",,"
PANEL EMERGENCY SHUTDOWN BOILER
1" ,"BOOL_TYPE", "DISTR","PROSA-
FE","E:000,0","EV_BIN","ALM_FUP1
All the items of the application where
this example comes from, are created
with MS-Access™ directly from the
customers I/O-list.
In addition, frequently used settings
can be put into a macro. In the examp-
le the last word "Alm_fup1" represents
a macro that describes several first-up
alarm settings for this item.
This way of working saves you a lot of
configuration time and, secondly,
makes the data more readable.
With only one command these configu-
ration files can be loaded into
FAST/TOOLS ("quickloading").
The advantages of preparing the confi-
guration database like this are:
• Preparation of configuration data can
be done off-line
• You can pre-check your data on:
• Consistency
• Format and syntax
• Completeness
(figure 5.1)
Quickload files
 • Re-use for other applications
• Easy and fast configuration of
backup-system

You can ‘quickload’ configurations on-

line without stopping the system.
During loading the configurations
FAST/TOOLS continuously checks the
quickload data. Errors in configura-
tions will be reported instantly, stop-
ping the loading process or skipping
the error if wanted.
The following configuration data can be
prepared off-line without needing
FAST/TOOLS.
• Items have a full text search using the find
• I/O-driver configurations facility.
• Alarm collections Of course beside the online help, detail-
• History groups ed manuals are also available. These
• User-profiles manuals supply you with detailed
• Programming code information on the subjects as descri-
bed the information in a conventional
5.6 FAST/TOOLS Online help book format.
FAST/TOOLS has a number of diffe-
rent levels of on-line help which assist
you in configuring the SCADA environ-
ment. The first help level is the context
sensitive help, which is available for all
FAST/TOOLS dialogs. The second help
level is accessible via the Help menu
and gives you direct access to the Help
contents and Help guide.

The Help contents operate using stan-

dard Windows functionality. This pre-
sented in a books form. In the help
index you can type a part of a key
31 word, to find the information. You also
 6. Product support
6.1 Documentation
There is a range of documentation
available for the FAST/TOOLS packa-
ge. The manuals are written for two
user groups:
• Operators and system managers
• System integrators and programmers
The manuals are clearly written with
many illustrations and useful examp-
les. The manuals, in the English
language, are delivered with the
FAST/TOOLS licences. The System
integrator and Maintenance manuals,
and Programmers guides are part of
the development kit and available in
the English language.
The documentation is available on CD-
ROM and can be accessed via a user
friendly document browser. On request
the manuals can be printed.
6.2 Training
Yokogawa ISS offers a series of stan-
dard FAST/TOOLS training courses.
These are conducted in the excellent
training facilities of Yokogawa ISS in
Apeldoorn, The Netherlands. Special
training sessions can be organised at
the customer’s site. Each course will
give the student a thorough basis to
the application of the course subject.
The courses consist of a theoretical
part and a series of hands-on sessions
where the student will gain practical
experience. The following courses are
available:
6.2.1 FAST/TOOLS Process
Operations
Process Operators makes use of the
application in order to monitor or con-
trol the process. These users do not
necessarily have any knowledge of the
underlying (FAST/TOOLS) system,
except for the dialogue with the
Human Machine Interface. Obviously,
the process operator interface will
strongly depend on the application
32 demand. This lecture-based course
combined with lab exercises provides
the opportunity for hands-on experien-
ce with the fundamental TOOLS. This
training is given on request and is
customer specific.
6.2.2 FAST/TOOLS System
Management
The course is meant for System
Managers who will configure and or
maintain the FAST/TOOLS operational
environment. This course can also be
given to System Integrators and or
Programmers. For these users the
course is meant as an introduction to
the course "FAST/TOOLS Architecture
and Internal Structure".
Subjects that are part of the course are:
• Configure alarm situations (e.g.
limits, activation, alarm text, sup-
pression, acknowledgement)
• Show process variables and display
historical information
• Process control functions (classes)
• Define user reports
• Create mimics
6.2.3 FAST/TOOLS Architecture
and Internal Structure
Value Added Resellers (VAR’s) and
System Integrators actually use
FAST/TOOLS in the way it is designed
for: a set of tools. The FAST/TOOLS
are used as the basis for the final
application. Tools can be added and
configured as desired, eliminating the
need to put a lot of effort in the basic
functionality. This modular course
covers the design aspects, internals,
service aspects, fault finding, building
API’s (Application Programming
Interfaces) and SCADA engineering
and integration aspects.
6.3 Consulting
Yokogawa ISS offers a complete set of
professional services that can be tailo-
red to your specific needs. Our highly
praised consultants provide services
that offer a quick, cost-effective way to
ensure success in developing and
 implementing your FAST/TOOLS sys-
tems.
Yokogawa has many years of experien-
ce assisting users from the process con-
trol industries, as well as in many
other application areas. In addition,
the company invests in the continuous
education of our professional service
staff.
Yokogawa ISS consultants can give you
advice on the following subjects
• Conceptual study
• Proof of concept study
• Feasibility study
• Project handling
• Networking study
• Communication protocol interfacing
• Custom graphics
• Application prototypes
• Performance tuning
Yokogawa ISS is dedicated to providing
quality customized consulting services
to our customers. Our consulting servi-
ces are offered by a team of professio-
nals who are highly experienced in con-
ceptual, detail application and third
parts software integration. The
Yokogawa ISS consulting staff includes
senior developers and expert applica-
tion builders with many years of expe-
rience.
Yokogawa ISS consulting services are
available in any form that fits your
unique configuration and programming
needs. Services range form simple, day-
rate advisory to complex, ongoing pro-
jects. Our staff can assist in any or all
phases of your integration process,
from conceptual study to implementa-
tion and maintenance.
6.4 Software licensing
There are three different categories of
software licensing, each supporting a
different function.
There is the Server Package, which
include nearly all the FAST/TOOLS
function modules. Depending on the
numbers of tags you need a different
33 license. The range starts with 250 tags
up to an unlimited version (unlimited .
> 750.000 tags) The number of suppor-
ted tags can be increased in a later
stage via upgrade licenses. This makes
it possible to balance the investment of
the SCADA system with the needs of
your site and to expand the system
only when necessary.
A sub set of the Server Package is the
Front-End package which includes only
the real-time database related modules.
The third category is the Operator
Station package. This includes the
HMI client license only.
All software licenses are sold with a
support contract and will become effec-
tive at license purchase.
The support contract covers technical
support, telephone support and soft-
ware upgrades. Support is therefore
available while the system is being
commissioned to assist the engineers
with technical matters concerning the
installation and configuration, as well
as assisting the end users with any
queries they may have.
Our Service and Support Center in the
Netherlands is able to support your
system for 24 hours /365 days.
The FAST/TOOLS software is available
in three languages English, French
and German. At installation the
national version must be selected. This
means you can accommodate the lan-
guage of your customers.
 7. Technical Review
System Architecture
• Client – Server Architecture with
Thick and/or Thin clients Scalable
system from single node to multi ser-
ver systems
• Distributed SCADA system; worksta-
tions, servers and front-ends
• Multi platforms (You can make com-
bination of platforms)
Personal Computer: Windows 2000
Hewlett Packard: HP-UX
IBM: RS6000/AIX
SUN: Solaris for SPARC
General
• Automatic time synchronization of all
nodes. One system time for the appli-
cation (GPS or Radio Control)
• Max 256 nodes (nodes can be Servers,
Workstations or Front-ends).
Unlimited I/O real time database.
• Reference site with over a million
database points
• Object oriented high level program-
ming language within FAST/TOOLS
Redundancy
• Primary/backup architecture fault
tolerance architecture
Networking
• Redundant network support
I/O communication
• Continuous communication link
monitoring with automatic fail-over
to max two other communication
links.
• Up to a maximum of 255 different I/O
drivers can run on one node.
• I/O acquisition on scan- or event
based
Items (data points)
• Max 45 character item name, in for-
mat unit.installation.tag, so multiple
instances of the same tag names are
possible.
Quality index
Value clamping
34 Sub-items
Integrator
Pulse counter
Min/max indicator
Rate of change
Limit and deadband
Blocks of items, unit & installation
Data compression
Displays
• Object Oriented Display builder
• More than 3000 symbols
• Unlimited numbers of display and
symbols
• Multi monitor support
• Multiple animation on the same
symbols
Connectivity
• OPC server and OPC client
• ODBC server both for process data as
well for configuring the SCADA sys-
tem
• Data Set Service (DSS) appears to
the application developer as an
Application Programming Interface
(API) for easy connection of third
party software
Alarm Management
• Unlimited numbers of alarms - cen-
tralised or distributed
• Outstanding alarm overview and
Sequence of Event (SOE) overview
• Define acknowledging the alarms
• Define layout of alarm lines
• Delayed alarms
• Repeated alarms
• Alarm groups
• Alarm collections
• First out and first up alarm annun-
ciation
• Area of Interest
• Alarm re-routing
• Alarm prioritising
Operator log/audit trail
• Store actions of users and SCADA
system; Who, Where, When, What and
Why
 Trends
• Bar, line, points, scatter, & web
• Up to 10 pens per trend.
• Zoom and pan
• Configurable sample periods
• Hairline cursor

Reports
• Scheduled and event-based report
generation
• Report manager and report browsing
• Ad hoc generation of reports
• Printer management

Data Archiving
• On scan and event based
• Storing information on time, item,
event & direct based
• Averaging of history values
• Managing historical files
• Automatic archiving on tape of all
new historical data

Security
• User name & password
• User groups
• Language selection
• Authorization level (0-999)
• Authorization groups
• Process area access
• Initial display
• Hierarchy field for forms access

Support tools
• On line protocol analyzer
• On line debug tools
• On line system diagnostics tools
• Setup file editor

35
 Yokogawa Industrial Safety Systems B.V.
Lange Amerikaweg 55, 7332 BP Apeldoorn
P.O. Box 20020, 7302 HA Apeldoorn
The Netherlands
Tel.: Int. +31 (0) 55 538 9500
Fax: Int. +31 (0) 55 538 9511
E-mail: marketing@yis.nl

Yokogawa Industrial Safety Systems Sdn. Bhd.

No. 8, Jalan 12/91A
Taman Shamelin Perkasa
3 1/2 Miles, Jalan Cheras
56100 Kuala Lumpur
Malaysia
Tel.: Int +60 (0) 3 9200 2100
Fax: Int +60 (0) 3 9200 5100
E-mail: marketing@yis.nl

Yokogawa Electric Corporation

Industrial Safety Systems Dept.
Industrial Automation Systems Business Div.
2-9-32 Nakacho, Musashino-shi, Tokyo
180-8750 Japan
Tel.: +81 422 52 5816
Fax.: +81 422 52 0571
E-mail: prosafe@csv.yokogawa.co.jp

For more information:

www.yokogawa-iss.com
BU 50A04A00-00E-N/0401/05