IndustrialIT

System 800xA
Version 4.1

System Guide
Performance and Capacity
 IndustrialIT
System 800xA
Version 4.1

System Guide
Performance and Capacity
NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.

This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.

The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.

This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.

Copyright © 2003 - 2004 by ABB.

All rights reserved.

Release: June 2005

Document number: 3BSE041434R4101

TRADEMARKS
All rights to trademarks reside with their respective owners:
 Section 1 - System 800xA
Introduction .......................................................................................................................9
System 800xA Capabilities ...............................................................................................9
Servers ...............................................................................................................9
Clients .............................................................................................................10
Server Based Clients ............................................................................................10
System Capabilities Summary .............................................................................11
System 800xA Dimensioning..........................................................................................11
Tag Calculation and Aspect Object Creation .......................................................11
CLP Calculations .................................................................................................12
Configuration Rules.........................................................................................................15
Domain vs. Workgroup ........................................................................................16
Windows XP vs. Windows Server .......................................................................16
Connectivity Server Combinations within System ..............................................17
Connectivity Server Service Combinations .........................................................17
Combined Node Types .........................................................................................17
Engineering Systems ............................................................................................20
Network Configuration ........................................................................................22
Configuration Rules Summary.............................................................................22
Available Functions..............................................................................................31
Third Party Hardware and Software................................................................................38
PC Recommendations for System 800xA............................................................38
Supported Operating Systems ..............................................................................38
Other third party software ....................................................................................38
Core System.....................................................................................................................39
Control Network Clock Synchronization ........................................................................41
AC 800M Connect Performance .....................................................................................41
Connectivity Server Throughput..........................................................................41
Display Call-up Time ...........................................................................................42
Command Response Time....................................................................................42
Information Management ................................................................................................43
PPA History Capability ........................................................................................43

3BSE041434R4101 5
 History Services ...................................................................................................43
Batch Management ..........................................................................................................50
Manufacturing Management ...........................................................................................52
Asset Optimization ..........................................................................................................53
Fieldbus ...........................................................................................................................53
System Configuration Examples .....................................................................................55

Section 2 - Control and I/O

Control and I/O................................................................................................................61
Memory .............................................................................................................61
Spare Memory Needed for Online Changes ........................................................64
Comparing Memory Allocations Made with Different Versions .........................65
Memory Consumption and Execution Times.......................................................66
Compilation and Download .................................................................................69
Hardware and I/O ............................................................................................................70
Modulebus Scanning of Digital/Analog Modules................................................70
Calculation of Scan Time on the Modulebus and CPU load................................70
Modulebus Scanning of ABB Drives (AC 800M) ...............................................72
I/O Channels in High Integrity Controller ...........................................................72
I/O Response Time...............................................................................................73
MMS Communication..........................................................................................74
INSUM Network ..................................................................................................77
ModBus Communication .....................................................................................78

Section 3 - 800xA for DCI

Technical Data and Performance.....................................................................................80
800xA for DCI Performance ................................................................................81
Recommended Hardware Configuration..............................................................83

Section 4 - 800xA for Harmony

Technical Data and Performance.....................................................................................84
Harmony Performance .........................................................................................85
Recommended Hardware Configuration..............................................................87

3BSE041434R4101 6
 Section 5 - 800xA for Melody
Technical Data and Performance.....................................................................................89
Sizing Data (Melody) ...........................................................................................90
Recommended Hardware Configuration..............................................................90
Supported Operating Systems ..............................................................................91

Section 6 - 800xA for MOD 300

Technical Data and Performance.....................................................................................92
Technical Data......................................................................................................92
Product Performance ............................................................................................93
Pre-requisites and Configuration Rules...........................................................................94

Section 7 - 800xA for Advant Master

Technical Data and Performance .....................................................................................97
Technical Data......................................................................................................97
Product Performance ..........................................................................................101

Section 8 - PLC Connect

Technical Data and Performance...................................................................................102
Technical Data....................................................................................................102
Product Performance ..........................................................................................104

Section 9 - Process Engineering Tool Integration for INtools

Technical Data and Performance...................................................................................106
Configuration Rules ...........................................................................................106
Performance Data...............................................................................................106

3BSE041434R4101 7
8 3BSE041434R4101
 Section 1 System 800xA

Introduction
This document contains performance and capacity data for the Industrial IT
Extended Automation System 800xA. The document also specifies configuration-
and dimensioning rules.
The document is an appendix to the System 800xA, System Guide, and intended for
sales people when making quotations. The information in this document is also of
interest during system design, engineering, and commissioning. The document is
delivered on the System 800xA software media.

System 800xA Capabilities

The System 800xA is scalable both in functionality and size. The rules for how the
system can be configured depends on how functionality is combined in different
node types, and on the system and application size. This chapter defines these
combinations and rules for System 800xA SV 4.1.
Different system functions are provided by different types of nodes in a
System 800xA installation. A node in this context is a computer (PC) that has a
network address on the 800xA system network, used as a server, or as a client.

Servers
In most cases, server nodes can be configured for redundant operation, either as
1oo2 or 2oo3 (one-out-of-two or two-out-of-three). Note that in order to achieve the
intended increase in system availability, server redundancy requires the 800xA
system network to also be redundant.
The basic server node types are:

3BSE041434R4101 9
Clients Section 1 System 800xA

• Domain Server - runs the Domain Controller and Domain Name System.
Supports 1oo2 redundancy.
• Aspect Server - runs the ‘central’ intelligence in the system, including the
aspect directory and other services related to object management, object names
and structures, security etc. Supports 1oo2 or 2oo3 redundancy.
• Connectivity Server - provides access to controllers and other data sources.
Supports 1oo2 redundancy.
• Application Server - runs various types of system applications
– Batch Server - runs Batch Management. Supports 1oo2 redundancy.
– IM Server - runs Information Management. Dual servers supported.
– AO Server - runs Asset Optimization. No redundancy.
– MM Server - runs Manufacturing Management. No redundancy.
– Other applications.
* Softpoints: 1oo2 redundancy.
* Calculations: No redundancy.
* Integrated third party applications. Depending on the functionality, these
application servers may or may not support redundancy.

Clients
A Client runs workplace functionality, such as operator and engineering
workplaces, including Batch, Information Manager, Manufacturing Manager, and
Asset Optimization clients.
A Remote Client Server provides terminal server functionality to connect to remote
workplaces.

Server Based Clients

All node types except the Domain Server include client functionality. These clients
are referred to as server based clients.

10 3BSE041434R4101
Section 1 System 800xA System Capabilities Summary

System Capabilities Summary

The System 800xA has the following general capabilities:
• One Domain Server
• One Aspect Server
• up to 12 Connectivity Servers
• up to 10 Application Servers
• up to 40 Clients
• up to 75 AC 800M Controllers
• up to 60.000 Tags

System 800xA Dimensioning

Tag Calculation and Aspect Object Creation
A Tag is any Aspect Object that has one or more Faceplate Aspects attached.

Minimizing of Aspect Object creation in the Control Structure

In order to avoid unnecessary creation of Aspect Objects in the Aspect Directory,
there is a way to minimize the number of created Aspect Objects from the Control
Builder M.
There are two attributes in the Control Builder that affects the creation of Aspect
Objects in the Control Structure.
• Alarm Owner. This is an attribute on Types in the libraries. Default setting for
this attribute is true for both Control Modules and for Function Blocks. The
default setting can be changed on the Type in the library. If Alarm Owner is
true, an Aspect Object is created upon instantiation of the Type.
• Aspect Object is an attribute on instances in the application, and on formal
instances (instances inside function block or control module types). If the
attribute Alarm Owner is true on the Type, the Aspect Object attribute is set to
true when the instance is created, and hence an Aspect Object is created.
Otherwise, no Aspect Object is created.

3BSE041434R4101 11
CLP Calculations Section 1 System 800xA

You can change the Aspect Object attribute on the instance in the Control
Builder if you want to override the default creation as described above.
NOTE! For objects created from the Plant Explorer the attribute Aspect Object is
always by default set to true.

CLP Calculations
The CLP (Control License Point) calculation, used when ordering
AC 800M Control Software Integration, is based on all variables connected to local
and remote devices, such as I/O units, FOUNDATION Fieldbus, or PROFIBUS
devices.
There are different licenses for CLP count depending on, if you run with a regular
AC 800M controller for non-SIL applications, or an AC 800M High Integrity
controller for SIL applications, or a combined controller (AC 800M High Integrity
controller) for both SIL and non-SIL applications.
The CLP calculation is made in the Control Builder hardware tree-structure in the
Project Explorer. The hardware tree in the Control Builder is where I/O and other
field connected devices (via e.g. PROFIBUS-DP/PA, FOUNDATION Fieldbus-
HSE, INSUM, DriveBus or ModuleBus) are defined. See below picture:

Figure 1. Control Builder Hardware Tree-structure

12 3BSE041434R4101
Section 1 System 800xA CLP Calculations

The number of CLPs to be counted per variable, INSUM MCU, and ABB Drive are:
Basic rule:
• Each variable in the hardware tree of Boolean data type counts as one CLP.
• Each variable in the hardware tree of non-Boolean data type counts as two
CLPs.
Exception rules:
• Each INSUM MCU counts as seven CLPs.
• Each ABB Engineered Drive counts as ten CLPs.
• Each ABB Standard Drive counts as seven CLPs.
Note, that variables connected in the hardware tree for INSUM MCUs and ABB
Drives, shall not be counted according to the basic rule. The calculation is based on
a fixed number of CLPs per MCU and Drive, according to the exception rule above.
Variables used in the Control Builder application connected via access variables e.g.
Modbus, MMS, COMLI or Siemens 3964R, are not counted as CLPs.
• AC 800M High Integrity controller. A CLP license for SIL applications
calculates the number of variables connected to I/O for an AC 800M High
Integrity controller (SIL marked applications only).
• Combined controller. A fixed license plus both a CLP license for non-SIL
applications, and a CLP license for SIL applications. A combined controller is
always an AC 800M High Integrity controller (for running both SIL and non-
SIL applications in a High Integrity controller). One license must be purchased
per controller.

Counting CLPs
To calculate the total number of CLPs:
• Identify all objects to be controlled by each controller.
• Count all Boolean connected variables.
• Count all non-Boolean connected variables.
• For each Boolean variable, add one (1) CLP to the CLP count.

3BSE041434R4101 13
CLP Calculations Section 1 System 800xA

• For each non-Boolean variable, add two CLPs to the CLP count.
• Count the CLPs for INSUM MCUs, ABB Engineered Drives and ABB
Standard Drives according to the CLP calculation list above.
• Add 20% to the CLP count, to create a margin for growth.
An example:
A project consisting of:
• Two S800 I/O units (one AI895 and one DO810). There are 5 variables
connected to each of these I/O boards. And on one of the AI channels, there is a
HART pressure transmitter connected
• One ABB Drive ACS 800
• One PROFIBUS-PA instrument connected (with one analog signal)
• 200 boolean signals connected form a 3rd party Modbus device
Is counted as:
• According to the basic rule: 5 analog signals and 5 boolean signals above is
calculated as 10+5=15CLPs. (Unused I/O connections is not counted, HART
data is counted only for the data used in the AC 800M controller)
• According to one of the exception rules ABB Drives (standard Drives) is
calculated as 7 CLPs, no matter how many variables are used to/from the drive.
• According to the basic rule, variables connected to instruments on PROFIBUS-
PA is counted according to how many variables are used, in this case one
analog ≥ 2CLP.
• Variables connected via access variables are not counted
In total this application is consuming 15+7+2=24 CLPs.

14 3BSE041434R4101
Section 1 System 800xA Configuration Rules

Configuration Rules
In configuration drawings, PC nodes are drawn as rectangles, with the node type as
label. The operating system (Windows XP or Windows Server) is indicated with XP
or S respective. Redundancy, if supported, is indicated as 1oo2 or 2oo3 (one-out-of-
two or two-out-of-three).

<Node Type>

<OS> <Redundancy>

Figure 2. PC node drawing

Figure 3 below illustrates the general System 800xA Configuration principles. The
maximum number of each node type is listed in Table 1.

Domain Aspect Server IM Server Client Remote Client

Server Server
1oo2 or
S 1oo2 S 2oo3 S xx XP 1oo2 S 1oo2

Batch Server AO Server Conn. Server Appl. Server

S 1oo2 S 1oo2 S 1oo2 S (1oo2)

Figure 3. General Configuration

Depending on the system and application size, there are different ways to optimize
this configuration, by
• using a workgroup instead of a domain
• using Windows XP for certain servers
• combining different connect services in the same Connectivity Server

3BSE041434R4101 15
Domain vs. Workgroup Section 1 System 800xA

• using combined node types

Domain vs. Workgroup

A System 800xA installation can be configured either as a Windows Domain or as a
Workgroup.
• When the system is configured as a domain, a separate (optionally redundant)
Domain Server is required. For installation as a production system, it is
strongly recommended that the 800xA system forms its own domain, i.e. it
should not be part of a larger domain, such as a corporate network domain.
• A workgroup becomes increasingly difficult to administer as the number of
users and computers grows. Workgroup should therefore be considered only
for small systems with few users.

Windows XP vs. Windows Server

Certain server types can run on Windows XP as well as on Windows Server.
Depending on Microsoft licensing rules, the system size is limited when Windows
XP is used for any server node.
• When Windows XP is used for the Aspect Server(s), the system size is limited
to nine PC nodes, not counting Domain Servers.
• When Windows XP is used for any other server, but not for the Aspect
Server(s), the system size is limited to 11 PC nodes, not counting Domain
Servers.
• Some server types always require Windows Server:
– Domain Server
– Batch Server (in all configurations except single node engineering system)
– Asset Optimization Server (in all configurations except single node
system)
– Information Management Server (in all configurations except single node
engineering system)
– Manufacturing Management Server
– Connectivity Servers: Harmony, Harmony Configuration, Melody,
Melody Configuration, MOD 300

16 3BSE041434R4101
Section 1 System 800xA Connectivity Server Combinations within System

Note that all servers in a redundant group (1oo2 or 2oo3) must always use the same
operating system.

Connectivity Server Combinations within System

Only one OCS connectivity can be used in one and the same system, together with
AC 800M. The following exceptions apply:
- Advant Master AC 400 and Safeguard can be used simultaneously
- Symphony Melody can not be used together with AC 800M.

Connectivity Server Service Combinations

The following connect services can be combined in the same Connectivity Server
node:
• AC 800M Connect
• FOUNDATION Fieldbus Device Integration
• PROFIBUS Device Integration
• HART Device Integration
• PLC Connect
800xA for SafeGuard requires 800xA for Advant Master in the same Connectivity
Server node.
Other connect services require separate Connectivity Servers, unless otherwise is
specified in the respective System Guide appendix.

