Anda di halaman 1dari 16

MicroSCADA Application Library

Product Guide

LIB 500

L IB5 0 0
S ta n d a rdF u n c tio n s E n g in e e rin g in s ta lla tio n
n a m e

A p p lic a tio n
p ic tu re

p a ra m e te riz in g
p a ra m e te ra p a ra m. . . ..................... ..................... .....................

C o n fig u ra tio n file

d a ta b a s e (o b je c ts )

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG
Issued: April 1999 Status: Updated Version: C/09.05.2006 Data subject to change without notice

Features

Fast and effective application engineering with pre-built library modules supporting ABBs product range for substation automation Base functions for the application engineering Background picture for all applications with header, pull-down menus and shortcut functions Authorization handling function

Alarm list with two templates and filtering functions Event list with filtering functions Blocking list System self-supervision handling function Busbar colouring function Data base import/export function Language converter function

Application

The LIB 500 4.0.1 Application Software Library consists of product packages for building applications. It includes pictures, dialogs and application objects for local and remote monitoring and control of power transmission and distribution substations. LIB 500 is intended for local engineering centres to make it easier, faster and safer to engineer systems for their local customers. As ABB has a wide variety of terminal product families delivered by the different product centres, an agreement has been made that each product centre supports their own products to be able to cope with product revision handling and to react fast when new products are released. LIB 500 is therefore divided into four product packages at present: The LIB 500 Base package includes the common application platform functionality and is always required when the Application Software Library is used

The LIB 510 medium-voltage process package supports products manufactured by ABB Transmit Oy, Vaasa, Finland (FIMIT) Product Centre, e.g. SPACOM protection and control terminals, SACO annunciator terminals, REF 54x protection and control terminals, SRIO gateways, RTU 2xx remote terminal units, and some other products The LIB 520 high-voltage process package supports products coming from ABB Network Partner, Vsters, Sweden (SENET) Product Centre: REL 5xx protection terminals, RET 5xx protection terminals, REB 5xx protection terminals, REC 561 control terminals, REO 500 protection and control terminals The LIB 530 high-voltage process package supports products coming from ABB Network Partner, Baden, Switzerland (CHNET) Product centre: RE. 216 protection terminals, RE. 316 protection terminals, RE. 316*4 protection and control terminals, TCS1.10 MK30E voltage regulators (Reinhausen) The SIGTOOL signal engineering package coming from ABB Network Partner, Baden, Switzerland (CHNET)

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

M VP ro cess
L IB510 M Vp ro cess
S P A C O M relay to o ls R E F 56. relay to o ls D istu rb an ce rec. to o l T ren d rep o rts M easu rem en t rep o rts

H VP ro cess
L IB 520 H V /C o n tro l
H V /R E x5xx H V /co llect

