© A

BB

Util

ities

- 1

20

01-0

1/S

PID

ER

MR

9

Process Communication Unit PCU400

© A

BB

Util

ities

- 2

-

PCU 400 Product Presentation

© A

BB

Util

ities

- 3

-

PCU 400 Presentation Agenda

Presentation by Mattias Gustin for Market Release 9:

History

Protocols

PCU 400 concept and configuration

Documentation

Data flows

Tools

Ordering

H/W

© A

BB

Util

ities

- 4

-

PCU 400 Requirements for the product

Flexible enough to build systems solutions Possible to work standalone Suitable also for non-SCADA systems

Minimal configuration Component thinking Support of open interfaces Modern development tools

Easy to adapt new protocols Easy debugging and fault tracing

Windows NT based Standard PC type Hardware

© A

BB

Util

ities

- 5

-

SPIDER Front-End History

1988 ... 1997 1999 2000 2001 Time axis

Front-End 200

SPIDER rel. 7 SPIDER rel. 8 SPIDER rel. 9 SPIDER rel. 10

SPIDER rel. 1

RCS210

PCU400

RCS300

Release 1used with SPIDER in BKK

Release 3Introduced in SPIDER

DCU

© A

BB

Util

ities

- 6

-

Technology steps

Function 1986 1992 2000Operating system CX VxWorks Windows NT

Development tool Offline debug Online non-symbolic

Full symbolic

Language Pascal,asm C, asm C, C++

CPU 68020,12 Mhz Alpha, 100Mhz Pentium >333

Hardware ABB design DEC+ABB commercial

Interface GCOM TCP/IP,RSP TCP/IP,RSP,DDE,XML,

IEC

Commercial open interfacesGives flexibility!

© A

BB

Util

ities

- 7

-

Slave Protocols• IEC870-5-101• DNP 3.0• ADLP80/180• RP570

Master Protocols• IEC870-5-101• ADLP80• ADLP180• RP570/571• Indactic 33/41A, 2033• SINAUT 8, ST1• MODBUS RTU

Field Buses• LON

Interfaces•RSP•DDE client•XML•OPC (future API)

PCU 400, Schematic picture Interfaces

NT Server

Plug-inRSP

EngineeringTool

(Excel Based)

XML

XML

Process Equipment

CommunicationGatewaySoftware

SlaveProtocols

Master RTU

Protocols

Control Center System

LON

DDE client

Used for standalone configuration

FieldBuses

Plug-in

© A

BB

Util

ities

- 8

-

PCU 400 IEC870-5-101 profile

PCU400 implementation: ABB Norwegian User Convention Configurable link address and Common address Handling of Integrated Totals considered spontaneous transmission from

the RTU (i.e. ASDU 101 not used) File transfer is still not supported but will be developed

Experiences from projects: RTU232 and RTU560 is tested Siemens RTU AKER Elektro RTU

© A

BB

Util

ities

- 9

-

PCU 400 Connection to SPIDER

PCU400 A

RTU lines

PCU400 B

Main Computer A (Unix)

RCS Application

Rest of SPIDER

Main Computer B (Unix)

RCS Application

Rest of SPIDER

RSP Links

LAN or WAN

© A

BB

Util

ities

- 1

0 -

Functions:

• Front-End for SPIDER or SCADA• RSP protocol to SPIDER • Downline loading of DB from SPIDER• 1–24 multi-drop lines to RTUs• Protocol configurable per line• Various communication media• Replaces RCS300 (not all protocols supported)

• Distributed configuration is supported

PCU 400 as Front-End

ApplicationServers

RSP protocol overEthernet or RS-232

NGWT

ZG

115

PCU 400

RTU orSCS system

Available RTU protocols

Router

Router

WAN

Can be distributed over WAN

© A

BB

Util

ities

- 1

1 -

Functions:

• Data concentrator • Multiple multi-drop lines to RTUs / IEDs• Multiple lines (1-24) to Master systems• Protocol configurable per line• Media converter• Local configuration• Allow connection to old systems

PCU 400 as Concentrator for SA and SCADA

NGWT

ZG

115

Configuration Tool

NGWT

ZG

115

Remote Master Systems

RTU orProtection relay

F.ex. IEC870-5-101

© A

BB

Util

ities

- 1

2 -

Functions:

• Connection of new RTU to old Master System • Connection of old RTUs to new Master System • One line to RTUs / Protection relays• One line to the Master system • Media converter (dial-up to leased line)• Local configuration

PCU 400 as Converter

NGWT

ZG

115

RemoteMaster System

RTU orSA system

F.ex. IEC870-5-101

F.ex. Indactic 2033

Configuration Tool

© A

BB

Util

ities

- 1

3 -

PCU 400 Functionality

IEC870-5-101

Redundant lines individually configurable

Dial-up is supported and separated from the protocol

Dual-LAN

External minute pulse

Bit-protocol support

FTAB-loading RP570/571

Remote diagnostics via Telnet

File transfer is not supported in PCU400 and RCS300