Combined Node Types

In order to optimize the cost/performance ratio for a particular installation, certain
server functions can be combined in the same node. Depending on what functions
are combined there are different limitations to system sizes. Approved combinations
are
• AS+CS - Aspect and Connectivity Server. Supports 1oo2 redundancy.
The connect services that can run in an AS+CS node are the same as the ones
that can be combined in one Connectivity Server, see above.

3BSE041434R4101 17
Combined Node Types Section 1 System 800xA

• AS+CS+AO - Aspect, Connectivity and Asset Optimization Server. This

combined node type supports 1oo2 redundancy for the AS and CS functions.
The connect services that can run in an AS+CS+AO node are the same as the
ones that can be combined in one Connectivity Server, see above.
• Batch+IM+MM - Batch, Information Management, and Manufacturing
Management Server. No redundancy.
A single node system is a system that consists of one node of type AS+CS or
AS+CS+AO. Only a few controllers can be connected and the applications are
small.

Aspect Server
Conn. Server
(AO Server) AO Server optional
Client
XP 1oo2

Figure 4. Single node combined system drawing

Systems with up to five clients and limited application size can be configured with
combined node types AS+CS (or AS+CS+AO), and Batch+IM+MM, and with
server based clients.

18 3BSE041434R4101
Section 1 System 800xA Combined Node Types

Domain Server Aspect Server Batch Server Max 5 clients in

Conn. Server IM Server 3 Client total, including
(AO Server1 ) (Client) server based
(2 * Client) clients
S 1oo2 XP/S 2 1oo2 S xxxx XP xxxx

Conn. Server Appl. Server

Optional additional Optional Application
Connectivity Server Server node e.g. for
node for OCS Melody Config Server
systems
S 1oo2 XP/S 2 (1oo2)

1) AO runs non-redundant, in one server

2) Observe limitations for use of Window s XP (see above)
3) Redundancy is not supported for the Batch / IM combined node type

Figure 5. Multi node combined system drawing

For larger applications Batch and IM should run on separate servers, and clients
should be separate. See Batch and IM requirements for further definition.

≤5
Domain Server Aspect Server Batch Server IM Server
Conn. Server Client

S 1oo2 XP 1 1oo2 S 1oo2 S 1oo2 XP

AO Server Conn. Server Appl. Server

S 1oo2 S 1oo2 S (1oo2)

1) Observe limitations for use of Windows XP (see above)

Figure 6. Large combined system drawing

3BSE041434R4101 19
Engineering Systems Section 1 System 800xA

Engineering Systems
An engineering system is intended for engineering only, i.e.no production. Except
for the single node engineering system, the same basic configuration rules apply to
engineering system as to systems intended for production.
With respect to domain membership, there are two use cases for the engineering
system:
1. The engineering system is used stand alone, e.g. in an engineering office. For
this use case, there are three possible alternatives:
– The system can be added to an existing domain (e.g. in an office network
domain)
– The system can be defined as a new domain added to an existing domain
controller
– The system can be defined as:
a separate domain with its own domain controller and DNS server, or
as a workgroup (i.e. same as a production system).
2. The engineering system is connected to a production system and is used for
system synchronization. For this use case the engineering system must belong
to the same domain as the production system.
Engineering node configuration examples:

Aspect Server
Conn. Server
(AO, Batch, IM)
Client
XP xxxx

Figure 7. Single node engineering system

20 3BSE041434R4101
Section 1 System 800xA Engineering Systems

≤ 10
Domain Server Aspect Server Batch Server
Conn. Server IM Server Client
(AO Server)

S (1oo2) XP/S 1oo2 S 1oo2 XP xxxx

Optional additional Conn. Server Appl. Server: SoftControl for

Connectivity Server SoftControl control application
node for OCS systems test purposes only

S 1oo2 XP/S xxxx

Figure 8. Multi user engineering system

3BSE041434R4101 21
Network Configuration Section 1 System 800xA

Network Configuration
The maximum number of nodes (PC nodes and controllers) in one control network
area is given in Table 1. The limitation is primarily due to limited network resources
in controller nodes.
For larger systems a split into separate Client/Server and Control networks is
recommended, if needed with several control network areas (see the chapter
Network Architecture in the System Guide). The maximum number of (PC) nodes
on a client/server network is stated in Table 1.
It is recommended to use 100 Mbit/s switched, fast Ethernet communication
between clients and servers. Controllers use 10 Mbit/s, and should be connected via
switches to 100 Mbit/s backbones.

Configuration Rules Summary

Typically, the following is known when a project is being defined:
• Number of controllers and tags/applications
• Number of Connectivity Servers
• Number of operator workplaces and display values
• Number of PPA logs per Connectivity Server
• Number of IM logs from a Connectivity Server
• Stable state event rate
• Reports and how often they will run with the amount of data (for example 1
daily averages based on 15 second logs)
The following rules help summarize the requirements so system size and loading
can be determined to best meet the known needs. This is organized based on:
• Node Types
• System
• OPC
• Control and I/O
• Applications

22 3BSE041434R4101
Section 1 System 800xA Configuration Rules Summary

Node Type Rules

Table 1 states the maximum numbers of each node type that can be configured in a
system. Numbers in parenthesis indicate the node count for redundant configuration

Table 1. Maximum number of nodes per node type

Max per Out of

Node Type Remark
system which
Network
Combined System Network 50
Separate Control Network 50
Separate Client/Server 100
Network (no controllers)
Servers
Domain Server 1 (2)
Aspect Server 1 (2 or 3)
Connectivity Servers 12 (24)
- AC 800M 8 (16) Included on Connectivity Servers
- PROFIBUS Device 8 (16)
Integration
- HART Device Integration 8 (16)
- FOUNDATION Fieldbus 8 (16) 2 with combined AS+CS or
Device Integration 1 with AS+CS+AO
- PLC Connect 8 (16)
- 800xA for Advant Master 6 (12) Max 2 (4) per MB300 network
- 800xA for Harmony 3 (6)
- 800xA for Melody 8 (16)
- 800xA for MOD 300 3 (6)
- 800xA for AC100 2 (4) Max 1 (2) per AF100 link
- 800xA for SafeGuard See 800xA for Advant Master
- 800xA for DCI 4 (8)
Application Servers 10
- Batch Server 1 (2)

3BSE041434R4101 23
Configuration Rules Summary Section 1 System 800xA

Table 1. Maximum number of nodes per node type (Continued)

Max per Out of

Node Type Remark
system which
- IM Server 6
- AO Server 4
- MM Server 1
- Other applications 2 Application specific restrictions may
apply
Remote Client Servers 2 Not with combined AS+CS or
AS+CS+AO
Combined Servers
Combined Server types 2
- AS+CS 1 (2) Not with separate AS or AS+CS+AO
- AS+CS+AO 1 (2) Not with separate AS or AS+CS. This
combination node type supports 1oo2
redundancy for the AS + CS
functions. AO is not redundant.
Multiple non-redundant AO Servers
are allowed. Precisely one of these
must be configured as the AO Main
Server
- Batch+IM+MM 1 Maximum of 5 Operator Workplaces
with Batch and/or MM Workplaces
supported
Clients
Rich Clients 40
- Operator Workplaces(1) 40 5 with combined AS+CS or
AS+CS+AO or Batch+IM+MM
- Batch Workplaces(1) 40 5 with combined AS+CS or
AS+CS+AO or Batch+IM+MM
- MM Workplaces(1) 40 5 with combined AS+CS or
AS+CS+AO or Batch+IM+MM
- Engineering 10 1 with combined AS+CS or
Workplaces(1) AS+CS+AO

24 3BSE041434R4101
Section 1 System 800xA Configuration Rules Summary

Table 1. Maximum number of nodes per node type (Continued)

Max per Out of

Node Type Remark
system which
Remote Clients 15 Not with combined AS+CS or
AS+CS+AO
- Per Remote Client Server 8
(1) Optionally included

System Level Parameter Rules

Table 2 details the limits in system configuration size when combined and separate
node types are used.

Table 2. System Configuration Limits - System Level Parameters

AS+CS+AO AS+CS
AS+CS+(AO) AS and CS
no server no server
Parameter (max numbers) with server separate
based based
based client
clients clients
Tags (items with faceplates) 1.000 3.000 5.000 60.000
Aspect Objects 5.000 10.000 15.000 200.000
History Sources - see 250 1.500 1.500 180.000
applications for History Logs

Table 3 details the maximum numbers of clients when combined and separate node
types are used.

Table 3. System Configuration Limits - Client Count

AS+CS+AO AS+CS
AS+CS+(AO) AS and CS
no server no server
Parameter (max numbers) with server separate
based based
based client
clients clients
Client nodes 5(1) 5 5 40
Remote Client nodes N/A N/A N/A 15
Engineering clients 1 server based 1 1 10

3BSE041434R4101 25
Configuration Rules Summary Section 1 System 800xA

Table 3. System Configuration Limits - Client Count (Continued)

AS+CS+AO AS+CS
AS+CS+(AO) AS and CS
no server no server
Parameter (max numbers) with server separate
based based
based client
clients clients
Batch Clients - 5 5 40
Information management - 5 5 40
clients
(1) Including server based client

System Level Aspect Server Rules

Table 4 details the limits in system configuration size, as limited by the System
Message Service load on the Aspect Server, for combined and separate node types.

Table 4. System Configuration Limits - Aspect Server Parameter Limits

AS+CS+AO AS+CS
AS+CS+(AO) AS and CS
no server no server
Parameter (max numbers) with server separate
based based
based client
clients clients
DA Subscriptions Reads / 50 per sec. 50 per sec. 50 per sec. 50 per sec.
Aspect Object(1)
DA Subscriptions Writes / 1 per sec. 1 per sec. 1 per sec. 1 per sec.
Aspect Object(1)
Continuous alarm/event 10 10 20 30
throughput/second
Event burst (events per 200 per CS 200 per CS 200 per CS 200 per CS
100ms) applied to one maximum maximum maximum maximum
Controller
Event burst (events evenly 600 total over 3 1.000 total 1.600 total 1.000/s for
distributed over controllers) sec. over 3 sec. over 3 sec. 3 sec.,
plus 10/s for
15 minutes
Event burst recovery time, 60 sec.
1000 events evenly
distributed
(1) Aspect Server properties that only exist in the Aspect Server.

26 3BSE041434R4101
Section 1 System 800xA Configuration Rules Summary

Table 5. System Configuration Limits - Alarm Parameter Limits

AS+CS+AO AS+CS
AS+CS+(AO AS and CS
no server no server
Parameter (max numbers) ) with server separate
based based
based client
clients clients
Total numbers of displayed alarm 10 10 10 30
lists, per system
Displayed alarm lists, including 4 4 4 4
alarm line, per client
Alarm band buttons per system 25 25 25 75
Alarm band buttons per client 5 5 5 5
External Alarms 10 10 10 10

Connectivity Server OPC DA/AE Rules

Table 6 details the limits in Connectivity Server OPC DA/AE rules when combined
and separate node types are used. These numbers reflect what the base system can
support. Each connect option will be equal to or less than these numbers.

Table 6. Configuration limits per Node for Connectivity Server Parameters

AS+CS+AO AS+CS
AS+CS+(AO)
no server no server AS and CS
Parameter (max numbers) with server
based based separate
based client
clients clients
Number of Active OPC DA 1.000 6.000 6.000 20.000 / CS(1)
Subscriptions
Average OPC DA 100 600 600 2000 / CS
Subscription Rate per
second
Average OPC DA 200 1.200 1.200 4.000 / CS
Subscription Burst Rate per
second
OPC AE Event burst (events 200 200 200 200 / CS
per 100ms)

3BSE041434R4101 27
Configuration Rules Summary Section 1 System 800xA

(1) This number is based on 5000 History Sources with parallel redundancy which has a 1 to 4
loading ratio if enabled and includes History subscriptions.

Control and I/O Rules

Table 7 details the limits in Control and I/O size when combined and separate node
types are used.

Table 7. System Configuration limits - Control and I/O Parameters

AS+CS+AO AS+CS
AS+CS+(AO)
no server no server AS and CS
Parameter (max numbers) with server
based based separate
based client
clients clients
AC 800M Controllers 3 5 8 75
AC 800M Controllers per N/A N/A N/A 12 per CS
separate CS (single or
redundant)
AC 800M Connectivity 1(2)(1) 1(2)(2) 1(2)(2) 8(16)
Server node
CLPs (Control License 2.500 4.200 6.500 75.000
Points)(2)
I/O Channels 1.800 3.000 4.800 45.000
Field devices FOUNDATION 500 960 960 960 per CS
Fieldbus
Field devices PROFIBUS 250 500 500 1.000 per CS
Field devices HART 250 500 500 1.000 per CS
(2) 1(2)(2) 2(4)(3)
Fieldbus Connectivity Server 1(2) 8(16)
nodes
(1) In combined node.
(2) Calculated number of variables connected and downloaded to controller.
(3) 1(2) in combined node, 1(2) additional.

28 3BSE041434R4101
Section 1 System 800xA Configuration Rules Summary

Table 8. System Configuration limits - Application Servers

AS+CS+(AO) AS+CS+AO AS+CS
Parameter (max AS and CS
with server no server no server
numbers) separate
based client based clients based clients
Application Server No Batch/ max 5 max 6 max 10
nodes in one system IM/MM, AO 1 Batch/IM/MM 1 Batch/IM/MM 1(2) red. Batch
built in or or 6 IM, 1 MM
1(2) Batch, 1+1 1(2) Batch, 1+1 4 AO,
(dual) IM, 1 MM (dual) IM, 1 MM 2 other
AO built in 1 AO, application
1 other 1 other server
application application
server server

Application Rules
Table 9 details the limits in system configuration for application specific parameters
when combined and separate node types are used.

Table 9. Configuration limits per Node for Application Parameters

AS+CS+AO AS+CS Separate
AS+CS+(AO)
no server no server AS, CS and
Parameter (max numbers) with server
based based Application
based client
clients clients Servers
PPA History
Number of Data Sources 250 1.500 1.500 5.000
Number of History Logs 250 1.500 1.500 10.000
OPC DA Items 250 1.500 1.500 5.000
No Redundancy
OPC DA Items with 250 / 500 1.500 / 3.000 1.500 / 3.000 5.000 /
Redundancy / with 10.000
Parallel Enabled
Average OPC DA 50 300 300 1.000
Subscription Rate per
second

3BSE041434R4101 29
Configuration Rules Summary Section 1 System 800xA

Table 9. Configuration limits per Node for Application Parameters (Continued)

