Course T300, Engineering an 800xA System

Chapter 2 800xA System Concept

TABLE OF CONTENTS
Chapter 2 800xA System Concept................................................................................................................................................. 2-1
2.1 General Information ............................................................................................................................................................. 2-3
2.1.1 Description .................................................................................................................................................................... 2-3
2.1.2 Status report .................................................................................................................................................................. 2-3
2.1.3 Objectives...................................................................................................................................................................... 2-3
2.1.4 Reference Documentation............................................................................................................................................. 2-3
2.2 System Architecture ............................................................................................................................................................. 2-4
2.2.1 Traditional Systems ...................................................................................................................................................... 2-4
2.2.2 IndustrialIT Architecture................................................................................................................................................ 2-6
2.3 800xA Platform.................................................................................................................................................................... 2-8
2.3.1 Aspect Object Platform................................................................................................................................................. 2-8
2.3.2 AfW Service Model .................................................................................................................................................... 2-10
2.3.3 System deployment..................................................................................................................................................... 2-11
2.4 System topology................................................................................................................................................................. 2-12
2.4.1 Logical network structure ........................................................................................................................................... 2-12
2.4.2 Server Classes ............................................................................................................................................................. 2-14
2.4.3 Clients Classes ............................................................................................................................................................ 2-15
2.5 Review................................................................................................................................................................................ 2-16
2.5.1 Questions..................................................................................................................................................................... 2-16
2.5.2 Answers ....................................................................................................................................................................... 2-17

2-1

Course T300, Engineering an 800xA System

2-2

T300, Engineering an 800xA System

2.1 General Information

2.1.1 Description
This chapter gives an overview about the 800xA system topology and the Aspect
Framework architecture. The logical structure of an Automation network and the
function of the main components is explained.

2.1.2 Status report

The course starts with this chapter and the participants should have the necessary
knowledge as described in the course prerequisites.

2.1.3 Objectives
On completion of this chapter you will be able to:

Describe the system architecture and compare it with traditional automation

architectures.

Describe the basic terms which are used in the 800xA base platform.

Describe how an Afw Service access is implemented in the Client/server model.

Explain the function of the main components in an Automation network.

2.1.4 Reference Documentation

3BSE034461R301 System Guide SV3.1 SP1
3BUS092080R0001 System Architecture Overview

2-3

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2.2 System Architecture

2.2.1 Traditional Systems
2.2.1.1 PLC / SCADA Architecture
In the PLC architecture each level has its own data definitions. Object orientation is
possible within one level. Products could be kept simpler.

Communication is point to point between individual levels. Leads to complex

communication system in large systems. Each level requires its own tools for
navigation.

2-4

T300, Engineering an 800xA System

2.2.1.2 DCS Architecture

A typical feature of the DCS systems is a more consistent way of handling process
control items. Being a system object oriented access and increased functionality is
provided for the user. One clear benefit of DCS systems is the increased engineering
and maintenance efficiency.

Generally DCS systems provide more complex functionality and the investement can
be justified in large systems. Installations requiring additional levels bring additional
data definitions and additional tools.

2-5

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2.2.2 IndustrialIT Architecture

Industrial IT Extended Automation System 800xA extends the reach of the traditional
automation systems.beyond control of the process.
Industrial IT architecture introduces a system wide object definition. Each level or
subsystem handles its data which is referenced from the single object definition. Full
object orientation throughout the system can be implemented.
Extended Automation objects provide a foundation for the efficient development,
deployment, reuse and continuous improvement of production applications.

2.2.2.1 Aspect Object Concept

The Aspect Objects architecture is a cornerstone of the Industrial IT concept. It
provides:

2-6

A consistent, scalable concept that integrates Process Control & Automation,

Substation Automation and Safety products.

Information-centric navigation a consistent way to instantly access all

information without having to know how and by which application the
information is handled.

A homogeneous base for all applications. Open standards make it possible for
users to integrate new aspect systems.

T300, Engineering an 800xA System

A central problem in plant operations, as well as asset life cycle management, is the
need to organize, manage, and have access to information for all different aspects of a
great number of plant and process entities.
These entities, or real world objects, are of many different kinds. They can be physical
process objects, like a valve, or more complex, like a reactor. Other examples are:
products, material, batch procedures, manufacturing orders, and customer accounts.

They are called Aspect Objects

Each of these real world objects can be described from several different perspectives.
Each perspective defines a piece of information and a set of functions to create,
access, and manipulate this information.
Examples are: graphic, alarm, trend, report, order definition, mechanical layout etc.

We call this an Aspect of the object.

It is necessary to be able to implement these aspects using many different applications,

both existing and new, from ABB, third parties and customers. It is desirable to be
able to do this without changes to the applications.
It is not reasonable to require that all these different applications be aware of each
other. Still, the applications must cooperate to provide an integrated view and
functionality of the object.
Examples are: Graphics Builder for graphic, Auto CAD for mechanical layout, SAP
for order handling etc.

These applications are called Aspect Systems, which implements one or several
Aspect types.