H VP ro cess
L IB530 H Vp ro cess
R ..16/*4 relay to o l R ein h au sen to o l D istu rb an ce rec. to o l S eq u en ce C o n tro ller D 20 G atew ay h an d lin g

L o cal ad ap tatio n
L IB5__

S IG T O O L L IB500 B ase
B ack B o n e fu n ctio n s -A p p licatio n settin g -H elp D ialo g -B asket -U ser M an ag em en t -S IG T O O L im p o rt/exp o rt - In stallatio n to o l -C o n fig u ratio n to o l E ven t &A larmH an d lin g B u sb ar co lo u rin g S ystemS elf S u p ervisio n L an g u ag e co n verter

Fig. 1

Library package structure

Design

Application engineering
Today there are two complementary application engineering methods to be used for creating MicroSCADA applications. One method is to build the application from the beginning using the SCIL language and the other one is to use the LIB 500 Application Software Library. The SCIL method offers total flexibility, but lacks standard solutions. The training and know-how level of the engineers ought to be high and the testing of the application is extensive. On the other hand, when using the LIB 500 method the application engineering is performed by composing LIB 500 standard functions to pictures. The application objects connected to various process functions are automatically created together with the graphical presentations and dialogs when the standard functions are installed in the application pictures. All the functions are type-tested and the complexity hidden in standard functions allows a lower entry level for the engineering. In many cases, when specific customizations are needed, a combination of the LIB 500 and the SCIL methods is used.

in respect of authorization handling, event and alarm lists, trend reports and measurement reports.

Standard functions
By using standard functions, several types of process pictures may be created in an application. A standard function may contain all available picture elements, such as background, start, update and exit programs and function keys. The only restriction, in technical respect, is that it must not contain another standard function. The visual background may, in principle, be of any size. Standard functions are created with the picture editor. The standard functions are grouped and organized in a menu structure in accordance with their purpose. The LIB 500 Base package is used as a base for the application design. The process pictures and the data objects are generated by installing standard function building blocks into the base picture containing the header and the base functionality.

Extensions of existing applications


Applications built with MicroLIBRARY versions from 3.1 on can be used in an application built with LIB 500 4.0.1, as separate pictures. It is not possible to combine them into the same picture. LIB 500 is, as far as possible, made to support earlier applications
4

Picture function
The application pictures are composed of picture function elements (also other picture elements may be included). When a standard function is installed into an application picture, it becomes a picture function.

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

A picture function is a part of the application picture though it has its own picture elements such as picture background, start, update and exit programs, function keys and windows. Each picture function is given a name that must be unique within the picture. A picture function may be repositioned. All elements of a picture function can be viewed.

The base picture which acts as a background for the application pictures contains a header with time and date presentation, pull-down menus and some shortcut push-buttons. The pull-down menus may be edited. In addition, the backbone package includes a start-up picture, accessory pictures, the picture for password handling, automatic printout picture, basket picture and notebook.

LIB 500 Base components


Backbone functions

This standard function is used as a base picture in all LIB 500 applications regarding menu configuration and default links from the default menu items.

Fig. 2

Some backbone pictures

Backbone function features

title bar

alarm row drop-down for alarm acknowledgment local/remote indication system debugging tool

date and time presentation toolbar shortcuts to event and alarm lists alarm indication

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

application setting tool: language settings, time-out for log-ins, process control settings such as close/keep dialog after control execution print/do not print user name on control execution note marker help in all dialogs title bar SigTOOL import/export User management tool
SigTOOL import/export

The modified database is brought back to the MicroSCADA application using the same import/export tool. This tool can also be used for general purpose database import and export
User management tool

The application framework contains a user authorization mechanism with four user levels VIEW LEVEL. The operator is allowed to view the application, but is not allowed to make control operations, nor to use the programming and system configuration tools. Default setting for new users is the view level CONTROL LEVEL. The operator is allowed to make control operations, but has no access to the engineering and system configuration tools ENGINEERING LEVEL. All rights are granted, excluding user management SYSTEM MANAGEMENT LEVEL. This is the system manager level. All rights are granted, including the rights to add and remove users. Each application has one and only one system manager The individual application objects can be grouped to programmable authorization groups. For each user it is possible to give a certain user level for each authorization group. If an object is not defined for a specified authorization group, it is part of the general group. In addition, a workstation with a unique IP address can be programmed to VIEW mode only. If this function is not programmed, the normal authorization mechanism will be used for the workstation.

This is a first step in the process of harmonization of the LIB 500 and SigTOOL engineering environments. The purpose is to simplify application engineering and make it more effective. The MicroSCADA application database can be created either by using the LIB 500 standard functions, or by using the SigTOOL. Both methods have advantages, and in order to combine all advantages, a link is provided between LIB 500 and SigTOOL. In the future combined method, application engineering is performed roughly as follows: A draft application database is created, along with the application pictures, using the LIB 500 standard function This draft is transferred to SigTOOL using the import/export tool Signal engineering is performed with the SigTOOL

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)
Management

Authorization level

Engineering

Control

1 0
rs ke ke rs Br ea rs ea ea Br tti ng ke Br Se er al

User 3 User 2

View

User 1

V 0k

kV

11

20

kV

la

11

Programmable authorization groups


Fig. 3 Authorization profile example

Re

Alarm list function

The alarm list displays the present alarm situation of the process supervised. Each alarm is presented as an alarm predefined text line which describes the alarm in the process. The alarm text line consists of a time stamp, object identification, a signal text and a text indicating alarm status. The alarms are shown in chronological order. The newest alarm can be presented on the top or at the end of the page.

Fig. 4

Alarm list, template 1

en

The LIB 500 alarm list has two templates: template 1 and template 2. The user can select which one to use. The templates share some of the dialogs, some dialogs are template-specific. In template 1, alarms are presented in two separate lists: the upper one contains active acknowledged and unacknowledged alarms (persisting alarms), while the lower one contains inactive unacknowledged alarms (fleeting alarms). Both lists can be scrolled.

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

Each alarm is presented as a single alarm text line. This text line consists of a time stamp (date and time), object identification (station name and bay name), signal text and status text. The length and position of each text column can be defined within certain limits. The colour of each alarm type can be selected from a predefined set of nine colours.

The most significant feature in the LIB 500 alarm list template 2 is that while the list is open, also inactive acknowledged alarms are shown in the list. They are removed with the reset function or when the alarm list picture is closed. All alarms are shown on a single list containing 32 lines of alarms. A blinking character * indicates all unacknowledged alarms, both active and inactive.

Fig. 5

Alarm list, template 2

A single alarm is acknowledged by clicking the line of the desired alarm on the list. If the selected alarm is unacknowledged, the line is highlighted and the acknowledgment dialog is opened. At the same time, the alarm list is frozen to prevent unwanted scrolling. Conditions are used when the user wants to concentrate on specific information contained in the alarm buffer. This is done by introducing a criterion to filter out unwanted information. A single criterion or multiple criteria can be used. These criteria can be freely combined to create grid-like filters. Station, bay and device names can be saved in an application-specific text file.
Alarm list features

fetched from the process database), device (device names can be fetched from the process database); function type (breakers, disconnectors, measurements, etc.); alarm class persisting and fleeting alarms separated alarm list setting tool for colours and text layout updating/frozen presentation modes alarm acknowledgment: single object, all objects alarm reset function authorization support help function available in all dialogs
Event list function

two types of alarm list templates time-based and object-based conditions: time (lower and upper time limit, one second accuracy); five-level object identification structure, default levels are station (station names can be fetched from the process database), bay (bay names can be
8

The event list presents the process events from the monitored process in time order. Each event is normally presented by displaying a predefined event text line which describes the event in the process. Event text lines consist of a time stamp, object identifi-

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

cation, a signal text and a text indicating status. The events are presented in chronological order so that the latest event appears on the bottom line of the first page. The event list contains keys for browsing the list forward and backward.

Events are normally stored in the history buffer in the computers RAM memory, and they are also stored on the computer hard disk. The number of events that can be stored is limited by the size of the hard disk. The length of the history buffer is normally 10 000 events.

Fig. 6

Event list, main view

The default event text that describes the event consists of: status sign time stamp object identification signal name status text In some applications, there is a need to change or to extend the text. It is then possible to configure the length of the columns, the order of the columns and the column labels. Conditions are used when the user wants to concentrate on specific information in the event list. This is done by introducing criteria to filter out unwanted information. One single criterion or multiple criteria can be used. These criteria can freely be combined to create grid-like filters. Station, bay and device names can be saved in an application specific text file.

Event list features

The event list layout is configurable. Depending on the character type used, more than 80 characters per line are possible Printouts are configurable The event logfile is configurable to day file, week file, month file, or year file The amount of stored events is limited only by the size of the hard disk Supervision of available hard disk space. The default limit value is 50 MB free space Scroll functions such as go to first page, scroll one line, scroll one page, scroll one interval or standard scrollbar Time-based and object-based conditions: time (lower and upper time limit, one second accuracy); five-level object identification structure, default levels are station (station names can be fetched from the process database), bay (bay names can be
9

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

fetched from the process database) and device (device names can be fetched from the process database); function type (breakers, disconnectors, measurements, etc.), alarm class updating/frozen presentation modes authorization support help function available in all dialogs
Blocking list function

presented as a predefined signal text line. In addition to the signal text, a check box indicates the blocking status. An object-blocking procedure is done by choosing it from the application picture or by request from the process database and consequently activating the chosen blocking condition. Automatic blocking procedures are possible as well. For instance, when the station is switched for local control, all objects connected to the station can automatically be alarm-blocked.

The blocking list is a summary display of the present blocking situation in the process which is supervised. Each blocked signal is

Fig. 7

Blocking list example

The MicroSCADA version 8.4.1 provides a wide range of blocking attributes, which all are included in the blocking list as well. To provide a blocking handling mechanism in a more clear and rational way, the following blocking types are provided by the LIB 500 blocking list: alarm blocking: alarms are not raised, regardless of object state update blocking: indications are not updated from the process control blocking: operation commands are not sent to the process

event blocking: event recordings are not made, events are not shown in the event list action blocking: event channel activation is blocked
Blocking list features

easy signal selection selection of signals for blocking/deblocking blocking list setting tool printout of blocking situation printout blocking: events are not sent to the printer

10

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

authorization support help function available in all dialogs


System self-supervision function

The system self-supervision function provides standard functions for the supervision of system objects. The system overview displays the status information of the hardware, system components, communication equipment and process control and protection units.

The status information of hardware and software can be displayed by both colour information or numerical information. The status information can also be stored in the history buffer and be set to give alarm at critical values or limits.

Fig. 8

System self-supervision

System self-supervision features

DCP-NET and PC-NET supervision NET line supervision NET printer supervision process control and protection unit supervision X-monitor and VS-monitor supervision help function available in all dialogs
Busbar colouring function

should be able, at a glance, to see whether a busbar segment is earthed, energized or deenergized. This helps to prevent incorrect switching operations even when switching operations have to be performed in stress situations. Especially in large networks, the operator needs to know which bays are being supplied by which intake feeder (e.g. intake feeder, generators). Thanks to a better overview, undesired parallel switching of unsynchronized network parts can be prevented, and the operator can react quicker to the loss of an intake or generator. The busbar colouring software package consists of three main components:

The busbar colouring function provides dynamic colouring of the single-line diagram process picture. The purpose of busbar colouring is to give the operator a quick overview of the actual state of the switchyard or network. The operator

11

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

Single-line editor: It is used to create the single-line diagram for the switchyard and convert it into elements necessary for topology calculation. Topology Calculation: This consists of calculating the actual state of each of the busbar sections. The actual switch states are the input to topology calculation, and colouring of the individual busbar sections is the output. A new topology calculation will be triggered by a change in the state of a switch element.

Topology Presentation: This consists of displaying the calculated colours for each of the busbar sections at the station level.

Fig. 9

Busbar colouring example

The user has the possibility to select between approximately 35 different colours. Operating equipment such as transformers and reactors can either be coloured according to the appropriate busbar section or have a fixed colour which is independent of the topology. The status of the switch elements and the colour (= priority) of the individual busbar sections are stored in the MicroSCADA process database
Busbar colouring features

energized, de-energized, earthed and unknown states are presented in different colours multiplied infeeds can be distinguished by different colours voltage levels (also transformer windings) can be distinguished by different colours freely definable colours up to 200 stations, may be limited by computer resources up to 1000 switches per station a single line may be spread over multiple pictures bidirectional connection to the topology environment
12

fast recognition of infeed conditions coloured sections in the single-line picture show the state of the process

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Design (contd)

creation of single lines supported by the single-line editor


Language converter function

previous translations and keyword functions, which make the translation of repeated phrases and words faster.

The language converter is a tool for the translation of LIB 500 text files. It offers a translation interface and the possibility to utilize

Fig. 10

Language converter main view

Language converter features

support of the LIB 500 structure support to use previous translations support for three different text file formats

fonts and maximum length of translation are changeable functions for adding, editing and using keywords help function available in all dialogs

13

MicroSCADA Application Library


Product Guide

LIB 500
1MRS750444-MBG

Technical data

Table 1: General requirement


LIB 500 4.0.1 requires the MicroSCADA release 8.4.1 or newer. All other product names are trademarks, registered trademarks, or service marks of their respective owners.

14

ABB Oy
Distribution Automation P.O. Box 699 FI-65101 Vaasa, FINLAND Tel +358 10 22 11 Fax +358 10 224 1094 www.abb.com/substationautomation