AS+CS+AO AS+CS Separate
AS+CS+(AO)
no server no server AS, CS and
Parameter (max numbers) with server
based based Application
based client
clients clients Servers
Average OPC DA 100 600 600 2.000
Subscription Burst Rate
per second
Average HDA Request 50 300 300 1.000
per Minute
Average HDA Values per 200 1.200 1.200 4.000
Second
Burst HDA Values per 400 2.400 2.400 8.000
Second
Information Management History
Number of History Logs 250 1.500 1.500 30.000
Average HDA Request 50 300 300 1.000
per Minute
Average HDA Values per 200 1.200 1.200 4.000
Second
Burst HDA Values per 400 2.400 2.400 8.000
Second
Average Alarm retrieval 10 10 20 30
per second from Aspect
Server
History Collection HDA 50 300 300 1.000
Retrieval Rate per Minute
Scheduling Service
Simultaneous jobs, 200 200 200 200
maximum
Calculations
Number of Services 1 1 1 10
Write transactions / 10 10 10 10
second to AC 800M

30 3BSE041434R4101
Section 1 System 800xA Available Functions

Table 9. Configuration limits per Node for Application Parameters (Continued)

AS+CS+AO AS+CS Separate
AS+CS+(AO)
no server no server AS, CS and
Parameter (max numbers) with server
based based Application
based client
clients clients Servers
Write transactions / 100 100 100 100
second to Softpoint
objects
Softpoint Service
Number of Objects 25 75 75 2.500
Number of Signals, 250 750 750 25.000
maximum
OPC Clients (800xA OPC Client Connection)(1)
Maximum Number of 250 500 500 2.000
OPC-items to a Client
Number of OPC-items 25 25 25 100
changing/second via afw
OPC
Batch Management
Batch Active phases 60 60 - 100(2) 60 - 100(1) 300
Asset Optimization
Assets Monitors(3) 2.000 2.000 10.000 10.000

(1) Under evaluation. Contact technical sales.

(2) Depending on Batch/IM/MM server configuration. See Table 28
(3) Max. 30 000 Asset conditions per AO server.

Available Functions
This section specifies which system functions that can be used with which controller
connectivity. Most of the system functions are verified with most of the controller
connectivities. Some functions may though intentionally not be supported by a
certain controller connectivity.
Combinations not specified in Table 10 are either not meaningful, will not work due
to not supported functionality, or can not be guaranteed to work since no tests have
been performed to verify the function.

3BSE041434R4101 31
Available Functions Section 1 System 800xA

See also the System 800xA Feature List, 3BSE038976 in ABB Library.

Table indications:
x = supported
- = not supported.

Table 10: Available Functions per Controller Connectivity

System 800xA with(1)

Advant Master

800xA for DCI

PLC Connect
Item
Safeguard
800xA for

800xA for

800xA for

800xA for
Harmony

MOD 300
AC 800M
Connect

Melody

Number Licensed Functions Comments

and

B010 xA Core System x x x x x x x Must always be selected

B020- 100, 1000, 10000 x x x x x x x Not to be used together with

B040 tags non-redundant B050-B070.

B050- 100, 1000, 10000 x x x x x x x Redundant Connectivity Server

B070 tags redundant requires redundant tags. Not to be
used together with
B020-B040.

B110 800xA for Advant x x - - x - - Can only be combined with

Master AC 800M Connect and
PLC Connect

B115 800xA for MOD 300 x - - - x x - Can only be combined with

AC 800M Connect and
PLC Connect

B120 800xA for Harmony x - x - x - - Can only be combined with

AC 800M Connect and
PLC Connect

B130 800xA for Melody - - - x - - - Can not be combined with any

other connectivity

B135 800xA for DCI x - - - x - x Can only be combined with

AC 800M Connect and
PLC Connect

32 3BSE041434R4101
Section 1 System 800xA Available Functions

Table 10: Available Functions per Controller Connectivity (Continued)

System 800xA with(1)

Advant Master

800xA for DCI

PLC Connect
Item

Safeguard
800xA for

800xA for

800xA for

800xA for
Harmony

MOD 300
AC 800M
Connect

Melody
Number Licensed Functions Comments

and
s

B140 PLC Connect x x x - x x x Can only be combined with

AC 800M Connect and
800xA for-, Advant Master,
Safeguard, Harmony, DCI and
MOD 300

B150 PLC Connect Dial-Up x x x - x x x Can only be combined with

AC 800M Connect and
800xA for-, Advant Master,
Safeguard, Harmony, DCI and
MOD 300

B160 PLC Connect x x x - x x x Can only be combined with

IEC60870-5-101/104 AC 800M Connect and
Protocol 800xA for-, Advant Master,
Safeguard, Harmony, DCI and
MOD 300

B170 800xA for Safeguard x x - - x - - Requires 800xA for Advant Master

B210 800xA OPC-Client x x x x x x x

Connection

B220 OLE-DB Real Time x x x x x x x

Data-Client
Connection

B310 Audit Trail x x x x x - -

B320 Advanced Access x x x x x - x

Control

B330 Digital Signature x x - - - - -

B340 SMS and e-mail x x x x x x x

Messaging

B350 Calculation Engine x x x x x x x

C010 Operator Workplace x x x x x x x 1 license required for each running

(Client) client

C020 Operator Workplace x x x x x x x 1 license required for each running

(Remote Client) client

D007 Small Batch x - - - - - -

D010 Batch Server x - - - - - - Must not be used with D020

3BSE041434R4101 33
Available Functions Section 1 System 800xA

Table 10: Available Functions per Controller Connectivity (Continued)

System 800xA with(1)

Advant Master

800xA for DCI

PLC Connect
Item

Safeguard
800xA for

800xA for

800xA for

800xA for
Harmony

MOD 300
AC 800M
Connect

Melody
Number Licensed Functions Comments

and
s

D020 Batch Server x - - - - - -

Redundant

D030 Batch Client x - - - - - - Requires D010 or D020.

1 license required for each running
client. Requires Item C010, C020,
or G010.

D040 Batch Schedule x - - - - - - Requires D010 or D020.

Interface

D050 10 Batch Equipment x - - - - - - Requires at least one of D010,

D020 or D070.

D060 100 Batch x - - - - - - Requires D010 or D020.

Procedures

D070 100 Batch Advanced x - - - - - - Requires D050.

Phases

D210 Manufacturing x - x - x x x
Management Server

D220 Manufacturing x - x - x x x Requires Item C010 or C020 or

Management Client G010. The total number of D030
and D220 should not exceed the
allowable 800xA client maximum.

D230 Inventory x - x - x x x Requires D210

Management

D240 Weigh and Dispense x - x - x x x Requires D210 and D230

D250 Quality Management x - x - x x x Requires D210 and D230

D260 Operations x - x - x x x Requires D210

Management

E010 Basic Historian x x x x x x x Batch reports with trending require

Server items E510 and E520.

E110- 100, 1000, 15000 x x x x x x x Requires E010.

E130 History Logs

E210- 100, 1000, 15000 x x x x x x x Requires E010.

E230 Dual History Logs

34 3BSE041434R4101
Section 1 System 800xA Available Functions

Table 10: Available Functions per Controller Connectivity (Continued)

System 800xA with(1)

Advant Master

800xA for DCI

PLC Connect
Item

Safeguard
800xA for

800xA for

800xA for

800xA for
Harmony

MOD 300
AC 800M
Connect

Melody
Number Licensed Functions Comments

and
s

E310- 100, 1000, 15000 x x x x x x x Requires E010. Requires

E330 Consolidated History E110 - E130 or E210 - E230.
Logs

E410 Display Builder for x x x x x x x Requires E010.

MDI Client

E420 Multi-Display x x x x x x x Requires E010.

Interface (MDI) Client

E430 Desktop Trends x x x x x x x Requires E010.

E440 Excel Data Access x x x x x x x Requires E010.

E510 ODBC Historical Data x x x x x x x Requires E010.

Server

E520 ODBC Client x x x x x x x Requires E510

Connection

E530 OLE-DB Historical x x x x x x x Requires E010

Data Server

E540 OLE-DB Client x x x x x x x Requires E530

Connection

F010 100 AC 800M Control x - - - - - -

Software Integration
CLPs

F040 SoftController x - - - - - -

F120 100 AC 800M High x - - - - - -

Integrity Control
Software Integration
CLPs

F160 AC 800M High x - - - - - - Requires F010 and F120

Integrity and Process
Control

G010 Engineering x x x x x x x
Workplace - Rich
Client

G110 Script Manager x x x x x x x

Professional

3BSE041434R4101 35
Available Functions Section 1 System 800xA

Table 10: Available Functions per Controller Connectivity (Continued)

System 800xA with(1)

Advant Master

800xA for DCI

PLC Connect
Item

Safeguard
800xA for

800xA for

800xA for

800xA for
Harmony

MOD 300
AC 800M
Connect

Melody
Number Licensed Functions Comments

and
s

G120 Reuse Assistant x - - - - - -

G130 Library Assistant x - - - - - -

G133 Process Engineering x - - - - - -

Tool Integration -
Base for INtools

G135 Process Engineering x - - - - - -

Tool Integration -
New Object Creation
Support for INtools

G140 Aspect Express x x x x x x x

G210 Aspect Studio x x x x x x x

H010 100 Asset Monitoring x x x x x x x

H020 PC, Network and x x x x x x x

Software Monitoring

H030 Maximo Integration x x x - x x x

H040 DMS Calibration x x x - x x x

Integration

H050 SAP/Plant x x x - x x x
Maintenance
Integration

K010 100 Devices using x x x - - - x

HART Device
Integration

K015 HART Multiplexer x x x - - - x Requires K010. AC 800M

Connect supported, but preferred solution
is to use integrated tool routing
function. AC 800 M High Integrity
is not supported

36 3BSE041434R4101
Section 1 System 800xA Available Functions

Table 10: Available Functions per Controller Connectivity (Continued)

System 800xA with(1)

Advant Master

800xA for DCI

PLC Connect
Item

Safeguard
800xA for

800xA for

800xA for

800xA for
Harmony

MOD 300
AC 800M
Connect

Melody
Number Licensed Functions Comments

and
s

K020 100 Devices using x - - - - - -

FOUNDATION
Fieldbus Device
Integration

K030 100 Devices using x - - - - - -

PROFIBUS Device
Integration

(1) For AC 100 Connect, please refer to the AC 100 Connect Product Guide.

3BSE041434R4101 37
Third Party Hardware and Software Section 1 System 800xA

Third Party Hardware and Software

PC Recommendations for System 800xA
System 800xA is verified with a defined set of workstations and servers. Supported
PCs, and communication hardware, are listed in "Third Party HW products verified
for IndustrialIT System 800xA", 3BSE034719, that can be found in ABB Library.
The document is continuously updated, when new hardware is approved for use
with the system.
To safeguard the quality of the system, all recommended PC hardware are tested by
ABB before approval. This means that all models on the recommendation list have
been installed and run with relevant system functions in our tests. If there for any
reason is a need to use a non-recommended hardware, this has to be approved by the
System 800xA Product Management, as well as any functional requirement on the
system.
Generally, Level 3 or Level 4 problem support for systems based on non-supported
hardware will be charged, above and beyond any maintenance contracts, if the
problem is related to the non-supported hardware.

Supported Operating Systems

System 800xA SV 4.1 supports the following operating systems:
- Windows XP Professional for clients and servers
- Windows 2003 Server for server nodes
- Windows 2000 Server for server nodes when upgrading from earlier system
versions
See Configuration Rules on page 15 for details.

Other third party software

Each version of the System 800xA is verified with particular versions and revisions
of underlying third party software. It is very important that the correct versions of
the software is used. Normally the System Installer will verify the correctness of the
third party software.

38 3BSE041434R4101
Section 1 System 800xA Core System

A complete list of third party software used can be found as an appendix in the
System Installation Users Manual. Since there may be updates to this list in between
system releases, an updated version of the list, “800xA Third Party Software for
4.1”, 3BSE039230R4101 can be found in ABB Library.

Core System

Redundancy Switchover Time

The switchover times for redundant Connectivity Server and Aspect Server (1oo2)
are shown in Table 11

Table 11. Redundancy Switchover Time

Parameter Data
Switchover time Connectivity Server < 1 sec.
Switchover time Aspect Server 1oo2 2 - 4 sec.

Scheduling Service
The maximum scheduling capacity is 200 simultaneous jobs per scheduling server.

Softpoint Service
The Softpoint Server can have up to 2.500 softpoint objects. Each softpoint object
can have up to 100 signals; however, the total number of signals cannot exceed
25.000. Softpoint Server redundancy is also supported.
CPU time for each read or write transaction is one millisecond. The Softpoint server
can write 10 events per second to platform-based Aspect Objects.

3BSE041434R4101 39
Core System Section 1 System 800xA

Calculations

Table 12. Calculations Parameters

Parameter Description
OPC Base Rate Rate at which input variables are updated by
their respective OPC data sources.
Range: 100 milliseconds to 1 hour
Default: 1.000 milliseconds (1 second)
Cycle Base Rate Rate at which the Calculations Scheduler scans
the list of cyclically scheduled calculations.
Range: 100 milliseconds to 1 hour
Default: 500 ms (1/2 second)
Number of calculations that may 10.000 Maximum
be queued waiting to be
executed
Execution Rate 100 calculations/second, see write transaction
rates specified below to determine capabilities
Write transactions/second The Calculation server can write up to 10
values/second to process (AC 800M) objects.
Write transaction/second to The Calculation server can write up to 100
softpoints values/second to process softpoint objects

40 3BSE041434R4101
Section 1 System 800xA Control Network Clock Synchronization

Control Network Clock Synchronization

Table 13 shows the clock synchronization accuracy based on the type of control
network,

Table 13. Control Network Clock Synchronization

Type of Clock Synchronization Accuracy per node
High Precision SNTP 1 ms
SNTP 200 ms
CNCP (between AC 800M) 1 ms
CNCP (AC 800M to AC 800C/Advant Controller 250) 200 ms
CNCP (AC 800M to PPA) 200 ms
MB300 network 3 ms

AC 800M Connect Performance

Connectivity Server Throughput
The capacity in number of OPC-items and OPC item change rate/second through an
AC 800M Connectivity Server is shown in Table 14.

Table 14. Connectivity Server throughput

AS+CS+(AO) AS+CS+AO AS+CS AS and
Parameter with server no server no server CS
based client based clients based clients separate
Max numbers of 7.000 12.000 15.000 30.000
subscribed OPC items per CS
Max change 200 400 500 1.000
rate/second per CS

3BSE041434R4101 41
Display Call-up Time Section 1 System 800xA

Display Call-up Time

The OPC Server for AC 800M collects data from controllers via MMS, and makes it
available to OPC clients. The table below shows the display exchange time of a
process display containing 100 objects.

Table 15. Display Call-up Time for Displays

