Generic System Supervision

 Generic System Supervision Functions
MicroSCADA Pro ABB Grid Automation
Generic System Supervision Functions
DocNo/Rev. Page 1 / 47
Contents
0 REVISION HISTORY ............................................................................................. 4
1 INTRODUCTION ................................................................................................... 5
2 WINDOWS SERVICE & PROCESS SUPERVISION FUNCTIONS ........................ 6

Operation .......................................................................................................... 6
Configuration ..................................................................................................... 7
Configurable Attributes ................................................................................. 7
Object Name, Index and Object Identifiers .................................................... 8
Example Configuration Windows Process..................................................... 9
Example Configuration Windows Service.................................................... 10
Application Objects Windows Process............................................................. 12
Application Objects Windows Service.............................................................. 12
Files Windows Process ................................................................................... 13
Files Windows Service .................................................................................... 13
Dependencies ................................................................................................. 14
Mapped subdrawings ...................................................................................... 14
3 ICMP (PING) DEVICE SUPERVISION ................................................................ 15
Operation ........................................................................................................ 15
Configuration ................................................................................................... 15
Configurable Attributes ............................................................................... 15
Object Name and Index .............................................................................. 16
Example configuration ................................................................................ 16
Application Objects.......................................................................................... 17
Files ................................................................................................................ 18
Dependencies ................................................................................................. 18
4 SYSTEM UPTIME FUNCTION ............................................................................ 20
General ........................................................................................................... 20
Operation ........................................................................................................ 20
Configuration ................................................................................................... 21
Object Name and Indices and Object Identifier ........................................... 21
Example Configuration................................................................................ 21
Files ................................................................................................................ 25
Dependencies ................................................................................................. 26
5 SYS600 GLOBAL MEMORY POOL SUPERVISION........................................... 27
General ........................................................................................................... 27
Operation ........................................................................................................ 27
Configuration ................................................................................................... 33
Object Name and Indices and Object Identifier ........................................... 33
Example Configuration................................................................................ 34
Files ................................................................................................................ 36
Dependencies ................................................................................................. 37
0 Revision History
Date Version Description/Changes Written Approved
by by
21.04.2017 1.0 First version AnBr
05.11.2017 1.1 Added functions for global memory pool AnBr
supervision and parallel queue supervision
1 Introduction
This document describes two SA-LIB addon functions:
- ICMP (ping) Supervision
o Sends a ping request to given device. The function can generate alarm
when it’s connected or disconnected.
- Windows Service Supervision
o Generates alarm in case abnormal state is entered for a given Windows
Service. The abnormal state can be configured as running or not running.
- Windows Process Supervision
o Generates alarm in case abnormal state is entered for the Windows
Process. The abnormal state can be configured as running or not running.
Additionally this function can also keep a count on how many processes
with the same image name is running. If that count differs from configured
count, an alarm is generated.
- System Uptime
o Indicates SYS600 system uptime for up to the last 10 years. The indications
show daily, weekly, monthly and yearly uptime in percent.
- SYS600 Global Memory Pool Supervision
o Logs SYS600 system global memory pool usage. Trends are analyzed and
a continous increasing usage of memory will cause alarms. Trends are
analyzed both for a 1h time period.
All functions support Hot Standby Server Configurations. For the Process and Service
Supervision functions, this means that alarm is also generated if a service or process
on the Standby server enters an abnormal state.
2 Windows Service & Process Supervision Functions
Operation
The only user interaction with these functions is alarm indication and
acknowledgement. The indications are typically LED-type symbols or texts. Clicking
these symbols will allow authorized users to acknowledge the alarm.
Below is a few of the available symbols.
When clicking any of the symbols, the acknowledgement dialog is opened.
Configuration
The functions are installed through the standard interface in Object Navigator. Once
the SA-LIB Addon package has been installed, the functions are available under
- Standard Functions > SA_LIB > Supervision > Windows Service Supervision
- Standard Functions > SA_LIB > Supervision > Windows Process Supervision
Configurable Attributes
Some of the configuration attributes are known from the standard SA-LIB functions.
They also have the same meaning as for other SA-LIB functions. These are listed in
the table below.
Attribute name Description
AUTHORIZATION_GROUP The authorization group name that

determines whether or not specific
users can acknowledge the alarm.
Level within given group must be at
least 1 – Control. If left empty, the
group ALARM_HANDLING is used.
Common attribute for both functions:

ALARM_ON_RUNNING When this option is checked, an
alarm is generated when the service
or process is running, otherwise
alarm is generated when service or
process is NOT running.
RUN_ON_HSB_SERVERS Checking this box will make the
function check the state of given
process or service also on the Hot
Standby server. If not checked it is
only checking on the currently hot
server.
Attributes for Service Supervision:

SERVICE_NAME The name of the Windows Service to
supervise. Note that this name is
NOT the Display Name, but the
service name found in the Service
properties, General tab. The service
name is normally shorter and does
not include special or space
characters.
The service name vs. display name example:
Attributes for Process Supervision:

PROCESS_NAME The name of the Windows Process
to supervise. This name is the Image
Name, seen in Task Manager
Processes tab. No file path should
be given. The name is not case
sensitive. Examples:
NotePad.exe
explorer.exe
DAOPCCL.EXE
PROCESS_COUNT How many instances of
PROCESS_NAME should be
running. Range is 1..50. Note that if
ALARM_ON_RUNNING is selected,
this number has no meaning – only
one instance running is enough to
generate alarm.
Object Name, Index and Object Identifiers
The process object name (P_OBJECT_LN) is generated automatically based on the

SERVICE_NAME or PROCESS_NAME. Any illegal characters are automatically
removed from the name. For Process supervision the prefix WINPRO_ is used and for
Service supervision WINSVC_.
Examples:
Service or Process Name Generated P_OBJECT_LN
PROCESS_NAME: notepad.exe WINPRO_NOTEPADEXE
PROCESS_NAME: my app.exe WINPRO_MYAPPEXE
SERVICE_NAME: pla WINSVC_PLA
SERVICE_NAME: WINSVC_MSSQLPCMSERVER
MSSQL$PCMSERVER
The process object index is always 10.
The Object Identifiers are not used, except STATION_NAME which is automatically set
to the System Name (SYS:BCX attribute).
Example Configuration Windows Process
Generate an alarm when somebody start Internet Explorer.
Create process object:
Add a symbol in display:
Test by starting Internet Explorer. Within 30 seconds you should get an alarm:
Display:
And close internet Explorer. The alarm should reset:
Example Configuration Windows Service
Alarm when Performance Log & Alerts service (pla) stops.
Create process object:
You can also add same symbols in a display as for the Windows Process function.
Test by starting and stopping pla service:
Alarming:
Application Objects Windows Process
Object Type Object Name Description

Command WINPROCESS_1 Executed cyclically from time
Procedure channel WINPROCESS. This
procedure finds and updates all
process objects for Windows
Process Supervision.
Command WINPROCESS_2 Called from WINPROCESS_1
Procedure with do() command. This
procedure looks for running
processes in OS using Windows
command ‘tasklist’. It takes the
process name as an argument.
Returns the number of running
instances for given process.
Time Channel WINPROCESS Runs cyclically every 30 seconds.
Executes command procedure
WINPROCESS_1
Event Handling WINPROCESS Used by process object index 10
Application Objects Windows Service

Command WINSERVICE_1 Executed cyclically from time
Procedure channel WINSERVICE. This
procedure finds and updates all
process objects for Windows
Service Supervision.
Command WINSERVICE_2 Called from WINSERVICE _1 with
Procedure do() command. This procedure
looks for services in OS using
Windows command ‘sc’. It takes
the service name as an argument.
Returns a 1 when service is
running, 0 if it’s not running (or not
found).
Time Channel WINSERVICE Runs cyclically every 30 seconds.

WINSERVICE _1
Event Handling WINSERVICE Used by process object index 10
Files Windows Process
All files associated with this function are placed in folder sc\sa_lib\base\nam
subfolders.
File path name Description

inst\SAI_WINPROCESS.DAT Standard Function Configuration file.
inst\SAI_WINPROCESS.POT Process object definition, creation of other
application objects.
inst\WINPROCESS_1-xx-yy-zz.txt SCIL code for command procedure
WINPREOCESS_1. The version number
may vary for different versions of Addon
package.
inst\WINPROCESS_2-xx-yy-zz.txt SCIL code for command procedure
package.
lang0\SAI_WINPROCESS.TXT Language dependent texts for application
objects.
lang0\SAI_WINPROCESS.HLP Help file for Standard Configuration Tool.
Files Windows Service
subfolders.

inst\SAI_WINSERVICE.DAT Standard Function Configuration file.
inst\SAI_ WINSERVICE.POT Process object definition, creation of other
inst\ WINSERVICE_1-xx-yy-zz.txt SCIL code for command procedure
WINSERVICE_1. The version number may
vary for different versions of Addon package.
inst\ WINSERVICE_2-xx-yy-zz.txt SCIL code for command procedure
package.
lang0\SAI_ WINSERVICE.TXT Language dependent texts for application
objects.
lang0\SAI_ WINSERVICE.HLP Help file for Standard Configuration Tool.
Dependencies
These functions use the following files and application objects:
 api_update.txt
 API_SALIB:C