DNP 3.0 is not supported yet

© A

BB

Util

ities

- 1

4 -

Aftersales opportunities

Flexible solutions both for SCADA, Substation Automation and Standalone protocol converting

Add new functionality to old systems Extend old systems with more lines and new protocols Selling communication solutions to other competitors Integrate new functionality in old systems

© A

BB

Util

ities

- 1

5 -

PCU 400 Ordering

A checklist and a spreadsheet is used for Price calculation

Ordering

Information about number of PCUs, lines, redundancy and mounting is required

The 19” box PCU 400 is delivered mounted in a cubicle or as a stand-alone box.

The production of the cubicles is handled by ASY/NSP SEASY has produced documents for production of mounted cubicles

This information can be transferred to local unit if local production is considered

© A

BB

Util

ities

- 1

6 -

Order-form (EXCEL spreadsheet)

The order form is divided in the following sections:

A - PC-equipment

B - Connection Unit

C - Front End switch

D - Power switch

E - Clock unit

F - Power supply

G - Cubicle

H - Installation and test

K - Additional equipment

© A

BB

Util

ities

- 1

7 -

PCU 400 Documentation

Project Engineer Handbook:• Notes• User’s Guide• Installation Manual• Configuration Manual• Product Sheet• CPU Motherboard specification• TeamCom FE-switch specification

Production documents:• Calculation spreadsheet• Drawings• Assembly• Part lists

Development:• Release plan• Agreement NOINA & SEASY• Development & Maintenance guide• Functional specifications

Ordering:• Configuration Guidelines• Calculation spreadsheet• Check-list

© A

BB

Util

ities

- 1

8 -

Training

SEASY has developed a PCU 400 course called F96. The training is handled by ABB University (contact Lars Garpemyr). The course is useful both for customers and ABB personnel for learning the functions and the tools of PCU 400.

We plan to make a special marketing tour for DEUTA and USTRA for promoting the PCU 400 product. The seminar includes: Sales training Technical description DEMO of the product.

© A

BB

Util

ities

- 1

9 -

PCU 400 Data flow - SCADA

Data Engineering Tool (DE400)

SCADA servers

Loading over LAN/WAN using RSP protocol

Parameter loading to RTU if supported

NGWT

ZG

115

Customer data

© A

BB

Util

ities

- 2

0 -

PCU 400 Data flow - Gateway

Configuration Tool

Excel based

Customer data

XML-files

REC 561 REL 5x1

LON

© A

BB

Util

ities

- 2

1 -

PCU 400 Host www-server

Logging

Current value

Event list

Device status

The PCU400 also supports web-interface for some protocols forremote debugging

© A

BB

Util

ities

- 2

2 -

PCU 400 Development tool

•Standard software

•Microsoft Development Studio 6.0

•Language C and C++

•Visual Source Safe

•PC based

•portable for site assistance

© A

BB

Util

ities

- 2

3 -

Standard PC type Communication cards

Standard COM-ports for asynchronous byte protocols. Speeds up to 56kbps/line

OCC-card 8ch for bit and byte protocols (used in standard config.) Speeds up to 9.6kbps/line.

Qualifying card is the RCS320 BCOM56-PCI Speeds up to 56kbps 1-24 lines i.e. 3 OCC cards in one PC

SEASY offers a tested and proved set-up.

Find your own H/W set-up by choosing parts from the local dealer!

PCU 400 Hardware

© A

BB

Util

ities

- 2

4 -

PCU 400 Protocol Development

Developed as “eXternal”-modules. No interference with other system components

Private database structures

Template as a base for new protocols available for: RSP interface

API for internal functions

Media and Low level drivers available

Or use DDE protocol interface. This will gain access to many already developed protocols.

© A

BB

Util

ities

- 2

5 -

Customer benefits

PCU400 is flexible

Different configurations are supported

Standard non-ABB hardware is used

Standard Windows NT 4.0

Open interfaces available e.g. DDE, XML

Protocols can be bought as 3rd part products e.g. LON

Protocols are run as separate processes in NT

Remote diagnostics via LAN or Modem

Adds functionality as new protocols to old systems

© A

BB

Util

ities

- 2

6 -

Customer benefits (cont.)

PCU400 replaces RCS3xxPCU400 covers SCADA, SA and standalone configurationsPCU 400 is a component in the SPIDER systemPCU400 has potential to grow as GatewayReduced maintenance costNew markets gives bigger volumes

© A

BB

Util

ities

- 2

7 -

PCU 400 References and Availability

On-site:

BKK project in Norway 22 pcs PCU 400 in operation since 14th of June 1999

Operational hours per PCU is 8800 hours

Total operational hours is 190 000 hours with no H/W failure

Tussa Kraft, Oppland Energi, Nord Trondelag 1999

Current Projects:

SCECO (Saudi) 8 pcs PCU400 with Indactic 33 & RP570

ABB SWG in Untra, Panama & Kolsva IEC870,DNP+LON

Schneider-Electro, Sweden ADLP180-MODBUS