Graphic Displays Display Call-up Time
Graphic Display with 100 objects (800 OPC items) ≤ 2 sec.
Faceplate ≤ 1 sec.
Extended Faceplate ≤ 2 sec.
Trend Display, at first call-up of trend with 10 variables 3 - 4 sec. typical

Command Response Time

The Command response time is given as two values, one being the time from
command in a faceplate until an I/O signal reacts in the controller, and the other
from command in a faceplate until the feedback indication shows up on the
faceplate. All values are first time call-up, and with Audit Trail off. Audit Trail on
adds another 0.5 - 1 sec.

Table 16. Command Response Time

Response Time
Measurement
(Average)
Command to I/O ≤ 1 sec.
Command to indication ≤ 2 sec. typical

42 3BSE041434R4101
Section 1 System 800xA Information Management

Information Management
PPA History Capability
The History Capabilities are related to connectivity servers.

Table 17. PPA History Capability

Capability Capacity
Maximum average log values written to disk per 500/second
connectivity server
Maximum number of primary logs per connectivity 5.000
server
Maximum retention period (buffer for history data) 3 months

History Services
The Information Management History Services (Inform IT Service Provider for one
Information Management node) can manage up to 50.000 history logs (combination
of primary and secondary).
In a system the maximum number of history logs is according to Table 2. The
maximum number of history logs supported is dependent on the configured system
including connectivity options, cycle times, and collection rates. Please refer to
Information Management user documentation for further information.

Disk and Memory Capacity Requirements

Table 18. System limits and capabilities - Information Management Server

Capability Capacity
PDL Option - Additional disk capacity 4 GB disk for Batch
Management
PDL Option - Additional memory 256 MB for large
applications
Audit Trail Option - Additional Disk capacity 2 GB additional disk

3BSE041434R4101 43
History Services Section 1 System 800xA

Table 19. System Sizing Examples - Information Management

Number of Disks
Disk
System Requirements (SCSI RAM
Capacity
Recommended)
Base - Includes: 2 15 GB 2GB
1000 TYPE5 History logs
with 1-minute storage rate,
90-day period,
one OPC message log
w/1.000.000 message capacity,
small PDL application
Up to 10.000 TYPE5 Logs(1) 3 50 GB 3 GB
Up to 50.000 TYPE5 Logs 4 200 GB 4 GB
Large PDL Application 4 GB 0.5 GB
Audit Trail 2 GB
Large System - 50.000 logs and all 4 208 GB 4.5 GB
options
(1) TYPE5 Logs are file based logs with variable size.

.
Table 20. Batch and IM Server capacity
Batch and IM Batch and IM Separate
Feature with server no server Batch and
based client based client IM server
Max no. of History logs per server 250 1.500 30.000(1)
Max no. of History data points 6.000 10.000 60.000
logged per minute in IM
Max no. of alarms/messages logged 10 10 30
per second per IM server
Max no. of softpoints objects(2) 25 75 2.500
Max no. of History data points 250 1.500 10.000
collected from one connectivity
server

44 3BSE041434R4101
Section 1 System 800xA History Services

(1) Plus additional 20.000 secondary logs (calculated)

(2) Reference Core System on page 39 for additional details regarding Softpoints and Calculations

Maximum Number of Entries Per Log (Nominal)

Log capacity and number of logs determine tablespace and disk requirements. The
limits indicated in Table 21 should be sufficient for most applications.

Table 21. Entries Per Log

Log Type Entries
TYPE1 - File-based 24-byte 5.000.000
TYPE2 - File-based 4-byte 32.000.000
TYPE3 - File-based 8-byte 16.000.000
TYPE5 - File-based variable size 315.000.000
(10 years of data at 1-second sample rate)
Oracle-based 50.000
OPC Message Logs 12.000.000 per log
Restored Logs Limit based on available restored table space
Report Log 5.000 reports

History Collection Maximum Sample Rate

History Services can collect from different types of data sources, and limitations on
sample rate are imposed based on the type of data source. These limitations are
described in Table 22.

Table 22. Maximum Sample Rates

Collection Type Rate(1)
Numeric data supplied manually and by 350 - 400 values/second
data clients

3BSE041434R4101 45
History Services Section 1 System 800xA

Table 22. Maximum Sample Rates (Continued)

Collection Type Rate(1)
PPA primary log 30.000 logs at 30.000
samples/minute.
Consolidation Node (via TCP/IP) 50.000 logs at 60.000
samples/minute
(1) Actual performance is based on the platform where History software runs, and control system
topology.
Blocking rate and stagger function must be used to balance CPU loading.

Fastest Sample Rate and Timestamp Resolution

TYPE 1,3&5, and Oracle-based logs support microsecond timestamp resolution and
collection at a one-second sample rate. TYPE2 logs can also collect at a one-second
rate; however, they support one-second resolution on timestamps.
Note, that some connectivity servers may not support (be able to provide data at) the
one-second sample rate. Refer to the applicable documentation for your
connectivity server for more information.

Disk Requirements Per Log Entry

Disk space requirements for each History value stored are indicated in Table 23.

Table 23. Bytes Required Per Log Entry

Log Storage Type Bytes Per Entry(1)
TYPE1 file-based 24
TYPE2 file-based 4
TYPE3 file-based 8
TYPE5 file-based 16-32 based on data type (float, double, etc...)
Oracle-based Numeric 110
Message in a message log 250
Restored log entry 100
(1) It is recommended that you leave 5-20% extra capacity for expansion.

46 3BSE041434R4101
Section 1 System 800xA History Services

For example: Disk Space for TYPE1 Log with 1-minute storage interval, and
90-day log period:
1440 samples/day * 90 days = 129,600 samples
129,600 samples * 24 bytes/sample = 3.1 MB per log

History Objects Miscellaneous Capacities

Table 24 describes size limitations for composite logs, log sets, and archive groups.

Table 24. History Object Miscellaneous Capacities

Object Size
Maximum number of Primary and Secondary Logs in a Composite Log 16
Maximum number of Logs in a Log Set 10.000
Maximum number of Logs in an Archive Group 10.000

History Archive
IM supports several methods to move archive information off the IM system. These
options should be evaluated based on the archive data generated by the
configuration.
Disk Archiving:
• Disk archiving requires local disk space to store archive data. Options exist to
create ISO images, volume backups, or both
• ISO images can be burnt to DVD or CDs
• The volume backups are copied to a local or remote destination. From this
location, the information can be backed up with any appropriate method to
transfer the data to the backup medium
Magneto Optical Disk Archiving:
• Supported device: HP SureStore 5200ex Single Magneto Optical Disk. 5.2 GB
per platter (2.6GB/surface) or HP SureStore 9100mx Single Magneto Optical
Disk. 9 GB per platter (4.5GB/surface)

3BSE041434R4101 47
History Services Section 1 System 800xA

• Operation: Disk must be manually removed and turned over to record to

second surface of disk
• Usable Storage/Surface: 2.05 or 4.2 GB
• Storage per numeric history value stored: 21 bytes
• Capacity per side: 97 million or 200 million entries (approximate for numeric
logs)
• Storage per message: Varies from 260 bytes to 4K bytes.
• Capacity per side: 7.8 million or 16 million messages (approximate for
message log)
After volume (one surface) is filled, volume must be changed manually before
buffered archive data exceeds volume capacity.
• With 2.05 GB - approximately 24 hours at 60.000 numeric storages/minute.
Deadband compaction can be used to minimize volume of data stored on-line,
and archived.
• With 4.2 GB - approximately 48 hours at the same storage rate.
Cost considerations for permanent storage of Archive Data.
The amount of archive data generated will result in a certain cost for backing up
archive data. Magneto Optic cartridges are more expensive than CD and DVD
blanks. However, the use of CD/DVD requires a separate step to burn the ISO
image to CD/DVD. If a remote file server is used and the local IT department backs
up the data, the information can be backed up with your organizations IT backup
process. These options should be evaluated based on the configuration
requirements, the data collected, convenience, and the cost per archive.

Display Services MDI (Multiscreen Display Interface)

Table 25. Multiscreen Display Interface

Batch and IM Batch and IM
Separate
Feature with server no server
IM server
based client based client
Total MDI clients in a system 10 15 150

48 3BSE041434R4101
Section 1 System 800xA History Services

Table 25. Multiscreen Display Interface (Continued)

Maximum number of graphic display 6 10 64
clients (MDI/SDI) per Basic Historian
server
Total Excel Data Access clients in a 10 15 150
system
Maximum number of Excel Data Access 6 10 64
clients per Basic Historian server
Supported data rate feeding Multiscreen 200/second nominal
Display Interface.(1)
Maximum size of request returned by Functions:
Excel Data Access 5.460 elements/function call Dialogs:
• History - 500 history values/log
• SQL - 65.536 records
Maximum rate for writing to process 1 value/second
objects
Maximum rate for writing to history logs 5 values/second
(1) Using LastHistoryValue option will minimize the load while providing near-realtime data

Desktop Trends

Table 26. Desktop Trends

Batch and IM Batch and
Separate
Feature with server IM no server
IM server
based client based client
Maximum number of Desktop Trend 10 15 150
clients in a system
Maximum number of Desktop Trend 6 10 64
clients per Basic Historian Server
Maximum number of trends on a trend 8 traces
display
Maximum number of tags per Tag 50 tags
Explorer Group

3BSE041434R4101 49
Batch Management Section 1 System 800xA

Table 26. Desktop Trends (Continued)

Batch and IM Batch and
Separate
Feature with server IM no server
IM server
based client based client
Maximum number of tags per Ticker file 50 tags
Maximum number of concurrent trend 4
controls on one client
Trend display call-up from local 15 seconds or less
Information Management server with
eight trends

ODBC Client and OLE-DB Client

Table 27. ODBC Client and OLE-DB Client

Characteristic/
Feature
Value
Maximum number of ODBC-Client Connections in a system 60
Maximum number of ODBC-Client Connections per ODBC 10
Historical Data Server
Maximum number of OLE-DB-Client Connections in a system 60
Maximum number of ODBC-Client Connections per OLE-DB 10
Historical Data Server

Open Data Access - Excel Data Access

Each ODA server supports up to 20 concurrent client connections. The maximum
number of values for one query against History is virtually unlimited; however,
large queries may cause the client application (Crystal Reports or Microsoft Excel)
to time out.

Batch Management
Table 28 details the capacities of Batch Management features.

50 3BSE041434R4101
Section 1 System 800xA Batch Management

Table 28. Batch Capacities

Batch and IM with Batch and IM no
Separate Batch
Feature server based server based
server
client client
Active Equipment(1) 30 50 100
(1)
Active Phases 60 100 300
Procedure Execution(1) 30 procedure block transitions/second(2)
Batch display call-up(1) 2 seconds typical
(1) All times and rates are typical and dependent on the connected system configuration and
system load.
(2) Transition means the completion of one procedure block until the start of the next procedure
block (for blocks that do not access the OPC server)

Table 29 details AC 800M RAM usage for the Batch Advanced Templates library.

Table 29. AC 800M RAM usage for BatchAdvTemplatesLib

Module Type(1) (Kb) Instance (Kb)

(2)
Unit 73 7.5
Unit Attribute String(3) 0.7
Unit Attribute Float(3) 0.5
Unit Attribute Integer(3) 0.5
SEM with Server Comm Module(2) 78 12
SEM Attribute String(3) 0.7
SEM Attribute Float(3) 0.5
SEM Attribute Integer(3) 0.5
SEM Server Ext Comm Module 80 8.5
SEM Client Comm Module 77 10.5
Phase(2) 54 7.5
Phase Parameter String(3) 0.7
Phase Parameter Float(3) 0.5
Phase Parameter Integer(3) 0.5
AE Named Value Item Numeric 0.1
AE Named Value Item String 0.17

3BSE041434R4101 51
Manufacturing Management Section 1 System 800xA

(1) Memory for type is allocated by the first existing instance in the controller, and is reused by all
subsequent instances within the same controller.
(2) These estimates are based on modules as delivered in BatchAdvTemplatesLib templates (i.e.
no user logic).
(3) The estimates for attribute and parameter modules assume that all ranges and description are
configured to the maximum size.

Manufacturing Management
Table 30 details the capacities of the Manufacturing Management features.

Table 30. Manufacturing Management Capacities

Feature Characteristic/Value
Materials Limited by database capacity, maximum of 5.000
recommended.
Lots, Active Limited by database capacity, maximum of 5.000
recommended.
Lots, Inactive Limited by database capacity, maximum of 10.000
recommended.
Sub Lots, Active Limited by database capacity, maximum of 50.000
recommended.
Sub Lots, Inactive Limited by database capacity, maximum of 50.000
recommended.
IForms, Configured Limited by database capacity, maximum of 1.000
recommended.
IForms, Running Limited by server processing capacity. Dual-processor
server can typically support 50 simultaneous IForms.
Reports Number of configured reports are limited only by the
amount of available hard disk drive space.
Security Standard 800xA System access configuration using batch
specific aspects.
Batch ID, Lot ID Recommended maximum of 31 characters combined from
following set (A-Z, a-z, 0-9, _). Physical maximum of 128
characters.

52 3BSE041434R4101
Section 1 System 800xA Asset Optimization

Asset Optimization
Asset Monitoring Engines provide the execution environment for Asset Monitors.
The startup time for Asset Monitoring Engines is dependent on the size and
configuration of the 800xA System. Factors affecting startup time include the
number of Asset Monitor conditions and the number of Aspect Server nodes.
• Asset Optimization supports a maximum of 10.000 Asset Monitors per 800xA
system.
• Asset Optimization supports up to four Asset Optimization Servers per 800xA
system.
• An Asset Optimization Server can support up to 30.000 Asset Monitor
conditions.

PC, Network and Software Monitoring (PNSM)

The recommended maximum capacity for a single PC, Network and Software
Monitoring Connectivity Server is 1.000 live monitored items (properties). A
typical example would be a large 800xA system (up to 30 nodes, plus 2 printers and
2 switches), although the actual performance will vary according to the
configuration. E.g. if more 'light' asset types are being used, more asset can be
monitored with the same performance. Systems significantly larger than this may
require additional PNSM Connectivity Servers.
For large configurations, it is recommended that PNSM server runs on its own
Connectivity Server node (or nodes), i.e. not in the same node as AC 800M
connectivity software, whereas for smaller configurations, the PNSM server may
run in the same combined node.

Fieldbus

FOUNDATION Fieldbus Configuration Rules

The FOUNDATION Fieldbus basic layout rules are given in the following table.

3BSE041434R4101 53
Fieldbus Section 1 System 800xA

Table 31. FOUNDATION Fieldbus basic layout rules