Mapped subdrawings
The following subdrawings can be used with these functions:
04 - SA_Indication\Tripping.sd
20 - NAM_Indications\LED OX Left.sd
20 - NAM_Indications\LED OX Right.sd
20 - NAM_Indications\LED Status OX Left.sd
20 - NAM_Indications\LED Status OX Right.sd
20 - NAM_Indications\LED Status.sd
20 - NAM_Indications\LED.sd
20 - NAM_Indications\Square LED OX Left.sd
20 - NAM_Indications\Square LED OX Right.sd
20 - NAM_Indications\Square LED Status OX Left.sd
20 - NAM_Indications\Square LED Status OX Right.sd
20 - NAM_Indications\Square LED Status.sd
20 - NAM_Indications\Square LED.sd
20 - NAM_Indications\Status Tag Letters.sd
21 - NAM_Alarms\Alarm Tag Background Status Color.sd
21 - NAM_Alarms\Alarm Tag Text Status Color.sd
21 - NAM_Alarms\Alarm Tile.sd
21 - NAM_Alarms\LED Alarm Descr Left.sd
21 - NAM_Alarms\LED Alarm Descr Right.sd
21 - NAM_Alarms\Square LED Alarm Descr Left.sd
21 - NAM_Alarms\Square LED Alarm Descr Right.sd
21 - NAM_Alarms\Square LED Alarm.sd
21 - NAM_Alarms\LED Alarm.sd
3 ICMP (ping) Device Supervision
Operation
This function has the same operation as described in chapter 2.1.
Configuration
The function is installed through the standard interface in Object Navigator. Once the
SA-LIB Addon package has been installed, the function is available under
- Standard Functions > SA_LIB > Supervision > ICMP (PING) Device Supervision
The configurable attributes are listed in table below.

STATION_NAME Station name of the Object Identifier
BAY_NAME Bay name of the Object Identifier
DEVICE_NAME Device name of the Object Identifier
SPECIAL_IDENTIFIER_1 Additional Object Identifiers if application is
SPECIAL_IDENTIFIER_2 configured to use them.
P_OBJECT_LN Process object name, common name for all
process object indices for this particular
function.
determines whether or not specific users can
control the switch. Level within given group
must be at least 1 – Control. If left empty, the
HOST_NAME_OR_IP_ADDRESS Enter the host name or IP-address to
supervise here. Some examples:
PRINTER01
10.11.12.13
WS-03
www.mysite.com
If host name is used, the Windows hosts file

must be updated.
ALIAS_NAME A more human readable name. If this is left

empty, the HOST_NAME_OR_IP_ADDRESS
will be used in the OX attribute for the alarm
process object. If a name is entered it will be
used in OX attribute.
ALARM_WHEN_CONNECTED When this option is checked, an alarm is

generated if the host can be reached.
When unchecked, alarm is generated when
host is not reached.
PING_COUNT Number of PING attempts. Range is 1..5.

This is the -n switch in a ping echo request in
Windows.
PING_WAIT_TIME_MS Number of milliseconds to wait for the reply
from host. Range is 100..5000ms. This is the
-w switch in ping echo requests in Windows.
On a slow network this value can be
increased.
Object Name and Index
The process object name (P_OBJECT_LN) is generated automatically based on the

HOST_NAME_OR_IP_ADDRESS. The name is prefixed by ICMP_. Examples:
ICMP_192_168_1_5
ICMP_WORKSTATION01
ICMP_WWWABBCOM
The process object index is always 10.
Example configuration
Alarm when IP-address 192.168.127.132 is lost.
Create process objects:
When disconnected, you should get an alarm:
Application Objects

Command ICMPSUP_1 Executed cyclically from time
Procedure channel ICMPSUP. This procedure
finds and updates all process
objects for ICMP Device
Supervision.
Command ICMPSUP_2 Called from ICMPSUP_1 with do()
Procedure command. This procedure looks
for services in OS using Windows
command ‘ping’. It takes the host
name or IP-address as an
argument. Return values:
>0 ping reply time if connected
-1 when no connection
0 if time could not be resolved
Time Channel ICMPSUP Runs cyclically every 30 seconds.
ICMPSUP_1
Event Handling ICMPSUP Used by process object index 10
Files
subfolders.

inst\SAI_ICMPSUP.DAT Standard Function Configuration file.
inst\SAI_ ICMPSUP.POT Process object definition, creation of other
inst\ ICMPSUP_1-xx-yy-zz.txt SCIL code for command procedure
ICMPSUP_1. The version number may vary
for different versions of Addon package.
inst\ ICMPSUP_2-xx-yy-zz.txt SCIL code for command procedure

ICMPSUP_2. The version number may vary
for different versions of Addon package.
lang0\SAI_ ICMPSUP.TXT Language dependent texts for application
objects.
lang0\SAI_ ICMPSUP.HLP Help file for Standard Configuration Tool.
Dependencies
This function uses the following files and application objects:
 api_update.txt
 API_SALIB:C

Mapped subdrawings
The following subdrawings can be used with this function:
04 - SA_Indication\Tripping.sd
20 - NAM_Indications\LED OX Left.sd
20 - NAM_Indications\LED OX Right.sd
20 - NAM_Indications\LED Status OX Left.sd
20 - NAM_Indications\LED Status OX Right.sd
20 - NAM_Indications\LED.sd
20 - NAM_Indications\Square LED OX Left.sd
20 - NAM_Indications\Square LED OX Right.sd
20 - NAM_Indications\Square LED Status OX Left.sd
20 - NAM_Indications\Square LED Status OX Right.sd
20 - NAM_Indications\Square LED Status.sd
20 - NAM_Indications\Square LED.sd

