Process Communication Unit PCU400

PCU 400 Product Presentation

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

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

SPIDER Front-End History 1988 ... 1997 1999 2000 2001 Time axis SPIDER rel. 1 SPIDER rel. 7 SPIDER rel. 8 SPIDER rel. 9 SPIDER rel. 10 Front-End 200 RCS210 RCS300 DCU PCU400 Release 1 used with SPIDER in BKK Release 3 Introduced in SPIDER

Technology steps Commercial open interfaces Gives flexibility!

PCU 400, Schematic picture Interfaces Slave Protocols IEC870-5-101 DNP 3.0 ADLP80/180 RP570 Master Protocols ADLP80 ADLP180 RP570/571 Indactic 33/41A, 2033 SINAUT 8, ST1 MODBUS RTU Field Buses LON Interfaces RSP DDE client XML OPC (future API) Control Center System XML RSP Plug-in Slave Protocols XML Communication Gateway Software Engineering Tool (Excel Based) Master RTU Protocols DDE client NT Server Field Buses Plug-in LON Used for standalone configuration Process Equipment

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

PCU 400 Connection to SPIDER Main Computer A (Unix) Main Computer B (Unix) Rest of SPIDER Rest of SPIDER RCS Application RCS Application LAN or WAN RSP Links PCU400 A PCU400 B RTU lines

PCU 400 as Front-End Functions: Front-End for SPIDER or SCADA Application Servers 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 Router WAN Router RSP protocol over Ethernet or RS-232 Can be distributed over WAN PCU 400 Available RTU protocols NG WT ZG 1 15 RTU or SCS system

PCU 400 as Concentrator for SA and SCADA Remote Master Systems 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 F.ex. IEC870-5-101 Configuration Tool NG WT ZG 1 15 NG WT ZG 1 15 RTU or Protection relay

PCU 400 as Converter Functions: Remote Master System 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 F.ex. IEC870-5-101 Configuration Tool F.ex. Indactic 2033 NG WT ZG 1 15 RTU or SA system

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

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

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

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

PCU 400 Documentation Ordering: Project Engineer Handbook: Configuration Guidelines Calculation spreadsheet Check-list Project Engineer Handbook: Notes User’s Guide Installation Manual Configuration Manual Product Sheet CPU Motherboard specification TeamCom FE-switch specification Development: Release plan Agreement NOINA & SEASY Development & Maintenance guide Functional specifications Production documents: Calculation spreadsheet Drawings Assembly Part lists

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.

PCU 400 Data flow - SCADA Customer data Data Engineering Tool (DE400) SCADA servers Loading over LAN/WAN using RSP protocol Parameter loading to RTU if supported NG WT ZG 1 15

PCU 400 Data flow - Gateway Customer data XML-files Configuration Tool REC 561 REL 5x1 LON Configuration Tool Excel based

PCU 400 Host www-server The PCU400 also supports web- interface for some protocols for remote debugging Current value Event list Logging Device status

PCU 400 Development tool Standard software Microsoft Development Studio 6.0 Language C and C++ Visual Source Safe PC based portable for site assistance

PCU 400 Hardware 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 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.

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

Customer benefits (cont.) PCU400 replaces RCS3xx PCU400 covers SCADA, SA and standalone configurations PCU 400 is a component in the SPIDER system PCU400 has potential to grow as Gateway Reduced maintenance cost New markets gives bigger volumes

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 PCU 400