01 PCP System
01 PCP System
x Training
1 – PCP System
Table of Contents
1 – PCP System.................................................................................................................1
1.1 General Information.............................................................................................2
1.1.1 Objectives.....................................................................................................2
1.1.2 Reference Documents.................................................................................2
1.2 System Overview................................................................................................3
1.2.1 Introduction..................................................................................................3
1.2.2 Data Acquisition...........................................................................................4
1.2.3 Architecture..................................................................................................4
1.2.4 Calculations..................................................................................................5
1.2.5 Human System Interface..............................................................................5
1.2.6 Process Control............................................................................................7
1.2.7 Alarm Management......................................................................................8
1.2.8 Trending.......................................................................................................9
1.2.9 Historian.....................................................................................................10
1.2.10 Reporting....................................................................................................11
1.3 PCP architecture...............................................................................................12
1.3.1 Server / Client Structure.............................................................................12
1.3.2 Internal architecture...................................................................................13
1.3.3 Functional architecture...............................................................................17
1.3.3.1 On-line and Off-line parts..........................................................................17
1.3.4 Configuration overview...............................................................................18
1.4 Installation and initial setup...............................................................................19
1.4.1 Preparation before installation...................................................................19
1.4.2 Installation..................................................................................................19
1.4.3 Post Installation Setup...............................................................................24
1.4.4 License.......................................................................................................29
1.4.4.1 License installation....................................................................................29
1.5 User Login.........................................................................................................34
1.5.1 Users configuration....................................................................................36
1.1.1 Objectives
Code Description
The powerful features of distributed data acquisition and control system and the latest
generation of field proven hardware and software platforms are combined in a flexible
and open Client-Server architecture to provide plant information and human interface
capabilities.
Monitoring and real-time optimization tools are provided for both utility and industrial
processes.
In addition to standard configuration facilities, open system design, flexible hardware
platform and client-server software architecture offer easy adaptation to any specific
user requirements.
ABB PS&S can provide customized application and engineering services as a part of
standard product support.
Plant and process data are gathered from field devices and/or other data servers via:
Ethernet TCP/IP
OPC (AC800F, AC800M, DCI System Six, third party OPC devices)
IEC870-5-101/103/104
ODBC
Generic Serial Link Protocols ( Modbus, Modbus RTU, Modbus TCP)
Siemens Teleperm (through XU device)
General Electric Mark V / VI (through GSM Protocol)
SPABUS
Parallel SCSI or serial RS232
(Modbus, Symphony proprietary protocol)
Server processes data acquired from the plant to provide diagnostic checks
(reasonability limits, open circuit, loss of power, rate of change, etc.), numeric filtering
(smoothing), alarm checking (with the capability of alarm inhibition and variable alarm
limits), and bad quality management. Multiple interfaces, executing through parallel
communication channels, assure high-speed data transfer to the server, while providing
fault tolerance through modularity.
1.2.3 Architecture
Standard hardware interfaces and protocols are used to connect local and geographical
networks, in order to make the system "open" and take advantage of distributed
architectures and functions.
1.2.4 Calculations
Displays may include real time data, such as process variables, digital inputs and
outputs, as well as historical data and information from user generated files. The
information may be presented using different formats such as alphanumeric, text string,
bar charts, dynamic symbols, trends, all according to user requirements.
Color, shape and blink can be assigned to dynamic elements of the display according to
associated quality flags (e.g. acknowledged / unacknowledged alarms, etc.).
The dynamic process data is updated at a rate of once per second. The entire system is
optimized to produce fast display retrieval and use minimal resources for data
refreshing.
The operator interface includes a full range of operator security features that can bound
access to programs, function keys, displays or individual fields, depending on operator
access rights. Security access is based on user name and password.
A powerful interactive graphic display builder with a basic shape library, a full range of
graphic commands to draw the display background and a library of dynamic elements to
specify process control information is provided to create application displays. The
number of supported displays is limited only by the available disk space.
Pop-up control faceplates allow the operator to control the process directly from plant
mimic displays. A single element can be controlled directly from the plant display.
A single pop-up or multiple pop-ups can be kept on top of the mimic during control
phases.
Control faceplates can be customized and created using the standard onboard display
builder.
Predefined graphic pages, named pegboards, allow the simultaneous control of multiple
field devices.
Custom application programs can be implemented to change controller modes, set
points, control outputs, ratios and/or switch positions through an application
programming interface.
This approach can be used to directly output the results of advanced control,
optimization or scheduling algorithms.
Alarm limits can be associated with any variable created by the various subsystems
(Process I/O, Calculation, User programs). If these limits are exceeded, alarm messages
can be issued to the
operator station and loggers. Multiple limits per point can be defined, in order to monitor
high/low alarm and pre-alarm (warning) conditions.
Individual alarm messages or alarm messages within a alarm page can be
acknowledged.
1.2.8 Trending
The trend display feature provides the ability to graphically display both current and
historical data. Any tag can be trended as real time data without being defined for
historical storage.
The trend presentation can be arranged in different formats and can be presented as a
window inside other displays. If needed, the Real Time presentation automatically takes
into account the historical archive in order to present the oldest data.
Variables to be trended and display attributes are dynamically defined by the user. The
fields that may be entered by the operator include process variable identification,
minimum and maximum value for scaling the Y axis, start time, time span and color.
All trend displays support pan and zoom functions that are addressed by the operator
just pressing a single key. A drag cursor allows to scan values on the trend curves.
1.2.9 Historian
The historical processor automatically saves data from field and calculated data in a
buffer called "Playback" in order to provide the capability of a very detailed medium-term
history for all tags. Compression algorithms are applied to the “Playback” buffer to
provide a more extensive history of the plant.
Historical data may be used for plot displays, trend logs, calculations or user written
applications for which standard functions are provided to access the data.
By default, the Playback buffer holds 24 hours of data. To keep a medium term history of
the plant, the Playback buffer is automatically saved on hard disk. By default, up to 10
days of data are kept on the hard disk and can be explored using standard access
interfaces. The 10 saved
Playback buffers are managed as a circular buffer.
Utilities are provided to manage Playback buffers and save them for a permanent off-line
history of the plant. Restore utilities are also provided. An automatic saving utility is
provided.
For long-term recording, the historical trend processor samples user-selected tags at
established intervals. Sampled data are processed to generate the datum to be saved in
the historical database. Instantaneous value, average, minimum, maximum, minimum
and total value, etc. can be defined.
Historical trend groups can be configured to define tags involved in the historical
processing. Standard utilities allow to retrieve and display historical data in trend curve
or table format.
Utilities are provided to manage the historical data files and to save/retrieve data to/from
permanent external storage.
1.2.10 Reporting
Process Control Portal provides full flexibility for formatting of reports using the standard
MS tools, which are fed by the DDE or OLE2/COM interface.
To format a standard report, the user simply creates an Excel spreadsheet using a
library of built-in functions to access databases.
PCP is based on a Server / Client structure, a modern architecture that allows flexibility
of use, a good system management and better reliability than other architectures
Monitor
Interface
Keyboard
Mouse / Trackball
Client
Server
The Server part ( a software process ) includes the Application Software Configuration
( Process Tags, Graphic pages etc ) and is bound to communicate to the controllers
using a specific interface depending on the type of controllers.
The Client part gets information from the Server and and drives the peripherals, such as
mouse/trackball, monitor, keyboard.
A Client represents a physical Workplace.
Connecting more than one client to a Server you can use many workplaces with only
one Server configured.
This solution is not wise, because in case of fault of the Server or even of the Interface,
all Clients will be out of order.
It is always advisable to have at least two Servers with a desired number of Clients.
Ethernet
Note that in real applications the computer hosting a Server also usually includes a
Client .
PCP resides on a tree of folders starting from one named “Process Control Portal”.
During installation you will be asked for the installation path and presented a default,
what before “Process Control Portal” can be modified ( Figure 1.3.2-1 ).
Application engineers must learn and remember very well some of the folders included
in the tree:
The folder \Config is the placeholder for most configurations ( Figure 1.3.2-2).
Some folders are important for PCP itself and should not be touched:
To understand how PCP works, the best way is to consider PCP as a black box split in
two parts: on-line and off-line.
The off-line part is mainly based on the folder \Process Control Portal\config.
On-line configuration
PCP
On-line part
Off-line configuration
PCP databases are mainly loaded by a set of (at least one) DBF or XLS files. The
content of these files is processed and loaded in the PCP data files by running a build
procedure. These files are located, unless differently specified, in the CONFIG folder
and its sub-folders.
PCP is mainly off-line customized editing a set of files. They are commonly named
DECK files or DECKs. These files are located, unless differently specified, in the DECK
folder.
The content of DECK files is processed and loaded in the PCP data files by running a
build procedure.
Database configuration and system customizations are separated activities. They can be
performed in different time and, with some restrictions, in whatever order.
Each operation can be performed separately from the others. Only changing the system
sizes or rebuilding the file system requires a complete build procedure. A single DECK
can be processed to change a specific configuration. Restrictions in the sequence of
processing take place when DECKs have some relationship.
System configuration parameters are defined into the MS-Windows Registry. Creating or
modifying these parameters is the first step in configuring PCP. Values of these symbols
will be used to size global commons,
data files, to select options and roughly customize the PCP application.
PCP installation sets a default value for each configuration parameter in order to allow
correct operation without any change. The parameters are located in
Hkey_Local_Machine\Software\ABB\Process Control Portal registry key of the MS-
Windows Registry.
PCP supplies a utility, named SysSetup, which allows viewing and modifying the
configuration parameters.
The SysSetup process only interfaces the PCP registry set.
When select the Registry button, the process dialog window changes. The tree of
registry folders is displayed on the left side of the dialog window. On the right side of the
dialog window the registry items are listed once the registry folder, has been selected.
Prior to install Process Control Software, some additional software must be installed on
your computer. This software is also included in the PCP installation CD.
1.4.2 Installation
If it is an upgrade from previous release, first stop PCP execution, then proceed.
If it is a new installation, proceed as follows.
Login as Administrator.
Click on Start > Run
Click OK.
In the next window select the installation path. A default one is proposed.
In the next window you can select the features you want to install.
Click Finish.
In the next InstallShield Wizard window select Yes to restart the computer. Click Finish.
Click :
Start > Programs > ABB Industrial IT > Process Control Portal > System Setup
Run Windows Explorer and open the folder \Process Control Portal\config\setup.
On the left pane of the System Setup window select expand Build Data Base.
This procedure will create and initialize all files in the folder \Process Control Portal\data.
After you click Build All the right part of the window will populate with check boxes and fill
in blank areas. Do not mind of them for this procedure, only check the box “Echo” that
allows to follow the sequence.
Click on the button “Import”. A dialog will ask to continue or not. Click OK.
At the end of the procedure you will read Build All completed.
The next step was meant to register all necessary files just installed.
On the left part of the System Setup window, expand Client and Server.
Do not take care of the check boxes at this level ( leave the default as it is ).
Click OK.
1.4.4 License
A license must be installed in all PCP Servers. Servers are responsible to manage a
number of clients. Clients do not need a local license. When the maximum number of
clients allowed for a Server is reached, the Server will not accept any additional
connection.
Licenses are locked to a Machine ID, usually a Hardware Key ( Dongle ) to connect to
the parallel port of the PC. It is also possible to use the MAC address of the Ethernet
card of the PC.
The user can receive the license on a Excel form or text file or both.
Fill the blanks with data from the Excel form or get data from the .DAT file.
Click Validate.
Click OK.
Click Save.
Click OK.
Click Test Checkout.
Click OK.
Repeat the sequence just done for Basic Features also for Drivers and
Application.
Close the System Setup window.
To start PCP:
Start > Programs > ABB Industrial IT > Process Control Portal > Start
Process Control portal
The command Start Process Control Portal will start both Server and Client.
The command for the Client only is Process Control Portal Explorer.
After few seconds on the task bar of the computer there will be the indication that
PCP ( Server ) is running.
User Password
SYSMGR PRIV
ENGINEER LEVEL1
OPERATOR LEVEL0
At startup PCP starts with a “default” user, one of the three available.
The default choice is “OPERATOR”, but it is possible to define a different default user
setting a specific register.
The register is located in the registry system in the folder:
\Process Control Portal\APPS\TntExplorer.
The name of the register is: DefaultUser. To access the register:
Start > Programs > ABB Industrial IT > Process Control Portal > System Setup.
Type in the name of the User you want at startup, then click OK to close the window.
Next time TntExplorer will start, it will use the new User.
To configure a new user click on the icon “New” or on “Configure > New Item”.
The two panes “Tag Operations” and “Privileges” in practice define “what” you can do.
Security groups and the tab “Clients” define “where” you can do what allowed before.