21 - NAM_Alarms\Alarm Tag Background Status Color.sd
21 - NAM_Alarms\Alarm Tag Text Status Color.sd
21 - NAM_Alarms\Alarm Tile.sd
21 - NAM_Alarms\LED Alarm Descr Left.sd
21 - NAM_Alarms\LED Alarm Descr Right.sd
21 - NAM_Alarms\Square LED Alarm Descr Left.sd
21 - NAM_Alarms\Square LED Alarm Descr Right.sd
21 - NAM_Alarms\Square LED Alarm.sd
21 - NAM_Alarms\LED Alarm.sd
4 System Uptime Function
General
Uptime is defined as an application that is up and running and functioning in a normal

manner. It does not take into account any other things, such as communication.
This function has a 10 second ‘heartbeat’. Some accuracy is lost whenever the
SYS600 is started and stopped. The accuracy error is max 9 seconds. Total accuracy
depends on how many times the system has been restarted – this function does not
keep track of restarts.
Operation
The system uptime is presented in displays as a normal measurement. Also all the
subdrawings available for normal measurements are also available for system uptime.
The user can set limits etc. from the standard Measurements control dialog.
Configuration
- Standard Functions > SA_LIB > Supervision > System Uptime

DAY_UPTIME Checking this box will install process object
for daily uptime
WEEK_UPTIME Checking this box will install process object
for weekly uptime
MONTH_UPTIME Checking this box will install process object
for monthly uptime
YEAR_UPTIME Checking this box will install process object
for yearly uptime
Object Name and Indices and Object Identifier
The process object name (P_OBJECT_LN) is hardcoded to SYS_UPTIME. The indices

are listed in table below.
Index Description
10 Yearly uptime (one year back from current time)
11 Weekly uptime (one week back from current time)
12 Monthly uptime (since same day in previous month from
current time)
13 Daily uptime (24 hours back from current time)
The object identifiers are hardcoded:

STATION_NAME = [System Name]
BAY_NAME = “UPTIME”
Example Configuration
Install with all options:
Create the process objects:
Add to the display:
Now you can access this as a normal measurement:
Application Objects
Command SYS_UPTIME_GET Returns system uptime for a given

Procedure period. Executed with do()
command from
SYS_UPTIME_WRITE.
Command SYS_UPTIME_START Executed at startup from
Procedure APL_INIT_1 event channel
Command SYS_UPTIME_STOP Executed from event channel
Procedure APL_CLOSE when stopping
SYS600.
Command SYS_UPTIME_WRITE Executed from time channel
Procedure SYS_UPTIME_WRITE. Writes
uptime in seconds for a 1 minute
period to data object
SYS_UPTIME2.
Time Channel SYS_UPTIME_HBEAT Executed every 10 seconds. Used
by data object SYS_UPTIME1.
Time Channel SYS_UPTIME_WRITE Executed every minute. Used by
command procedure
SYS_UPTIME_WRITE.
Data Object SYS_UPTIME1 Contains 10 second data samples.
Data Object SYS_UPTIME2 Contains 3 minute data samples.
Command procedure SYS_UPTIME_GET can be used in other SCIL programs to find

the uptime for a specific period. The procedure takes two arguments, start and end
time in SCIL TIME data format. If end time is left out, it uses current time. The seconds
are ignored, so the result is rounded off to current minute.
For example, to get the uptime for this year to date, you can use the following SCIL
code:
@start = pack_time(year,1,1,0,0,0)
@uptime = do(SYS_UPTIME_GET:C,%start)
No need to give an end time because it automatically uses current time. Variable
%uptime will now be a LIST:
The attribute AVAILABILITY is the uptime percentage.
To get the uptime for last year:

@start = pack_time(year - 1,1,1,0,0,0)
@end = pack_time(year,1,1,0,0,0)
@uptime = do(SYS_UPTIME_GET:C,%start, %end)
Files
subfolders.

inst\SAI_UPTIME.DAT Standard Function Configuration file.
inst\SAI_UPTIME.POT Process object definitions
inst\SAI_UPTIME_OK.SCL Executed when pressing Apply or OK in
SCT. This program will create all application
objects.
inst\SYS_UPTIME_GET-xx-yy- SCIL code for command procedure
zz.txt SYS_UPTIME_GET. The version number
package.
inst\SYS_UPTIME_START-xx-yy- SCIL code for command procedure
zz.txt SYS_UPTIME_START. The version number
package.
inst\SYS_UPTIME_STOP-xx-yy- SCIL code for command procedure
zz.txt SYS_UPTIME_STOP. The version number
package.
inst\SYS_UPTIME_WRITE-xx-yy- SCIL code for command procedure
zz.txt SYS_UPTIME_WRITE. The version number