HSE (High Maximum CI860 throughput 500 signals per second

Speed Maximum number of signals 1.000 signals overall out of:
Ethernet) - max 1.000 for analog input
- max 500 for analog output
- max 500 for discrete input
- max 250 for discrete output
Maximum no. of CI860 at CEX Bus 6
Maximum number of Linking Devices 15
per HSE Subnet
H1 Maximum no. of devices per H1 Link 16 (application dependent)(1)
Maximum no. of signals in total 70
between one H1 Link and HSE
Maximum no. of signals per second 20
per H1 link between H1 and HSE
(1) FOUNDATION Fieldbus recommendations for H1 segment layout is maximum 12 devices with
up to 4 valves.

Fieldbus OPC Server

The figures below are valid for the Fieldbus OPC Server.

Table 32. Capacity Figures for the Fieldbus OPC Server

Maximum number of Connectivity Servers with Please refer to Table 7

PROFIBUS/HART/FOUNDATION Fieldbus
Device Integration (depends on the maximum
possible number of connectivity servers in total)
Maximum number of HSE Subnets per =1 (1:1 relationship)
Connectivity server
Maximum number of field devices per Please refer to Table 7
Connectivity Server FOUNDATION Fieldbus (application dependent)

54 3BSE041434R4101
Section 1 System 800xA System Configuration Examples

Table 32. Capacity Figures for the Fieldbus OPC Server (Continued)

Maximum number of field devices per Please refer to Table 7

Connectivity Server PROFIBUS
Maximum number of field devices per Please refer to Table 7
Connectivity Server HART

System Configuration Examples

In the following two examples the “rules” defined above are applied to determine
how to configure a system optimized on number of nodes.

Example 1
The following requirements are assumed. See also Figure 9
• 5 Operator workplaces, one of which is also used as engineering workplace
• 600 Tags
• Batch
• IM
• 2 AC 800M Controllers
• FOUNDATION Fieldbus with 300 Devices
• 2000 CLP
• Redundancy is required for Aspect and Connectivity Servers

Applying the configuration rules defined in previous sections gives the following:
• To reduce the number of nodes a 1oo2 redundant combined Aspect and
Connectivity server (AS+CS) is used.
• Since Batch redundancy is not required, it is also possible to use a combined
Batch and IM server (Batch+IM).
• 2 AC 800M controllers are below the max number of controllers that can be
connected to a combined AS+CS node (≤8).

3BSE041434R4101 55
System Configuration Examples Section 1 System 800xA

• 300 FOUNDATION Fieldbus Devices, 2.000 CLP’s, and 600 tags are all below
the maximum numbers allowed for combined AS+CS node. (Max is 960
devices, 6.500 CLP’s and 5.000 Tags.)
Number of nodes needed
• 1 redundant pair of servers AS+CS. These nodes also serve as two Client
nodes.
• 1 combined Batch+IM Server, also serving as one Client node.
• 2 additional clients (one of which is also used as engineering workplace)
This sums up to a total of 5 nodes.
Domain or Workgroup
If the system is configured as a domain, an additional node (two for redundancy) is
required for the Domain Server. A relatively small configuration like this may work
well as a workgroup, however, if the system is later expanded with more computers
and more users, the workgroup will become increasingly difficult to administrate.
Operating System
The operating system on all nodes except the Batch/IM node may be Windows XP
Professional. The Batch+IM server requires Windows Server.
The Figure 9 illustrates the node layout for the system specified in this example.

Domain Server Aspect Server Batch Server

Conn. Server IM Server Client
2 * Client Client

S 1oo2 XP 1oo2 S xxxx XP xxxx

Figure 9. Configuration according to Example 1

56 3BSE041434R4101
Section 1 System 800xA System Configuration Examples

Example 2
The following requirements are assumed:
• Number of seats
– 21 workplaces. All of these shall be operator workplaces, 8 of them shall
also function as engineering workplaces
– 5 Remote workplaces
• Functionality
– Batch
– Information Manager
– Asset Optimization
• Size
– 52.000 Tags
– 15 AC 800M Controllers
– 2 Harmony Controllers
– FOUNDATION Fieldbus with 2.500 Devices
– 60.000 CLP’s
• Redundancy is required for all server functions (except AO)
Applying the configuration rules defined in previous sections gives the following:
• This system size must be built with basic node types, i.e. combined node types
can not be used.
• 2oo3 redundant Aspect Servers are selected.
• Fifteen AC 800M controllers require two redundant pair of Connectivity
Servers (max 12 controllers per CS). These connectivity servers can also
handle 960 FOUNDATION Fieldbus devices each (AC 800M and
FOUNDATION Fieldbus connect services can be combined in the same CS,
and the redundant pair counts as logically one server).
• One additional connectivity server is needed to handle the remaining 580
FOUNDATION Fieldbus devices.

3BSE041434R4101 57
System Configuration Examples Section 1 System 800xA

• Two Harmony controllers require one separate redundant pair of Connectivity

Servers.
• One redundant pair of Batch Server is needed
• One pair of IM Server is needed
• One AO Server is needed
• 21 workplaces require 21 client nodes, the system size is too large for using
server based clients. Eight of these client node are also used as engineering
workplaces
• Five remote clients require one Remote Client server.
Domain or Workgroup
A system this size is practically impossible to manage and maintain as a workgroup.
A redundant Domain Server is needed.
Number of nodes needed
2 Domain Servers
3 Aspect Servers
2 AC800 M + FOUNDATION Fieldbus Device Connectivity Servers
2 FOUNDATION Fieldbus Device Connectivity Servers
2 Harmony Connect Servers
2 Batch Servers
2 IM Servers
1 AO Server
21 Client nodes
1 Remote Client Server
5 Remote Clients.
-------------------------
43 nodes in total
Operating System
All server nodes require Windows Server, since the number of nodes exceeds 11.
Client nodes run Windows XP.

58 3BSE041434R4101
Section 1 System 800xA System Configuration Examples

Figure 10 illustrates the node layout for the system specified in this example.

Client

XP 1oo2

2 21

Domain Aspect Server IM Server Client Remote Client

Server Server

S 1oo2 S 2oo3 S xx XP 1oo2 S 1oo2

2
Batch Server AO Server Conn. Server, Conn. Server Conn. Server,
FF + FF
AC800M AC800M
FF + FF Harmony

S 1oo2 S 1oo2 S 1oo2 S xxxx

1oo2 S (1oo2)

Figure 10. Configuration according to Example 2, 43 nodes

3BSE041434R4101 59
System Configuration Examples Section 1 System 800xA

60 3BSE041434R4101
 Section 2 Control and I/O

Control and I/O

This section presents performance and technical data for Control Software and
Control Builder M key functions, configuration and items. For this data to be valid,
the prerequisites and requirements given below must be fulfilled.

Late changes might affect performance and/or functionality. For information on

late changes and restrictions on the use of the product, please refer to the Release
Notes.

Memory

Memory size
The total physical memory except the executing firmware is called “Memory size”
by the function block “SystemDiagnostics”. This amount of memory is sometimes
also called the “heap”.
The memory usage is also displayed in the dialog “Heap Utilization” which can be
displayed for each controller. The available memory is called “Non-Used Heap” and
the rest is called “Used Shared Heap”.

3BSE041434R4101 61
Memory Section 2 Control and I/O

Spare
(20-50%)
Available Memory
“Non-used heap”

Max Memory Size

Used “Heap”
Shared
Heap 8-32 MB
Empty Project RAM
Used
Shared
Heap
Used by Firmware

Executing Firmware

Figure 11. The memory organization

Available memory
The amount of available memory in the controller decreases when the controller has
started up, and an empty project has been downloaded from the Control Builder M.
The remaining memory is what can be used for application code, and is hereafter
referred as to “Available memory”. See Table 33

Execution Performance
The PM860 and PM861/PM861A processor units have the same internal design and
the same performance when executing application program.
The PM851, PM856 and PM860 processor units have the same internal design.
They differ only in performance when executing an application program. The
execution time in PM851 and PM856 is approximately twice the execution time in
PM860.
The PM864 and PM865 processor unit, in single configuration, has performance
data which theoretically peaks at twice the performance compared to the PM860.
The useful sustained performance improvement is, however, a bit lower and

62 3BSE041434R4101
Section 2 Control and I/O Memory

dependent on the actual application program, but can be expected to be 10 to 50%

higher compared to PM860. The difference in execution performance is dependent
on how much CEX buss accesses, and how much communication is running in the
controller (both communication running as CEX buss interfaces and communication
running on the built in ports on the CPU i.e. ModuleBus Ethernet and RS-232).
CEX buss access and communication decreases execution performance.
In a redundant configuration the execution performance is lower than in a single
configuration (typical less than 10%).
The execution performance of an AC 800M High Integrity controller is 60-70% of
an AC 800M Process Automation controller (PM865).
The number of code tabs used in SIL 2 applications has greater influence to the
performance of an AC 800M High Integrity controller compared to the performance
of an AC 800M Process Automation controller. However, the memory
consumptions of function blocks and control modules are the same on both
controllers. An AC 800M High Integrity Controller running non-SIL applications
has performance comparable to an AC 800M Process Automation controller
(PM864 or PM865). See Table 33

Table 33. Available RAM Memory and Performance in Controller

AC 800M

Execution Firmware and Available

Total RAM
Controller Performance an Empty Project Memory
(MB)
Factor (kbytes) (kbytes)
PM851 0.50 8 5.356 2.836
PM856 0.50 8 5.356 2.836
PM860 1.00 8 5.356 2.836
PM861 1.00 16 7.768 8.616
PM861A 1.00 16 7.768 8.616
PM864 1.10 - 1.50(1) 32 7.807 24.961
PM864A 1.10 - 1.50(1) 32 7.812 24.956

3BSE041434R4101 63
Spare Memory Needed for Online Changes Section 2 Control and I/O

Table 33. Available RAM Memory and Performance in Controller

AC 800M (Continued)

Execution Firmware and Available

Total RAM
Controller Performance an Empty Project Memory
(MB)
Factor (kbytes) (kbytes)
PM865 (PA) (1.10 - 1.50)(1) 32 7.780 24.988
PM865 (HI) (0.7 - 1.05)(1) 32 8.395 24.373
(1) The difference in execution performance is dependent on how much CEX buss accesses, and
how much communication is running in the controller. The more CEX buss accesses and
communication the lower execution performance. The more IEC 61131 execution the higher
performance

Spare Memory Needed for Online Changes

As a general rule, an application should never exceed half the size of the available
memory. The reason for this is the manner in which applications are updated online.
1. The modifications (the difference between the old and the updated application)
are downloaded to the controller memory.
2. A new version of the application is created in controller memory, based on the
old application and the modifications.
3. The controller switches from the old to the new application.
4. The old application is deleted.
This technique handles all updates in a very controlled and efficient way. As a
minimum, free memory equal to the size of the largest application is required. If an
application comes close to this limit, it should be divided into two parts so that they
can be updated separately.

One Application in the Controller

There must be spare memory in the available memory in order to be able to make
on-line changes. The amount of spare memory must be at least 20% of available
memory, and may require up to 50%.

64 3BSE041434R4101
Section 2 Control and I/O Comparing Memory Allocations Made with Different Versions

A minimum of 20% spare available memory may be sufficient, depending on a

number of factors, such as the complexity of the application and the number of
defined alarms.
The function block “SystemDiagnostics” reports used memory based on the
memory size, not on the available memory, but the dialog “Heap Utilization” will
show the available memory as “Non-Used Heap”

The function block SystemDiagnostics also presents another figure: the “Maximum
used memory”. This figure is presented in actual bytes, and as a percentage of the
memory size. This figure is far more useful to look at when determining how close
you are to being unable to make on-line changes. Several on-line changes must be
made in order to catch the maximum memory need in the controller.
It is still possible to make on-line changes as long as the maximum used memory
value is less than 100%.

More than one Application in the Controller

Less spare memory is needed when there is more than one application in the
controller.
The on-line changes are done to one application at the time. This means that if
changes are done to more than one application in the controller, these changes will
not take effect in a synchronized way.
Example: One application requires 50% used memory and 70% maximum used
memory. If you split this application into two equally smaller applications, it will
still require 50% used memory, but only 60% maximum used memory, since the
extra memory needed for the on-line changes will be half.

Comparing Memory Allocations Made with Different Versions

From the discussions above, you can see that the “used memory” value provided by
the SystemDiagnostics function block cannot be used to compare different versions.
The amount of available memory in the controller varies between versions for a
number of reasons, one being the number of functions implemented in the firmware.

3BSE041434R4101 65
Memory Consumption and Execution Times Section 2 Control and I/O

Memory Consumption and Execution Times

Memory is reserved for each function block type used in the application. When the
next instance of the same type is created, the amount of memory reserved for the
instance is very small in relation to the type. This means that the memory consumed
by the type itself is of great importance.
The following tables show memory consumption and execution time for AC 800M
PM864A controller and AC 800M PM865 controller with PM865 PA firmware, for
a number of common function blocks and control modules, as well as for a number
of common control loops.
In the tables the First Object column shows the required memory for the object type
and one function block or control module and Next Object column shows the
required memory for every further function block or control module.

Table 34. AC 800M Memory Consumption and Execution Time for Function Blocks
and Control Modules
First Object Next Object PM865
Object
(kbytes) (kbytes) (μs)
Function Blocks
SignalInBool 18.0 5.4 118
SignalOutBool 18.5 4.2 69
SignalSimpleInReal 28.0 4.5 92
SignalInReal 51.2 13.0 305
SignalSimpleOutReal 27.0 3.5 52
SignalOutReal 41.5 10.1 290
AlarmCondBasic 8.4 1.1 30
AlarmCond 8.8 1.2 42
Uni 46.5 7.8 255
Bi 53.7 10.6 325
MotorUni 54.1 9.1 343
MotorBi 67.7 13.7 449

66 3BSE041434R4101
Section 2 Control and I/O Memory Consumption and Execution Times

Table 34. AC 800M Memory Consumption and Execution Time for Function Blocks
and Control Modules (Continued)
First Object Next Object PM865
Object
(kbytes) (kbytes) (μs)
ValveUni 49.6 7.3 401
MCUExtended 97.2 23.5 607
ACStdDrive 76.6 15.1 265
PidSimpleReal 11.8 1.2 101
PidLoop 59.8 5.8 304
PidLoop3P 65.4 6.0 392
PidCascadeLoop 70.1 12.3 492
PidCascadeLoop3P 74.6 12.7 583
Control Modules
DetectorBool 38.5 7.8 162
Detector2Real 72.0 16.5 340
AlarmCondM 8.4 1.7 21
UniM 52.6 8.8 249
BiM 58.7 13.0 318
MotorUniM 60.4 10.7 313
MotorBiM 69.2 14.5 418
ValveUniM 51.1 8.2 221
McuExtendedM 98.2 24.7 505
ACStdDriveM 83.0 17.1 606
AnalogInCC 20.6 11.0 107
AnalogOutCC 17.7 2.9 71
Level2CC 25.8 5.6 88
Level4CC 32.9 9.2 124