2-7

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2.3 800xA Platform

2.3.1 Aspect Object Platform
From a software architecture perspective, the foundation of the 800xA system is the
800xA Base Platform.
The basic system functionality is packaged together with those Aspect Systems which
provide common functionality to an extended system implementation, such as screen
layout and handling of the screen, and Aspect Object navigation, engineering, and
information management functions.
The resulting functionality is represented by the base software deliverable of the
800xA system.

Controllers are connected to the system through connectivity components, which are
bundled together and offered as options to the 800xA System. Connectivity packages
provide access to real time data, historical data, and alarm and event data from
different types of controllers.
The 800xA system provides connectivity to 800xA controllers as well as controllers
from earlier system offerings:

2-8

AC 800M

AC400 Series Master

AC100 Series

PLC Connect

Safeguard

Symphony Harmony Infi-90

Symphony Melody

Connection to any OPC Server

T300, Engineering an 800xA System

2.3.1.1 Aspect Framework

Two main concepts are central to the Aspect Object architecture: the concept of
Aspect Objects, and the concept of Afw Services.

Based on these concepts, a framework is defined, with rules and conventions for how
to add functionality to the server and workplace layers, and for how to connect
functions in the control layer to the server layer. This framework is known as the
Aspect Framework (Afw).
The framework includes an Aspect Directory, where all Aspect Objects and their
aspects are registered, and also all aspect systems and the operations they support. To
perform an operation on an Aspect Object, an application (e.g. an aspect system)
invokes a framework interface for that operation. Using information in the Aspect
Directory, the framework then invokes the corresponding interfaces of all aspect
systems that are concerned by that particular operation for that particular object. Thus,
to copy and paste an object, for example, all aspect systems that implement aspects
that are defined for that object are involved and perform their part of the operation.

2-9

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2.3.2 AfW Service Model

Services must conform to the Afw Service model. An Afw Service is designed to run
around the clock. It is partioned into several service groups, each group handling part
of the scope of the service (e.g. part of the object space). For redundancy each group
can contain several service providers running on different servers.

An Afw Service normally provides a service handler. This is a COM object that a
client includes and runs as an in-process object to access the service. Using
information from the Aspect Directory, the service handler provides one uniform
interface to the service, relieving the client from having to deal with issues such as
how the service is partitioned, redundant service providers, etc.

2-10

T300, Engineering an 800xA System

A typical example is the OPC communication:

OPC plays a vital role in the Aspect Object architecture it is through OPC compliant
interfaces that applications have access to real-time data, historical data, and alarm and
event data from controllers, field devices, and other software applications

The Afw OPC server concept allows many different OPC servers to be placed under a
one common server that unifies access to data from different sources. This common
server provides one set of OPC compliant interfaces, eliminating the need for client
applications to know which OPC server to use for each data item.

2.3.3 System deployment

The Aspect Object architecture assumes a system of nodes and networks as explained
in the next chapter. From an architectural perspective, any Afw Service can run on any
server node in such a system.
While this is very flexible, it can also be quite confusing. Therefore, to make it
possible to create simple configuration rules, and to describe, test and verify various
supported configurations, three classes of servers are defined:

Aspect Server

Connectivity Server

Application Server

2-11

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2.4 System topology

2.4.1 Logical network structure
The Aspect Object architecture assumes a system of computers and devices that
communicate with each other over different types of communication networks, as
illustrated conceptually here.

System communication in the IndustrialIT System is based on Ethernet and TCP/IP

networks.
For smaller systems and for systems where network separation is not desired, the
Client/Server Network and Control Network can be combined in one Automation
System Network.
System 800xA provides the highest degree of fault tolerance to meet the most
demanding application needs for maximum system uptime. Optionally redundant I/O,
controllers, control networks, fieldbus networks, Connectivity Servers, Aspect
Servers, and Operator Workplaces with automatic switchover provide the required
functional integrity to meet the most demanding process needs.
The 800xA system uses a central licensing mechanism. One designated computer,
typically the domain controller, should contain the central licensing server (CLS).

2-12

T300, Engineering an 800xA System

2.4.1.1 Plant Network

The Plant Network can be dedicated for process automation purposes or be a part of
the plant intranet already available on a site.
Further connection of the plant network to the Internet or any other type of external
network should be performed in accordance with adequate network security practices.

2.4.1.2 Client/Server Network

The Client/Server network is used for communication between servers, and between
client Workplaces and servers.
Via a router, the client/server network can be connected to a plant intranet, and via a
firewall to the Internet. For performance and integrity reasons, connection of foreign
systems directly to the control and client/server networks should be avoided. The
Client/Server Network can optionally be made redundant.
For any installation larger than a Single Node system, the 800xA system nodes must
reside within a dedicated Windows 2000 domain. This requires you to set up a domain
controller and DNS server. All other 800xA system server and client nodes must be
configured to be members of the domain.
It is strongly recommended that the process control system is configured as one
(Windows) domain, which is not the same as the Windows domain used elsewhere in
the company.