package.
lang0\SYS_UPTIME.TXT Language dependent texts for process
objects.
lang0\SYS_UPTIME.HLP Help file for Standard Configuration Tool
Dependencies
 api_update.txt
Mapped subdrawings
05 - SA_Measurement\Value FG.sd
05 - SA_Measurement\Value FG Basic.sd
05 - SA_Measurement\Value BG.sd
05 - SA_Measurement\Value BBox.sd
05 - SA_Measurement\Value.sd
05 - SA_Measurement\Bar Graph.sd
05 - SA_Measurement\Line Graph 20 Samples.sd
05 - SA_Measurement\Circle.sd
05 - SA_Measurement\Current Transducer IEC.sd
05 - SA_Measurement\Current Transducer IEC H.sd
05 - SA_Measurement\Voltage Transducer IEC.sd
05 - SA_Measurement\Voltage Transducer IEC H.sd
05 - SA_Measurement\Current Transducer ANSI.sd
05 - SA_Measurement\Current Transducer ANSI H.sd
05 - SA_Measurement\Voltage Transducer ANSI.sd
05 - SA_Measurement\Voltage Transducer ANSI H.sd
23 - NAM_Measurements\Tag Value Unit.sd
23 - NAM_Measurements\Tag Value Unit Background Status.sd
23 - NAM_Measurements\Tag Value Unit Background Conf.sd
5 SYS600 Global Memory Pool Supervision
General
The global memory pool is accessed by all SYS600 base system processes. It is used
for process and report databases, execution queues, inter-process communication and
so on. The pool is pre-allocated and fixed in size. If it is exhausted, a hot stand-by
switchover is initiated. In a non-HSB system, the kernel tries to continue, but the
application may not function properly.
If the memory pool usage continously increasing it may be sign of misconfiguration or

some function not releasing memory after using it.
This function will log the used amount in percentage of the global memory pool and
continously check the trend. Alarms can be set to activate if the trend slope is
increasing too much during a time period. The logged data is stored for 90 days.
This function should mainly be used during configuration, troubleshooting and

engineering. In normal operating conditions it can be turned off.
Operation
The values can be shown in process displays and you can open the standard
Measurement Control dialog by clicking on the symbol.
The values are shown in Simulated state since they are not connected to any process
units.
An additional detailed control dialog with information and trend curves can also be
opened. Access the control dialog by right-click > Details…:
NOTE! If you cannot see the Details… menu, try to click to open the Measurement
dialog and then try right-click again.
The control dialog opens:
Control
From this dialog the user can turn the function on and off. Required authorization level
is 1 – Control.
The control button also indicates by colors and text the state of the function.
RUNNING – The function is running and loggin data

STOPPED – Function is stopped, no data is logged
UNKNOWN – There is a discrepancy when checking the state, see configuration
chapter.
Colors:
The RUNNING and STOPPED states when everything is ok, the color used is the
Generic state On and OFF colors.
If something is not quite right (mainly, if the standby server is unreachable in a HSB
system), the Warning status color is used.
By hovering over the button you will get a detailed ‘status message’.
To operate, click on the control button and answer Yes to confirm or No to cancel.
Measurements
Measurements are seen under the server name. There are two measurement values
shown:
1. Memory Pool Usage in percent. This is tha latest logged value.

2. Memory Pool Trend. This is a factor showing how much the value has increased
(positive value) or decreased (negative value) during the last hour. In most cases
values are very small. To calculate this trend, it requires at least 90% good data
samples for the 1 hour period. This means that with 30 second samples, at least
108 of the 120 samples must be good quality.
If installed on a Hot Standby system, there will be two sets of the values.
Hovering with the mouse over the value will show the latest time stamp of the value. By
clicking on the status button (left side of value), the limits (and blockings) can be set.
If the value has an unacknowledged alarm, there will be a tab to acknowledge it.
Trends
Trends are shown in graphs. The time span, start and end times can be modified. The
detault time span is approximately 1 hour, but depends on the actual time stamps of
the values.
Referring to the numbers in picture below, hereis a brief explanation.
1. Show or hide curves using the check box

2. Set time span, or a combination of start and end times.
3. Toggle real-time update. If clock is green, it is updating in real time. There is a
countdown timer until next update above the button.
4. Menu with additional graph settings
All settings are user specific and automatically stored when the dialog is closed. To
restore the default settings, a file sc\apl\’apl name’\PAR\’user name’\sys_gmem.sdb file
should be renamed or deleted by an administrator.
There are two trend curves, note that the trend slope is not shown by default:
1. The memory pool usage in percent

2. The trend slope – if the increase during the last 1 hour is steeper than this curve, an
alarm is generated. This can be set by editing the High Limit of the trend value.
The example below demonstrates how to read the trend curves. If the orange curve
(memory pool usage) slope had increased more than the green curve during the last 1
hour, an alarm is generated.
Please note that the Trend Slope curves are not updated at the same time as the
Usage curves, so if e.g. changing the time span it may take up to 30 seconds for the
Trend Slope curves to update.
Configuration
- Standard Functions > SA_LIB > Supervision >Global Memory Pool Supervision