3BSE041434R4101 67
Memory Consumption and Execution Times Section 2 Control and I/O

Table 34. AC 800M Memory Consumption and Execution Time for Function Blocks
and Control Modules (Continued)
First Object Next Object PM865
Object
(kbytes) (kbytes) (μs)
Level6CC 41.7 11.0 173
ThreePosCC 22.9 3.9 180
PidSimpleCC 15.2 1.8 96
PidCC 91.2 14.1 401
PidAdvancedCC 214.8 25.7 941

Table 35. Execution Time for a Number of Standard Operations and Function Calls
Operation/Function Data Type PM865 (μs)
a:= b or c bool 0.13
a:= b and c bool 0.13
a:= b xor c bool 0.15

a := b string[40] 14.90
a := b + c string[10] 16.90
a := b + c string[40] 21.10
a := b + c string[140] 51.10
a := b + c dint 0.12
a := b + c real 1.59
a := b - c dint 0.13
a := b - c real 1.32
a := b * c dint 0.17
a := b * c real 1.31
a := b / c dint 0.41

68 3BSE041434R4101
Section 2 Control and I/O Compilation and Download

Table 35. Execution Time for a Number of Standard Operations and Function Calls
Operation/Function Data Type PM865 (μs)
a := b / c real 3.70

a:= b <> c dint 0.15

a:= b <> c real 1.42

a := real_to_dint(b) dint 7.53

a := dint_to_real(b) real 1.14
a := real_to_time(b) time 10.43
a := time_to_real(b) real 5.45

Compilation and Download

CPU load is calculated as a percentage using the following formula.
CPU load (%) = 100*(Total execution time / Total interval time)

Note that applications can never use more than 70% of the CPU capacity. If an
application demands more than 70%, the controller will reschedule its tasks until
the demand is readjusted to 70% or stop the execution if configured to do so.

Running a controller at close to 70% CPU load will result in poor performance and
longer response times for peer-to-peer and OPC communication. Under all
conditions peak cyclic load should be maintained at 65% and “static” cyclic load at
60%. If high communication throughput is important, the cyclic load should be 30-
40%.
CPU load is also influenced by other factors, such as Modulebus scan interval and
the number of modules on Modulebus (AC 800M), or the scanning of ABB Drives.
For example, it takes 2.0 to 2.8 minutes to compile and download a complex 7 MB
application, from a Pentium IV 2.8 GHz, 2 GB PC, to a controller.

3BSE041434R4101 69
Hardware and I/O Section 2 Control and I/O

Hardware and I/O

Modulebus Scanning of Digital/Analog Modules
Modulebus scanning has a considerable influence on CPU load, since I/O copying
on Modulebus is handled by the controller CPU.
The scan time increases as modules are added, and at a certain point Modulebus
scanning will start to seriously influence CPU load.
The Modulebus scan cycle time can be set in Control Builder. The cycle time must
be set to suit the module requiring the shortest scan interval. A solution to this is to
connect I/O variables requiring shorter scan intervals via the CI854 PROFIBUS
adapter.
In AC 800M, Modulebus scanning has the highest priority. The cyclic load
presented for IEC 61131-3 applications includes extra load caused by Modulebus
interrupts.

Calculation of Scan Time on the Modulebus and CPU load

The following definitions are used in the calculations:
1. Amount of module types:
n1 = amount of drives and DP, DI, DO, AI and AO modules (except AI880A)
n2 = amount of AI880A modules

For redundant DO840, DO880 and AO845 both modules should be counted. For
other redundant modules, only one should be counted.

2. Scan time for different modules:

t1 = 0.4 ms (scan time for n1)
t2 = 0.5 ms (scan time for n2)

70 3BSE041434R4101
Section 2 Control and I/O Calculation of Scan Time on the Modulebus and CPU load

Calculation of Fastest Possible Scan Time

The fastest possible scan time is the sum of all modules (n1+n2) multiplied with the
sum of their respective scan times (t1,t2).
Example
It can never take less than 10 * 0.4 = 4.0 ms to scan 10 non-AI880A modules.

Calculation of the Modulebus CPU load

The Modulebus scanning causes the following CPU load if the chosen scan cycle
time is less or equal to the fastest possible scan time:
Load(fastest) = (n1 / (n1 + n2) * 17) + (n2 / (n1 + n2) * 26)

The following CPU load is caused for other scan cycle times:
Load(chosen) = Fastest Possible Scan Time / Chosen Scan time * Load(fastest)
The formulas are valid for all AC 800M processor unit types.
Example
Non-AI880A modules at fastest possible scan time will always cause 17% load.

Updating Rate of Data to an Application

The rate in milliseconds at which all channels of an I/O module are updated in the
controller to be used in the IEC 61131 application, as a function of the scan time in
milliseconds is as follows:
• For AI, AO and AI843 (except AI880A and other temperature measuring I/O
than AI843) the updating time is equal to number of channels divided by two
multiplied by the scan time.
• For temperature measuring I/O (except for AI843) the updating time is equal to
number of channels multiplied by the scan time.
• For AI880A the updating time is equal to scan time.
• For Standard Drives the updating time is equal to scan time.
• For Engineered Drives the updating time is equal to scan time multiplied by 12.
• For DI, DO, DP the updating time is equal to scan time.

3BSE041434R4101 71
Modulebus Scanning of ABB Drives (AC 800M) Section 2 Control and I/O

Modulebus Scanning of ABB Drives (AC 800M)

Scanning of ABB Drives on Modulebus also influences CPU load.

Modulebus Scanning of ABB Engineered Drives (AC 800M)

Scanning of an engineered Drive is distributed
over 3 * 12 scan cycles. Three channels (DDS
pairs) are scanned in each scan cycle. The first Table 36. Scan cycles for
two are always channels 1 and 2 (i.e. DDS ABB Engineered Drives
pairs 10/11 and 12/13); the third will be
different for each scan cycle.To scan the three
Scan Cycle DDS Pair 3
DDS pairs each cycle takes 3 * 0.4 = 1.2 ms. It
is not possible to have a scan interval less then 1, 5, 9 14/15
2 ms for the Modulebus scanner. Thus, for one 2, 6, 10 16/17
drive the scan time will be 2 ms.
3, 7, 11 18/19
Example
4 20/21
For four drives, the scan time will be
1.2 ms * 4 = 4.8 ms for the DDS pairs 10/11 8 22/23
and 12/13, and the scan time for the remaining 12 24/25
of the DDS pairs will be
1.2 ms * 4 * 12 = 57.6 ms.

Modulebus Scanning of ABB Standard Drives (AC 800M)

For ABB Standard Drives, all data sets (DDS 1/2 and DDS 3/4) are scanned in each
scan cycle. It takes 2 * 0.4 = 0.8 ms to scan a single Standard Drive.
Example
For four ABB Standard Drives the scan time will be 0.8 ms * 4 = 3.2 ms.

I/O Channels in High Integrity Controller

The maximum allowed I/O channel count in a High Integrity controller is 500
redundant channels.

72 3BSE041434R4101
Section 2 Control and I/O I/O Response Time

I/O Response Time

This section lists I/O response time for different I/O protocols, which are supported
on AC 800M. Different I/O unit type used will give different response time.
The measurement is done using PM864A. Measurements with S800I/O are done in
configuration with 12 I/O modules of various kinds connected to the field interface.
The four measured I/O channels (one analog input-output and one digital input-
output) are running on time critical task with 1 ms cycle time. The rest of I/O
channels are running on normal task with 250 ms cycle time.
S100 I/O bus is measured in the configuration with one DSDI110AV1 (scan
interval=0 and filter time=0), one DSDO115A (update interval=10), one DSAI130A
(scan interval=75 and filter time=0) and one DSAO130A (update interval=2).
Configuration on the task connection is similar to S800 I/O above. The time unit
used is 0.1ms.

Table 37. I/O Response Time for Different I/O Protocols

Response
Field Signal
I/O Protocol I/O type Time
Interface Type
[ms]
Modulebus (optical) TB840 DI810-DO810 digital 5
AI810-AO810 analog 167
PROFIBUS DP/V1 CI840 DI810-DO810 digital 26
(CI854A)
AI810-AO810 analog 203
1.5M Baudrate
CI830 DI810-DO810 digital 28
AI810-AO810 analog 194
CI801 DI810-DO810 digital 25
AI810-AO810 analog 164
S100 I/O bus DSBC176 DSDI110AV1- digital 2
(CI856) DSDO115
DSAI130A-DSAO130A analog 64

3BSE041434R4101 73
MMS Communication Section 2 Control and I/O

Table 37. I/O Response Time for Different I/O Protocols (Continued)

Response
Field Signal
I/O Protocol I/O type Time
Interface Type
[ms]
Drivebus (CI858) 1 unit ABB Engineered Drive 1 pair 8
Priority: Normal R/W
dataset
12 units ABB Engineered Drives 1 pair 40
R/W
dataset

Redundancy Switchover Time

The switchover times for redundant I/O and Controller CPU is shown in Table 38

Table 38. Redundant I/O and Controller CPU Switchover Time

Parameter Data
S800 I/O, FCI < 100 ms
PROFIBUS, FOUNDATION Fieldbus 1-2 sec., depending on the baud rate
From primary controller to backup < 10 ms
controller

MMS Communication
Communication performance is affected by bandwidth, message length and
application load.
MMS communication takes place serially and asynchronously, according to the
master/slave (or client/server) principle. The master channel of a system initiates
the message transmission sequence, while a system acting as a slave simply
responds to the calls from the master via a slave channel.

74 3BSE041434R4101
Section 2 Control and I/O MMS Communication

The following table gives the performance of MMS communication in terms of

transactions per second for MMSWrite or MMSRead commands.

Table 39. Performance of an MMS Master System

AC 800M Max. Transmission Rate [transactions/second]
50% load 100 bool 300 bool 100 dint 150 dint 100 real 130 real
PM864A as MMS Client
Write 53.2 53.1 53.0 53.2 53.0 52.7
Read 51.8 51.7 51.7 51.8 51.6 51.7
PM864A as MMS Server
Write 42.1 42.2 42.2 42.2 42.1 42.2
Read 113.3 113.4 106.7 101.2 104.1 110.0
PM865 as MMS Client
Write 51.9 51.8 52.0 51.8 51.7 51.8
Read 50.3 50.3 50.4 50.2 50.4 50.2
PM865 as MMS Server
Write 42.0 42.0 42.0 41.9 42.1 42.2
Read 110.0 109.8 103.5 111.6 110.3 113.0

Higher load on the CPU will cause lower throughput in the MMS communication,
and lower load will give higher throughput.

The values presented here were obtained under optimized conditions. Several
function blocks have been triggered in parallel at a short interval time (10 ms) to
obtain the maximum transmission rate. It is important to consider this when using
these values for your communication design. The application internal
communication load can be monitored from Control Builder M
The Ethernet standard allows bandwidth transmission at 10 Mbit/s, 100 Mbit/s
(fast Ethernet), and 1000 Mbit/s (Gbit Ethernet) and AC 800M supports
10 Mbit/s.

3BSE041434R4101 75
MMS Communication Section 2 Control and I/O

The 10 Mbit/s is an ethernet speed which is in balance with the performance of the
AC 800M controller. The maximum data flow to and from the software in an
AC 800M is less than 10 Mbit/s. This means that the data flow for one AC 800M is
not limited due to its ethernet speed of 10 Mbit/s.
In a system with several controllers and PCs a switched network should be used
between the nodes. If hubs are used instead of switches the number of connected
nodes plays an important role for the throughput of the network and a single node
may get an ethernet throughput which is less than the nominal network speed. With
switches this is however not the case. Each node gets an ethernet throughput which
is more or less independent of the number of connected nodes. This means that the
data flow in the complete system is also not limited by AC 800M's ethernet speed of
10 Mbit/s.
For networks with several switches we recommend to use 100 Mbit/s or 1 Gbit/s
between switches since those ports need to manage data from several nodes to
several nodes. 10 Mbit/s should only be used on the ports where AC 800M
controllers are connected. Those ports only need to manage data for one node.
The actual communication throughput for a controller thus mainly depends on other
factors than the ethernet speed, for example the cycle times of the applications and
the CPU load in the controller.

MMS Connections Cannot Block Each Other

The controller can handle a number of concurrent MMS connections. All MMS
connections are handled in a round robin fashion. This means that no connection
can block communication for any other connection.
For example this means that it is guaranteed that variable access from one controller
to another can always be executed even if a control builder is downloading a very
large application domain to one of the controllers.

Number of Connections
The MMS stack handles several simultaneous connections. messages are treated in
a round robin fashion that guarantees that no connection is starved, but the
transmission rate through the stack decreases slightly with the number of active
connections. With 20 or less connections the performance decrease per additional
connection is however small. With more than 20 connections the amount of buffers

76 3BSE041434R4101
Section 2 Control and I/O INSUM Network

per connection is reduced. This may decrease the performance for the connections
substantially more, at least for connections transmitting much data.

INSUM Network

Table 40. INSUM Design Limitations

Limitation
Limitation type Value Reason
Number of MCUs per controller 128 Execution time for IEC61131
application and system heap memory
Number of MCUs per CI857 128 CPU performance on CI857
Number of Gateways per CI857 2 CPU performance on CI857 and
memory on CI857
Number of CI857 per AC 800M 6 CPU performance

3BSE041434R4101 77
ModBus Communication Section 2 Control and I/O

Table 41. INSUM Communication Interface CI857 Performance

Response time
Action Result Condition Comments
Start/stop 128 MCUs 15-16.5 s Task cycle 750 ms, Time measured inside the
five NV´s IEC 61131 application, from
subscribed per the time it sends the first
MCU command with INSUMWrite
to NVDesState until it
receives the last state
change with INSUM
Receive from
NVMotorStateExt.
Stop one MCU due 500 ms Task cycle 250 ms, Time measured on
to chain interlock 66 MCUs, five NVs electrical state signals on
from other MCU subscribed per the MCUs from the time the
MCU first MCU stop until the
second MCU stop.

ModBus Communication
Serial communication performance is affected by bandwidth, message length and
application load.
ModBus communication takes place serially and asynchronously.
The following table gives the performance of ModBus communication in terms of
transactions per channel per second for MBRead commands.

Table 42. Performance of a ModBus Master System

AC 800M Max. Transmission Rate [transactions/channel/second]
1 channel 2 channels 3 channels 4 channels
PM 864A
1 100 300 1 100 300 1 100 300 1 100 300
bool bool bool bool bool bool bool bool bool bool bool bool
1200 baud, 8 data bits, 1 stop bit, no parity
10% load 2.3 1.9 1.4 2.1 1.7 1.3 1.9 1.6 1.2 1.8 1.5 1.2