2.4.1.3 Control Network

The Control Network is a local area network (LAN) optimized for high performance
and reliable communication, with predictable response times in real time. It is used to
connect controllers to the servers. Controllers are nodes that run control software.
Controllers and Connectivity Servers are connected to the control network. The
control network can optionally be made redundant.
Fieldbuses are used to interconnect field devices, such as I/O modules, smart sensors
and actuators, variable speed drives, PLCs, or small single loop devices, and to
connect these devices to the system, either via a controller or directly to a server.

2-13

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2.4.2 Server Classes

Servers run software that provides system functionality, Workplaces run software that
provides various forms of user interaction.
Server classes are deployed on nodes. A node is a network addressable machine (a
PC). For very small installations, one single node (PC) can carry all these server
classes as well as the client part(s) of the product(s).
Server configuration and selection are important factors for system performance.

2.4.2.1 Aspect Server

Runs the intelligence in the system, including the aspect directory and other services
related to object management, names, security, etc.
There is only one Aspect Directory per System, which can be based on single or
redundant Aspect Servers.
Examples of services are:

Aspect Directory

File Set Distribution (FSD)

Structure and Name Server (SNS)

2.4.2.2 Connectivity Server

Provides access to controllers and other data sources. Several groups of Connectivity
Servers may exist in a system, each serving one set of data sources.
Each Connectivity Server runs only one type of connectivity. AC 800M Connect can
be combined with PROFIBUS Device Integration, HART Device Integration,
FOUNDATION Fieldbus Device Integration or PLC Connect in the same server.
Examples of services are:

OPC Data Access

OPC Alarm and Event

OPC Historical Data Access

System messages

2.4.2.3 Application Server

Run various types of system applications, such as:

2-14

Batch Management

Asset Optimization

Information Management

T300, Engineering an 800xA System

2.4.3 Clients Classes

2.4.3.1 Workplace (Rich) Client
The Operator Workplace uses client/server capabilities allowing both client and server
applications to run in one PC for a small configuration, or to run in a configuration
with one server and up to thirty client workplaces.

2.4.3.2 Remote (Thin) Client

Remote Clients enables remote access to an 800xA system from a standard PC without
ABB-specific software installed. Only the Internet Explorer is required to access the
data.
The Remote Client provides operation capabilities and access to historical
information. Configuration capabilities are limited on the remote client.
A third party solution from Citrix is used to implement Remote Clients. Citrix
Metaframe Presentation Server software must be installed on an Application Server
running an Operator Workplace rich client to enable access from remote clients.
The Citrix Server must execute in a PC running the Windows 2000 server operating
system. It is not included with the 800xA software and must be purchased separately.

The Terminal Service concept also enables connections over, for example, a VPN
(virtual private network) spanning the internet. It is also possible for use with rather
low bandwidth channels, like ISDN or possibly dial-up lines.
To get the Remote Client Server functionality the Windows Terminal Services must
be enabled and the Citrix software has to be purchased and installed on top of
Windows Terminal Services. Windows Terminal Services ONLY is not supported,
mainly due to the limitations in sound and colors.

2-15

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2.5 Review
2.5.1 Questions
The interlock logic of motor M-1234 is programmed in Function Blocks.
What is the Aspect Object, what is the Aspect and what is the Aspect
System?

What stands Afw for and what data are stored in the Aspect Directory ?

There is an 800xA System with several OPC servers running. Is it

necessary to build up a connection from every Client application to each
single OPC server?

From topology point of view there are three network levels defined: Plant
network, Control network and Client/Server network. Which networks
can be collapsed into one for smaller systems?

Is it necessary to have separate nodes (machines) for Aspect and

Connectivity Server?

2-16

T300, Engineering an 800xA System

2.5.2 Answers
The interlock logic of motor M-1234 is programmed in Function Blocks.
What is the Aspect Object, what is the Aspect and what is the Aspect
System?

The motor M-1234 is the Aspect Object.

The interlock diagram (FBD) is the Aspect, which is programmed by the
Aspect System Control Bilder.
What stands Afw for and what data are stored in the Aspect Directory ?

Afw stands for Aspect Framework.

All Aspect Objects and their Aspects are registered in the Aspect Directory
and also all Aspect Systems and the operations they support.
There is an 800xA System with several OPC servers running. Is it
necessary to build up a connection from every Client application to each
single OPC server?

No, the Client applications look on one Afw OPC Service only. The Afw
Service handles the access to the different OPC servers.
From topology point of view there are three network levels defined: Plant
network, Control network and Client/Server network. Which networks
can be collapsed into one for smaller systems?

Control network and Client/Server network can be collapsed to an

Automation System network. For performance and integrity reasons,
connection of a Plant network directly to the Automation System network
should be avoided.
Is it necessary to have separate nodes (machines) for Aspect and
Connectivity Server?

No, server classes are deployed on nodes. For small installations, one
single node can carry all server classes as well as the client part.

2-17

T300, Engineering an 800xA System

Chapter 2 800xA System Concept

2-18