STATION_NAME Object Identifier station name
BAY_NAME Object Identifier bay name
DEVICE_NAME Object Identifier device name
SPECIAL_IDENTIFIER_1 Object Identifier, additional fields. These will
SPECIAL_IDENTIFIER_2 only appear if the application has been
configured to use additional identifiers.
RUN_ON_HSB_SERVERS This option will be enabled if installed on a
Hot Standby System. If checked, the
memeory pool will be logged on both
servers, otherwise it will only log the Hot
server.
SERVER_1_NAME Name of the first server, defaults to the
computer host name. The first server is the
one with a lower Base System Node Number
(SYS:BND).
SERVER_2_NAME Name of the second server, only used if
RUN_ON_HSB_SERVERS is checked.
group SUPERVISION is used.
The user needs authorization level 1 or

higher to be able to control and set limits.
The process object name (P_OBJECT_LN) is hardcoded to SYS_GMEMSUP1. If

RUN_IN_HSB_SERVERS is checked, another set of process objects is created as
SYS_GMEMSUP2.
The indices are listed in table below.

Index Description
10 The logged real-time value of global memory pool
11 The calculated trend factor for the last 1 hour. The trend
factor is calculated using linear regression on the collected
real-time values for the last hour.
Install on a Hot Standby System. Make sure both Hot and Standby servers are running
and connected. Install from the main application:
Create the process objects. Note that you will only see the process objects for server 1
here, even if you have selected RUN_ON_HSB_SERVERS.
When clicking Apply or OK in Standard Configuration Tool, the required application

objects and the process objects for the second server are installed.
Add to the display, note that only the memory usage is available:
There are four different subdrawings available:
Application Objects

Command SYS_GMEMSUP_1 Writes the current ‘real-time’
Procedure values to process objects.
In a HSB system, this command
procedure resides in both WD
applications, not in the main
application. Executed from time
channel SYS_GMEMSUP.
Command SYS_GMEMSUP_2 Takes the logged real-time data

Procedure from data objects
SYS_GMEMSUPn and calculates
the trend slope. In a HSB system
this command procedure resides in
main application only. Executed

from time channel
SYS_GMEMSUP.
Time Channel SYS_GMEMSUP Executed every 30 seconds. Used
by data objects SYS_GMEMSUP1
and SYS_GMEMSUP2 and
command procedures
SYS_GMEMSUP_1 and
SYS_GMEMSUP_2. In a HSB
system, this time channel resides
in both WD and main applications.
Data Object SYS_GMEMSUP1 Contains 30 second data samples
for server 1. In a HSB system, this
object resides in the main
application only.
Data Object SYS_GMEMSUP2 Contains 30 second data samples
for server 2. In a HSB system, this
object resides in the main
application only.
Files
subfolders.

inst\SAI_GMEMSUP.DAT Standard Function
Configuration file.
inst\SAI_ GMEMSUP.POT Process object definitions
inst\SAI_ GMEMSUP_OK.SCL Executed when pressing Apply
or OK in SCT. This program
will create all application
objects.
inst\SYS_GMEMSUP_1-xx-yy-zz.txt SCIL code for command
procedure SYS_GMEMSUP_1.
The version number may vary
for different versions of Addon
package.
inst\SYS_GMEMSUP_2-xx-yy-zz.txt SCIL code for command
procedure SYS_GMEMSUP_2.
The version number may vary
for different versions of Addon
package.
lang0\SYS_GMEMSUP.TXT Language dependent texts for
process objects.
lang0\SYS_GMEMSUP.HLP Help file for Standard
Configuration Tool
use\SYS_GMEMSUP.VSO Visual SCIL Object file for
control dialog
sc\apl\apl_name\PAR\user_name\sys_gmem.sdb User specific settings file. The

file is updated every time the
Detailed dialog is closed.
Delete this file to reset all
settings to defaults.
Dependencies
 api_update.txt (during installation)

 sys_supmain.vso (launches correct control dialog depending on function)
 disp_obj.vso (trend graphs)
 vs_dialogs.vso (measurement properties objects)
 genconftable.vso (graph settings dialog)
 api_stat:c (calculate trend slopes)
 api_salib:c (generic functions for control dialog)
Mapped subdrawings
25 - NAM_Supervision\ Queues and Pools Value.sd