78 3BSE041434R4101
Section 2 Control and I/O ModBus Communication

Table 42. Performance of a ModBus Master System (Continued)

50% load 2.3 1.9 1.4 2.1 1.7 1.3 1.9 1.6 1.2 1.8 1.5 1.1
9600 baud, 8 data bits, 1 stop bit, no parity
10% load 8.0 7.2 6.2 5.9 5.5 5.0 4.7 4.6 4.4 4.0 4.0 3.9
50% load 7.9 7.2 6.2 5.7 5.3 4.9 4.6 4.6 4.1 3.8 3.8 3.5
19200 baud, 8 data bits, 1 stop bit, no parity
10% load 8.5 8.3 7.2 6.1 6.1 5.7 4.8 4.9 4.8 4.0 4.2 4.0
50% load 8.4 8.1 7.2 6.0 6.0 5.5 4.8 5.0 4.5 3.9 4.1 3.8

Higher load on the CPU will cause lower throughput in the ModBus
communication, and lower load will give higher throughput.

The values presented here were obtained under optimized conditions. Several
function blocks have been triggered in parallel at a short interval time (10 ms) to
obtain the maximum transmission rate. It is important to consider this when using
these values for your communication design.

3BSE041434R4101 79
Technical Data and Performance Section 3 800xA for DCI

Section 3 800xA for DCI

Technical Data and Performance

The following tables provide specific 800xA for DCI characteristics.

Table 43. 800xA for DCI General Characteristics

Characteristic Specification
Maximum number of Operator Not Impacted by 800xA for DCI - Refer to
Workplace Clients System Guide
Maximum number of Connectivity 4 (single or redundant)
Servers per system
Maximum number of DCI tags per 7.500
Connectivity Server
Maximum number of DCI tags per 30.000.
system
Supported System 800xA Full-size and single node.
Configurations
Remarks The 800xA for DCI server application must not
be combined with other control system server
applications on the same Connectivity Server
(note that the client part of 800xA for DCI must
be installed in all nodes except the Domain
Server).
800xA Batch Management is not supported by
800xA for DCI and the Batch Client must not
be installed on the same node as
800xA for DCI server application.

80 3BSE041434R4101
Section 3 800xA for DCI 800xA for DCI Performance

800xA for DCI Performance

Display Exchange Time

The 800xA for DCI server application collects data from controllers via GDBA, and
makes it available to the OPC clients. The table below shows the display exchange
time of a process display containing a certain amount and type of display elements.
The following information was measured with the product running on a PC with a
Pentium IV, 2.4 GHz processor and 1 Gbyte RAM. These values will vary
depending on the Client Network traffic, number of tags, number of clients/nodes in
the 800xA system and overall activity.

Table 44. 800xA for DCI Characteristics

Characteristic Specification
Continuous alarm throughput 25 events/s
Connectivity Server node network Compatible with ECCP and standard non-
connection redundant off-the-shelf Ethernet NICs
Engineering Tools Composer CTK version 5.1
Dual Processor Not supported on Server nodes

Table 45. Supported Operating Systems

Characteristic Specification
800xA for DCI Server (Primary & Windows 2000 Server and Windows 2003
Redundant) Server
800xA for DCI Client Windows 2000 Server or Windows 2003
Server or Windows 2000 Professional or
Windows XP

3BSE041434R4101 81
800xA for DCI Performance Section 3 800xA for DCI

Table 46. Display Exchange Time

Graphic Display Elements Display Exchange Time

20 Tag's / Graphic 2 Seconds typical (cached)
164 Total OPC Items subscribed
40 Tag's / Graphic 3 Seconds typical (cached)
230 Total OPC Items subscribed
80 Tag's / Graphic 5 Seconds typical (cached)
660 Total OPC Items subscribed

Server Switchover Time

The 800xA for DCI server application nodes provide redundant connectivity to the
DCI Control network. The connection requires two PC's each with a dedicated
ECCP or non-redundant Ethernet NIC to the Control Network. The following
information was measured with the products running on a PC with a Pentium IV, 2.4
GHz processor, 1 GByte RAM and using ECCP card connections. These values will
vary depending on the Control Network connection used, Client Network traffic and
the number of clients/nodes in the 800xA system.

Table 47. Server Switchover Time

Redundancy Switchover Time

ECCP communications failure <5 seconds
800xA for DCI connectivity node 10-20 seconds average
failure
Manual Switchover < 5 seconds
800xA for DCI Server application 10 seconds average
failure

82 3BSE041434R4101
Section 3 800xA for DCI Recommended Hardware Configuration

Recommended Hardware Configuration

Workstation requirements for 800xA for DCI are intended for new system
purchases or expansions to existing systems. Requirements are for all PCs used
within an 800xA for DCI system.
NOTES
1. Refer to literature to determine CPU speed, RAM, hard disk capacity, etc. for
800xA PC requirements.
2. Other ABB applications such as Asset Optimization and Information
Management as well as third party applications may apply additional load on the
workstation requiring additional workstation resources (CPU speed, RAM, hard
disk capacity, etc.).
3. Composer CTK can never be installed on the same workstation along with 800xA
for DCI software.
4. Conductor NT Server or Client can never be installed on the same workstation
along with 800xA for DCI software.

3BSE041434R4101 83
Technical Data and Performance Section 4 800xA for Harmony

Section 4 800xA for Harmony

Technical Data and Performance

The following tables provide specific 800xA for Harmony characteristics.

Table 48. 800xA for Harmony General Characteristics

Characteristic Specification
Maximum number of Operator 40
Workplace Clients
Maximum number of Connectivity 3 or 6 (when used in a redundant pair)
Servers per system
Maximum number of tags 60.000 (30.000 per Connectivity Server)
Remarks 800xA for Harmony must not be combined with
other connect servers on the same
Connectivity Server (note that the client part of
all connectivities that are selected must be
installed in all nodes except the domain
server).
A single or a single redundant pair of Harmony
Connectivity Servers are supported.
The Batch Client must not be installed on the
same node as the Harmony Server.

Table 49. 800xA for Harmony Characteristics

Characteristic Specification
Continuous alarm throughput 30 events/s

84 3BSE041434R4101
Section 4 800xA for Harmony Harmony Performance

Table 49. 800xA for Harmony Characteristics (Continued)

Computer Interface Unit (CIU) Compatible with Serial or SCSI Harmony/Infi90

CIU
Engineering Tools Composer for Harmony version 3.x and 4.x
Accessories, Options Adaptec© SCSI adapter required for SCSI CIU
interface
Dual Processor No Harmony restrictions prevent use of dual
processors

Table 50. Supported Operating Systems

Node Type Operating System

Harmony Connectivity and Windows 2000 Server or Windows 2003
Harmony Configuration Servers Server
(Primary & Redundant)
800xA for Harmony Client Windows 2000 Server or Windows 2003
Server or Windows XP

Harmony Performance

Display Exchange Time

The Harmony Server collects data from controllers via semAPI, and makes it
available to the OPC clients. The table below shows the display exchange time of a
process display containing a certain amount and type of display elements.
The following information was measured with the product running on a PC with a
Pentium IV, 2.4 GHz processor and 1 Gbyte RAM , and using a SCSI connection.
These values will vary depending on the Client Network traffic, number of tags,
number of clients/nodes in the 800xA system and overall activity.

3BSE041434R4101 85
Harmony Performance Section 4 800xA for Harmony

Table 51. Display Exchange Time

Graphic Display Elements Display Exchange Time

20 Tags / Graphic 1-2 Seconds typical (cached)
160 Total OPC Items subscribed
40 Tags / Graphic 1-2 Seconds typical (cached)
360 Total OPC Items subscribed
80 Tags / Graphic 2-3 Seconds typical (cached)
720 Total OPC Items subscribed

The tests where verified using one client node loaded to each of the three levels,
while ten other client nodes where running with level 1 graphic being displayed (20
tags / graphic).
The system included a separate ConfigServer and 3 redundant pairs of Connectivity
Servers. Each pair of Connectivity Servers contained a minimum of 10,000 tags.
Exception reporting on each pair of Connectivity Servers varied from 75-150
XR/sec to 1500-1700 XR/sec.
Event rate was 45-50 events/sec for 15-20 seconds.

Server Switchover Time

The Harmony server nodes provide redundant connectivity to the Harmony Control
network. The connection requires two PC’s each with a dedicated Computer
Interface Unit (CIU) to the Control Network.
The following information was measured with the products running on a PC with a
Pentium IV, 2.4 GHz processor, 1 GByte RAM and using a SCSI CIU connection.
These values will vary depending on the Control Network used, CIU connection
type, Client Network traffic and the number of clients/nodes in the 800xA system.

86 3BSE041434R4101
Section 4 800xA for Harmony Recommended Hardware Configuration

Table 52. Server Switchover Time

Redundancy Switchover Switchover Time

CIU communications failure <5 seconds
Harmony Server node failure 10-20 seconds average
Manual Switchover < 5 seconds
Harmony Server failure 10 seconds average

Recommended Hardware Configuration

Table 53 provides general workstation requirements for the Harmony system.

Table 53. General Workstation Requirements

Characteristics Requirements
Network connector Ethernet (IEEE ® 802.3) compliant (TCP/IP);
best performance achieved with 100Mbps
requiring 100BaseT
Ethernet addressing Fixed IP address required
Accessories, options Adaptec® SCSI adapter required for SCSI
INICI03 interface

Workstation requirements for Harmony applications are intended for new system
purchases or expansions to existing systems. The following set of notes applies to
all the 800xA for Harmony applications.
NOTES
1. Other ABB applications such as Batch Management and Information
Management as well as third party applications may apply additional load on
the workstation requiring additional workstation resources (CPU speed, RAM,
hard disk capacity, etc.). Refer to literature on these products to determine
what, if any, additional workstation resources are required.

3BSE041434R4101 87
Recommended Hardware Configuration Section 4 800xA for Harmony

2. Composer Server should never be installed on any of the 800xA nodes,

including the Harmony Server.

88 3BSE041434R4101
Section 5 800xA for Melody Technical Data and Performance

Section 5 800xA for Melody

Technical Data and Performance

The following table shows 800xA for Melody general characteristics.

Table 54. 800xA for Melody General Characteristics

Characteristic Specification
Maximum number of Operator 40
Workplace Clients
Maximum number of (optionally 8
redundant) Connectivity Servers
per system
Maximum number of CMC 70 / 10
PM 875 per (optionally
redundant) Connectivity Server
Maximum number of Melody tags 40.000 per 800xA Melody System
10.000 per Connectivity Server
Supported System 800xA Full-size.
Configurations
Remarks The 800xA for Melody must not be combined
with other connect servers on the same
Connectivity Server (note that the client part of
all connectivities that are selected must be
installed in all nodes except the domain
server).
In large systems, the 800xA for Melody Config
Server should reside in its own Application
Server, not sharing with other applications.

3BSE041434R4101 89
Sizing Data (Melody) Section 5 800xA for Melody

Sizing Data (Melody)

The following Table 55 shows sizing data that is based in Melody Control. For
details refer to the Melody documentation:

Table 55. Melody Sizing Data

Sizing Information Value

Time stamp resolution 1 ms
Available Melody message priorities 16
Message buffer size per connected module ≤ 4.000
No. of configurable messages per CCO 30 ≤ 22.500
No. of configurable messages per CMC 70 / PM 875 ≤ 60.000

Recommended Hardware Configuration

The following Table 56 shows the preconditions for personal computer to be used as
Melody Connectivity Server or as Melody Config Server. The Melody Connectivity
Server as well as the Melody Config Server are dedicated Server i.e. running only
with one of the 800xA for Melody Server components.

Table 56. Connectivity Server and Config Server Hardware Preconditions

Condition Specification
CPU clock ≥ 2.66 GHz

Memory (RAM) ≥ 1 GByte

[in case of using ≤ 5,000 tags per Connectivity Server]
Memory (RAM) ≥ 2GByte
[in case of using > 5,000 tags per Connectivity Server]

90 3BSE041434R4101
Section 5 800xA for Melody Supported Operating Systems

Supported Operating Systems

Table 57. 800xA for Melody Supported Operating Systems

Node Type Operating System

Melody Connectivity Server Windows 2000 Server or
Windows 2003 Server
Melody Config Server Windows 2000 Server or
Windows 2003 Server
Engineering Project Data Base Windows 2000 Server
Operator Workplace Windows XP Professional
Aspect Directory Windows 2000 Server or
Windows 2003 Server

3BSE041434R4101 91
Technical Data and Performance Section 6 800xA for MOD 300

Section 6 800xA for MOD 300

Technical Data and Performance

Technical Data

Supported MOD 300 Controllers:

An RTAB (Real Time Accelerator Board), mounted in a Connectivity Server,
provides the physical connection to the DCN or eDCN and the following
controllers:
• AC 460 Series
• AC 410 Series
• MOD 300 Controller Subsystem (SC Controllers and Model B)
• MOD 300 Multibus

Network Support
800xA for MOD 300 provides integration of the 800xA system and the Advant
OCS/MOD 300 control network (DCN or eDCN).

Other Functions
800xA for MOD 300 consists of two parts: one to be run on the workstation and one
on the RTA (Real Time Accelerator) board. The RTA board is of PCI-bus type, and
is installed on the computer where the Connectivity Server is executing. The
software on the RTA board is automatically downloaded at start-up.

92 3BSE041434R4101
Section 6 800xA for MOD 300 Product Performance

Product Performance

Product Capacity

Table 58. Product Capacity

Description Number
Connectivity Servers
Primary Connectivity Servers 3
Backup Connectivity Servers 3
Tags
Maximum number of tags per Connectivity 6.000
Server.
Include following items when calculating
the load on the connectivity server:
• CCF continuous and device loops
imported for display
• TLL objects imported for display
• Number of historical logs recorded
History
Maximum number of history 3.000
logs/connectivity server or redundant pair
Maximum rate for history 500 points/second
storage/connectivity server or redundant
pair.
Note, when specifying the history storage
interval: Storage intervals of 1, 2, 3 or
greater than 20 seconds will be
subscribed to the MOD system at the
specified interval. Storage intervals of 4
through 20 seconds will be subscribed to
the MOD system at 4 seconds regardless
of the specified interval.

3BSE041434R4101 93
Pre-requisites and Configuration Rules Section 6 800xA for MOD 300

Table 58. Product Capacity (Continued)

OPC Subscriptions
OPC subscription rate. Nominally 2.500 items per second
One history point counts as two OPC
subscription items (measure and quality).
A point on a graphic, like measure, counts
as one subscription item and is updated at
the given rate for the tag. PID faceplates
put a load of 35 to 45 items per second
depending on the faceplate type.

Pre-requisites and Configuration Rules

The following prerequisites and requirements are necessary to support the
800xA for MOD 300 software.

RTA Board Requirements

The Real-time Accelerator Board (RTAB) is required (PCI type only) to connect the
Connectivity Server to the Advant OCS Control Network (MOD 300 DCN/eDCN).
If you require the RTAB, you must install the PU514/PU514A (RTAB for DCN) or
the PU515/PU515A (RTAB for eDCN) before you install the PAS System Services
software. Do not use the PU518 or PU519.
The Real-time Accelerator Board is powered from the PCI bus supply in the
computer. The PCI RTAB board (PU514 or PU515) requires a 5V PCI slot. Do not
use the PU514 or PU515 RTAB in a PCI slot that uses the 3.3V standard. The PCI
RTAB board (PU514A or PU515A) uses either a 3.3V or 5V PCI slot or PCI-X slot
and replaces the PU514 / PU515. It has two redundant bus connectors.

94 3BSE041434R4101
Section 6 800xA for MOD 300 Pre-requisites and Configuration Rules

MOD 300 System Requirements

The MOD 300 integration software requires that the Advant OCS with MOD 300
System be at the following levels:
• AdvaBuild 3.3/2 P2 or higher for Windows
• MOD 300 System Version 14.6/x or higher software
One computer with AdvaBuild for Windows is required by the MOD Importer
application to populate the Aspect Server with MOD 300 tag data. A GENERICD
object must be configured in AdvaBuild to establish the MOD 300 Connectivity
Server (with RTAB) as an Advant OCS node in the MOD 300 database.

Software Requirements
The 800xA for MOD 300 integration software requires the Microsoft Windows XP
Professional or Microsoft Windows 2003 Server (US English version) and base
System 800xA 4.1 product be already installed to support the MOD 300 installation.
MOD 300 client software can be loaded alone, on a Connectivity Server, or on top
of an Application Server such as Information Management.
MOD PAS System Services is installed on the Connectivity Server only.
The Audit Trail option is required in order to record MOD 300 parameter changes to
Information Management.

Computer Requirements
Refer to the computer manufacturer’s documentation to determine if your computer
is working properly when powered up. Basic power up and power down instructions
for your computer are described in the computer manufacturer’s documentation.
The computer must meet the minimum requirements for the 800xA product.

Hyper threading and dual processing must be disabled on Connectivity Servers

with 800xA for MOD 300 in order for the RTA board to work properly. This must
be done before loading the Windows operating system. Otherwise, a complete
reinstall of the operating system will be required for Windows XP and Windows
2003 Server. Check the computer vendor documentation on how to turn off hyper
threading.

3BSE041434R4101 95
Pre-requisites and Configuration Rules Section 6 800xA for MOD 300

MOD 300 Multibus Restrictions

The MOD 300 Connect software requires that the MOD 300 System be at Version
14.6/x software. It is not possible to use the MOD Tag Importer with the Multibus
DPSS; therefore, users will have to contract to have ABB convert their tags by
migrating the database to Advant or Windows and then run the MOD Importer.

800xA functions not supported in MOD 300

This release of the 800xA for MOD 300 software does not include support for the
following functionality.
• MOD 300 Overview display
• Graphic Conversion
• Unit relativity
• MOD 300 PHL (configure history for any points/attributes that need a trend
presentation)
• TRIO Config and PLC Config. Use MOD 300 Engineering Displays.
• Batch 300
• Disk IO actions – open, close, remove, input, output, filesys

96 3BSE041434R4101
Section 7 800xA for Advant Master Technical Data and Performance

Section 7 800xA for Advant Master

Technical Data and Performance

Technical Data
The 800xA for Advant Master consists of two parts, one executing in the
workstation and one on the RTA (Real Time Accelerator) board. The RTA board is
of PCI-bus type, and is installed in the PC where the Connectivity Server is
executing. The software on the RTA board is automatically downloaded at start-up.

Hyper threading and dual processing must be disabled on Connectivity Servers

with 800xA for Advant Master in order for the RTA board to work properly. This
must be done before loading the Windows operating system. Otherwise, a
complete reinstall of the operating system will be required for Windows XP and
Windows 2003 Server. Check the computer vendor documentation on how to turn
off hyper threading.

This software product utilizes the client/server technique, making it possible to run
both client and server on one PC for a small configuration. For larger
configurations, one or several servers can be used with up to 40 client workplaces.

Table 59. Maximum System Configuration

Characteristic Specification
Maximum number of Operator 40
Workplace Clients
Maximum number of Connectivity 6 (single or redundant pairs)
Servers per system

3BSE041434R4101 97
Technical Data Section 7 800xA for Advant Master

Table 59. Maximum System Configuration (Continued)

Characteristic Specification
Maximum number of Connectivity 2 (single or redundant)
Servers per MB 300 control
network
Maximum number of AC 400 40 (20 per Connectivity Server)
nodes on an MB 300 control
network
Maximum number of tags 60.000
Supported System 800xA Full-size, operating system optimized, and
Configurations single node engineering.
Remarks 800xA for Advant Master must be run in a
dedicated connectivity server with the RTA
board.

Supported Advant Master Controllers:

• Advant Controller 400 Series with Master software
• MasterPiece 200/1
The table below shows the versions of MasterPiece 200/1, Advant Controller 410
and Advant Controller 450, that have been verified together with System 800xA
Version 4.1. Please be aware that if problems occur in other combinations, upgrade
to a later version may be required.

Network Support
The following network types are supported:
• Multiple MB 300 networks.
• Redundant Connectivity Servers on MB 300 networks.
• Redundant MB 300 network

98 3BSE041434R4101
Section 7 800xA for Advant Master Technical Data

Table 60. Controller Versions verified with System 800xA Version 4.1

Product Verified with

Controller Type Software Version
Version System 800xA
MasterPiece 200/1 2.0 XMP200 SW*2.0 -
XMP200 SW*3.0
2.1 XMP200 SW*4.0 yes(1)
3.0 QMP220 SW* 5.0 -
4.0 QMP220 SW* 6.0 yes
Advant Controller 410 1.0 QC01-BAS11*7.0 -
1.1 QC01-BAS11*7.0 -
1.2/0 QC01-BAS11*8.0 -
1.2/1-1.2/8 QC01-BAS11*9.0 -
1.3 QC01-BAS11*9.0 -
1.4 QC01-BAS11*10.0 -
1.5 QC01-BAS11*11.0 yes
Advant Controller 450 1.0 QC02-BAS21*7.0 -
1.1 QC02-BAS21*7.0 -
1.2/0 QC02-BAS21*8.0 -
1.2/1-1.2/8 QC02-BAS21*9.0 -
1.3 QC02-BAS21*9.0 yes
2.0 QC07-BAS41*1.0 -
2.1 QC07-BAS41*2.0 yes
2.2 QC07-BAS41*3.0 -
2.3 QC07-BAS41*4.0 yes
(1) The sequence Functional Unit (SEQ) cannot be supported for this version.

3BSE041434R4101 99
Technical Data Section 7 800xA for Advant Master

Table 61. Technical Data

Description Number
Process Objects
Predefined ABB process objects AI, AO, DI, DO, DAT, TEXT, GENBIN,
GENCON, GENUSD, GROUP, MANSTN,
RATIOSTN, SEQ, MOTCON, VALVECON,
PIDCON, DRICONS, DRICONE and
MOTCONI
Number of faceplates 1 - 3 per process object
Graphic
Number of graphic elements 2 - 5 per process object
Frequency of dynamic update in From 1 second and upwards. 3 cyclic
graphic elements intervals are pre-configured.
Alarm
Total number of system and process 10.000(1)
alarms in the alarm manager
TTD (Time Tagged Data)
Maximum numbers of TTD logs per 5000(2)
connectivity server
Shortest TTD log sample interval 10s
Direct (OPC) Logging
Recommended sample time when a 9 s for max. 50 logs per controller(4)
process object is used directly as a
data source(3)

100 3BSE041434R4101
Section 7 800xA for Advant Master Product Performance

Table 61. Technical Data (Continued)

Description Number
OPC 800xA Client Connection for Advant Master Process Objects
Read operations 1,3 or 9 seconds(5)
Write operations It is only supported to perform OPC write
operations towards DAT objects. There are
no hard limitations on the number of write
operations that can be executed.
(1) Shared with all other eventual alarms received from AC 800M, 3rd party OPC etc.
(2) This number of TTD logs must be decreased, if it exists secondary IM logs for the TTD logs,
where the sample blocking rate is faster than the default 20 minutes.
(3) Data source for a Historian log can be either a process object itself, or a TTD log in an Advant
Controller 400 Series. For performance and signal error handling reason, the recommendation
is to use TTD logs in the Advant Controller 400 Series as primary logs. These TTD logs are
then used as data sources for long term storage in the Historian.
(4) Sample times < 9s will be mapped to 1 or 3s cyclical subscription in the controllers, and sample
times > 9s will result in demand requests. HSI and controller load will be significantly increased
in both cases.
(5) Not all properties are supported. See manual 800xA for Advant Master, Configuration.

For more information see the product guide for the AC 400 Series controllers.

Product Performance
The Industrial IT System 800xA Operator Workplace is designed and verified to
have good performance, and to be the desired tool for the operator’s work, such as
process control and production supervision. It is also a powerful and suitable tool
for engineering and maintenance, for effective navigation and for fast access to the
information needed.
The system performance in an open environment is dependent on many factors such
as: PC type, size of memory, other installed software in use, etc.

3BSE041434R4101 101
Technical Data and Performance Section 8 PLC Connect

Section 8 PLC Connect

Technical Data and Performance

Technical Data
The system limits and capabilities in this document are valid, with the additional
limitations and capabilities below.
.

Table 62. PLC Connect General Characteristics

Characteristic Specification
Supported System 800xA Full-size, operating system optimized
Configurations (medium size), server optimized (small
size), and single node.
Maximum number of Connectivity Limited by the max number of
Servers per system Connectivity Servers (redundant or non-
redundant) allowed in a 800xA system.
Maximum number of PLC Connect 25.000
signal objects in one PLC Connect
Connectivity Server running in a
separate node (large or medium size
system)
Maximum number of PLC Connect Refer to system constraints.
signal objects in a server optimized or
single node configuration (small or
single node system)
Maximum number of serial channels 10
used in one PLC Connect Connectivity
Server for dialed communication with
PLCs via Comli or Modbus Serial

102 3BSE041434R4101
Section 8 PLC Connect Technical Data

Table 62. PLC Connect General Characteristics (Continued)

Characteristic Specification
Open interfaces
PLC Connect Real Time Data Access COM Methods for accessing dynamic
and static PLC Connect signal
properties.
Communication Server Pre Treatment Com interface for manipulation of read
process values.
Event Server Pre Treatment Com interface for manipulation of
properties of detected events when
entered to the Event Server.
Event Extended Options OLE interface for integrating an
application that is o be executed on an
event.
OLEDB Provider for Events OLE DB interface to saved event data.
PLC Connect properties Most properties of the PLC Connect
configuration aspects can be accessed
via OPC or by the Bulk Data Manager.
Dial Manager Server Access Com interface for initiating and
disconnecting calls handled by the Dial
manager for dialed communication with
PLCs.
Redundancy Redundant pairs of PLC Connect
Connectivity Servers are supported.
Configuration data is stored in Aspect
Directory, hence Aspect Server
redundancy in 800xA covers
PLC Connect Configuration Data.

3BSE041434R4101 103
Product Performance Section 8 PLC Connect

Table 62. PLC Connect General Characteristics (Continued)

Characteristic Specification
Audit Trail Audit of PLC Connect Configuration
changes are supported. Re-
authentication and double
Authentication is supported for
PLC Connect signals.
Remark PLC Connect can be combined with
AC 800M Connect in the same
connectivity server in a small size or
single node system.

Table 63. PLC Connect Characteristics

Description Number
PLC Connect signal types Boolean, integer, long integer, real,
double, string
Supplied Faceplate templates for PLC 3 variants
Connect object types
Supplied set of graphic elements for 16 variants
PLC Connect objects
Built in PLC protocol drivers Modbus RTU Serial, Modbus RTU
TCP/IP, Comli, SattBus, Sattbus over
TCP/IP, IEC60870-5-101 (option),
IEC60870-5-104 (option), OPC DA
client

Product Performance
The system performance is listed in this document. Specific PLC Connect
performance is given below.

104 3BSE041434R4101
Section 8 PLC Connect Product Performance

PLC Communication Performance

The time from a change in the process until the new signal value is available in the
PLC Connect communication server is dependent on a number of parameters: the
speed of the field-bus used, other products involved (for example a third party OPC
Server), the requested update cycle time set up in the PLC Connect configuration
aspect, total number of signals using the available system capacity and so on.
The time from a change of a value in the communication server until an indication
on the screen is typically less than 2 seconds for a polled 9.6 Kbaud serial protocol.

Manual Control Performance

Time from a manual control in the Process Graphics until a value change on
terminal in a PLC connected to PLC Connect server using a 9.6 Kbaud serial
protocol is typically less than 1.0 second.

Alarms and Events Performance

Continuous alarm throughput of 25 PLC Connect events/alarms per second can be
handled.
Bursts of 1.000 PLC Connect events/alarms every 10 minutes can be detected and
logged as long as the long term average load of 25 PLC Connect events/alarms per
second is not exceeded.

3BSE041434R4101 105
Technical Data and Performance Section 9 Process Engineering Tool Integration for INtools

Section 9 Process Engineering Tool

Integration for INtools

Technical Data and Performance

Configuration Rules
Process Engineering Tool Integration is installed on the same PC as the 800xA
Primary Aspect Server. There is also a part of Process Engineering Tool Integration
which is installed on the INtools® server PC.

Performance Data
Table 64 details the capacities of Process Engineering Tool Integration features.

Table 64. Process Engineering Tool Integration Capacities

Feature Characteristic/Value
Create objects in 800xA 1.000 objects in less than 30 minutes
Update properties of existing 800xA 400 objects of a 1.000 object database in
objects less than 3 minutes
INtools® Document call-up in 800xA 5 seconds typical(1)
800xA Faceplate call-up during Data <= 2 seconds(2)
Transfer
(1) All times and rates are typical and dependent on the connected system configuration and
system load. Depends on the size of the document being generated into PDF.
(2) Depends on the size of the document being generated into PDF.

106 3BSE041434R4101
3BSE041434R4101. Printed in Sweden June 2005
Copyright © 2003 - 2005 by ABB. All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.

http://www.abb.com

Automation Technology Products Automation Technology Products Automation Technology Products

Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
www.abb.com/controlsystems www.abb.com/controlsystems www.abb.de/controlsystems