25 - NAM_Supervision\ Queues and Pools Background Status.sd
25 - NAM_Supervision\ Queues and Pools Tag Value Unit.sd
25 - NAM_Supervision\ Queues and Pools Background Conf.sd
6 SYS600 Application Queue Supervision
General
The application queues are used to buffer application object execution, such as
command procedures and data objects. There are five different queues of interest:
- Process Event Queue. Incoming updates of a process object that will run an event
channel are queued here. When this queue reaches its maximum, the incoming
data updates are not accepted, which normally means that the data will be stored in
a buffer of the process device (IED, RTU etc.)
- Time Channel Queue. All objects that are executed by a time channel (and not
assigned to any parallel queues) are queued here.
- Event Channel Queue All objects that are executed by an event channel (and not
assigned to any parallel queues) are queued here.
- Parallel Execution Queues (0..30 queues possible, configurable).
- Delayed Execution Queue. Objects executed by the SCIL statement #exec_after
will use this queue to wait for its execution.
If any of the queues are starting to build up, it could eventually mean that data is lost or
some function stops working. In most cases when this happens, it is caused by a
command procedure that is taking to long to execute and therefore the queues start
building up. The root cause for the long execution time must be investigated.
Using this function, it is possible to catch any problems with the queues before they
overflow. A trend slope factor is calculated and an alarm is generated if the slope factor
is too high (this essentilally means that the queue is growing faster than expected). The
default time period used is 15 minutes.
This function does not have any specific Hot Standby functionality, but can be installed
in both single and hot standby systems. It is always the main application queues that
are supervised, in hot standby system, the watchdog application is NOT supervised.
Operation
The values can be shown in process displays and you can open the standard
Measurement Control dialog by clicking on the symbol. Note that the trend slope factor
can also be shown in process displays, but it is not possible to open the measurement
control dialog.
The Process Event Queue is separated from the others:
The values are shown in Simulated state since they are not connected to any process
units.
An additional detailed control dialog with information and trend curves can also be
opened. Access the control dialog by right-click > Details…:
The detailed dialog can be opened both from the Used and Trend symbols.
NOTE! If you cannot see the Details… menu, try to click to open the Measurement
dialog and then try right-click again.
The control dialog opens:
Control
From this dialog the user can turn the function on and off. Required authorization level
is 1 – Control.
The control button also indicates by colors and text the state of the function.
RUNNING – The function is running and loggin data

STOPPED – Function is stopped, no data is logged
UNKNOWN – There is a discrepancy when checking the state, see configuration
chapter.
Colors:
The RUNNING and STOPPED states when everything is ok, the color used is the
Generic state On and OFF colors.
If something is not quite right (mainly, if the standby server is unreachable in a HSB
system), the Warning status color is used.
By hovering over the button you will get a detailed ‘status message’.
To operate, click on the control button and answer Yes to confirm or No to cancel.
Measurements
Measurements are seen under each of the queue names. There are two measurement
values shown per queue:
3. Queue Usage in percent. This is tha latest logged value. This value is updated
every 10 seconds, except when the control dialog is open it is updated every 2
seconds.
4. Queue Trend. This is a factor showing how much the value has increased (positive
value) or decreased (negative value) during the last 15 minutes. In most cases
values are very small. To calculate this trend, it requires at least 90% good data
samples for the 15 minute period. This means that with 10 second samples, at least
81 of the 90 samples must be good quality. This value is recalculated every 10
seconds.
Hovering with the mouse over the value will show the latest time stamp of the value. By
clicking on the status button (left side of value), the limits (and blockings) can be set.
If the value has an unacknowledged alarm, there will be a tab to acknowledge it.
Trends
Trends are shown in graphs. The time span, start and end times can be modified. The
detault time span is approximately 15 minutes, but depends on the actual time stamps
of the values.
Refer to chapter Trends for Global Memory Pool Supervision for details about the trend
graphs.
There are two trend curves per queue, note that the trend slope is not shown by
default:
1. The queue usage in percent (Queue Used/Queue Max*100)

2. The trend slope – if the increase during the last 15 min is steeper than this curve,
an alarm is generated. This can be set by editing the High Limit of the trend value.
Configuration
- Standard Functions > SA_LIB > Supervision >Application Queues Supervision

STATION_NAME Object Identifier station name
BAY_NAME Object Identifier bay name
DEVICE_NAME Object Identifier device name
SPECIAL_IDENTIFIER_1 Object Identifier, additional fields. These will

SPECIAL_IDENTIFIER_2 only appear if the application has been
configured to use additional identifiers.
group SUPERVISION is used.
The user needs authorization level 1 or

higher to be able to control and set limits.
The process object name (P_OBJECT_LN) is hardcoded to SYS_QUESUP1. The

indices are listed in table below.
Index Description
10 Sampled real-time usage value of time channel queue in %
11 Sampled real-time usage value of event channel queue in %
12 Sampled real-time usage value of parallel queue in %
13 Sampled real-time usage value of delayed execution queue in %
14 Sampled real-time usage value of process event queue in %
15 Trend slope factor for time channel queue
16 Trend slope factor for event channel queue
17 Trend slope factor for parallel queue
18 Trend slope factor for delayed execution queue
19 Trend slope factor for process event queue
Install from the main application:
Create the process objects.
When clicking Apply or OK in Standard Configuration Tool, the required application

objects are installed.
Add to the display:
There are four different subdrawings available, same as for Memory Pool Supervision:
Application Objects

Command SYS_QUESUP_1 Writes the current ‘real-time’
Procedure values to process objects.
Command SYS_QUESUP_2 Takes the logged real-time data

Procedure from data objects SYS_QUESUPn
and calculates the trend slope.
Time Channel SYS_QUESUP Executed every 10 seconds. Used
by data objects SYS_QUESUPn,
command procedures
SYS_QUESUP_1 and
SYS_QUESUP_2.
Data Object SYS_QUESUP1 Contains 10 second data samples
for time channel queue.

for event channel queue.
for parallel queue.
for delayed execution queue.
for process event queue.
Files
subfolders.

inst\SAI_QUESUP.DAT Standard Function
Configuration file.
inst\SAI_ QUESUP.POT Process object definitions
inst\SAI_ QUESUP_OK.SCL Executed when pressing
Apply or OK in SCT. This
program will create all
inst\SYS_QUESUP_1-xx-yy-zz.txt SCIL code for command
procedure
SYS_GMEMSUP_1. The
version number may vary for
different versions of Addon
package.
inst\SYS_QUESUP_2-xx-yy-zz.txt SCIL code for command
procedure
SYS_GMEMSUP_2. The
version number may vary for
different versions of Addon
package.
lang0\SYS_QUESUP.TXT Language dependent texts for
process objects.
lang0\SYS_QUESUP.HLP Help file for Standard
Configuration Tool
use\SYS_QUESUP.VSO Visual SCIL Object file for
control dialog
sc\apl\apl_name\PAR\user_name\sys_quesup.sdb User specific settings file. The
file is updated every time the
Detailed dialog is closed.
Delete this file to reset all
settings to defaults.
Dependencies
 api_update.txt (during installation)

 sys_supmain.vso (launches correct control dialog depending on function)
 disp_obj.vso (trend graphs)
 vs_dialogs.vso (measurement properties objects)
 genconftable.vso (graph settings dialog)
 api_stat:c (calculate trend slopes)
 api_salib:c (generic functions for control dialog)
Mapped subdrawings
25 - NAM_Supervision\ Queues and Pools Value.sd

25 - NAM_Supervision\ Queues and Pools Background Status.sd
25 - NAM_Supervision\ Queues and Pools Tag Value Unit.sd
25 - NAM_Supervision\ Queues and Pools Background Conf.sd

Generic System Supervision

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Generic System Supervision

Uploaded by

Copyright:

Available Formats

 Generic System Supervision Functions

MicroSCADA Pro ABB Grid Automation

Generic System Supervision Functions

0 REVISION HISTORY ............................................................................................. 4

2 WINDOWS SERVICE & PROCESS SUPERVISION FUNCTIONS ........................ 6

2 Windows Service & Process Supervision Functions

When clicking any of the symbols, the acknowledgement dialog is opened.

AUTHORIZATION_GROUP The authorization group name that

Common attribute for both functions:

Attribute name Description

Attributes for Service Supervision:

The service name vs. display name example:

Attributes for Process Supervision:

Object Name, Index and Object Identifiers

The process object name (P_OBJECT_LN) is generated automatically based on the

The process object index is always 10.

Example Configuration Windows Process

Generate an alarm when somebody start Internet Explorer.

Create process object:

Add a symbol in display:

And close internet Explorer. The alarm should reset:

Example Configuration Windows Service

Alarm when Performance Log & Alerts service (pla) stops.

Create process object:

Test by starting and stopping pla service:

Application Objects Windows Process

Object Type Object Name Description

Application Objects Windows Service

Object Type Object Name Description

Time Channel WINSERVICE Runs cyclically every 30 seconds.

Files Windows Process

File path name Description

Files Windows Service

File path name Description

These functions use the following files and application objects:

The following subdrawings can be used with these functions:

3 ICMP (ping) Device Supervision

This function has the same operation as described in chapter 2.1.

The configurable attributes are listed in table below.

Attribute name Description

If host name is used, the Windows hosts file

ALIAS_NAME A more human readable name. If this is left

ALARM_WHEN_CONNECTED When this option is checked, an alarm is

PING_COUNT Number of PING attempts. Range is 1..5.

Object Name and Index

The process object name (P_OBJECT_LN) is generated automatically based on the

The process object index is always 10.

Alarm when IP-address 192.168.127.132 is lost.

Create process objects:

When disconnected, you should get an alarm:

Object Type Object Name Description

File path name Description

inst\ ICMPSUP_2-xx-yy-zz.txt SCIL code for command procedure

This function uses the following files and application objects:

The following subdrawings can be used with this function:

20 - NAM_Indications\Status Tag Letters.sd

4 System Uptime Function

Uptime is defined as an application that is up and running and functioning in a normal

The configurable attributes are listed in table below.

Attribute name Description

Object Name and Indices and Object Identifier

The process object name (P_OBJECT_LN) is hardcoded to SYS_UPTIME. The indices

The object identifiers are hardcoded: