Configuring System Self Supervision

. .

The definition file above will create NOD:B objects for base systems and PC-NET nodes. After this, the STAn:B objects are created for each station object created to the PC-NET nodes. This configuration should match with the configurations entered with System Configuration Tool.

When a hot stand-by switch, that is,“take-over” occurs during run-time, the main application changes to HOT state in the adjacent base system. In this situation, a procedure SHADMAPNET is executed and PC-NET nodes are informed that the application is running in another base system node. The used attribute is NET node attribute SY. For more information about the hot stand-by configuration and the run-time operation, refer to Section 3.9.1. Hot stand-by base systems.

3.4. Configuring System Self Supervision

The purpose of System Self Supervision is to provide the information about the status of SYS 600 system components to the operator. This information will be displayed in the form of supervision events to appear in the Event and Alarm Lists.

Additionally, the SYS 600 systems typically contain the System Self Supervision picture, displaying this information in a graphical view in the form of symbols and color semantics. It also shows that certain operations are possible to launch by using this same picture. For example, to perform the hot stand-by switchover or switch the redundant communication from primary communication line to the secondary manually.

The following SYS 600 system components are typically supervised: IED's, communication lines, network equipments, applications, monitors and base systems.

The real world objects supervised by SYS 600 are typically represented as process objects, which act as a placeholders for the supervision information in application.

Actually these process objects are the ones that generate events, alarms and keep the

system supervision picture updated, when configured accordingly. Beyond the process objects, it is MicroSCADA base system and communication engines that mainly provide the means for the different supervision events. Before any process object has its own supervision logic, there is need to do the application engineering by using application objects of SYS 600. In other words, by using the event channels, time channels and command procedures the logic for supervision information will be introduced into application.

While introducing the supervision logic in application, follow the design considerations given below:

1. Keep the supervision logic for each component as simple as possible.

Introducing more application objects into the re-processing chain of the same supervision event means that there will be delays and the granularity of the operation will be split to several places.

2. Represent the status information in binary way - one value representing the good status, and another value representing the bad status. In the SYS 600 process database, use process objects of type Binary Input for this. Use naming convention for the supervision process objects, as it is easier to recognize them among the other application process objects.

3. When detailed information is needed for certain system component, include detailed pictures or displays providing the detailed information on request.

4. Use Windows operating system events by using OS_EVENT predefined event channel and re-route the information into the process objects.

5. If system contains the devices capable for sending the SNMP messages in SYS 600 network, use SNMP-OPC gateway solution. It helps you to map the supervision information into process objects by using the subscription of related OPC items from the SNMP-OPC Server namespace.

6. When engineering system supervision picture, try to re-use the symbols found from the Palette of SYS 600 Display Builder. Include the color semantics representing the status information either beside the symbol or inside the symbol, when feasible.

3.4.1. Configuring application objects

To get the supervision information propagated to the process objects, it is required to develop the set of the application objects. Its main role is to re-define the

information produced by the SYS 600 base system and communication engines. In the example below, the following command procedure could be connected to the SYS_EVENT predefined event channel. For more information, refer to the Application Objects manual. The purpose of the this command procedure is to provide the values for the binary input process objects to be shown in the event and alarm lists. And to be displayed in the System Self Supervision display, when configured accordingly.

#case %SOURCE

#when "NOD" #block

#case %SOURCE_NR

#when 9 #block

#if %EVENT == "LOST" #then #set SYS_N0009:POV10 = 1

#else #set SYS_N0009:POV10 = 0

#block_end

#when 10 #block

#if %EVENT == "LOST" #then #set SYS_N0010:POV10 = 1

#else #set SYS_N0010:POV10 = 0

#block_end

#case_end

#block_end

#case_end

In some cases, some time channel based activations may be required. An example of the command procedure to be attached into time channel to supervise the PC-NET communication engine.

#if status == 0 #then #set SYS_N0003:POV10 = 0

#else #set SYS_N0003:POV10 = 1

3.4.2. Configuring communication engines for binary supervision information

For the PC-NET, the system message process objects should be created according to the definitions in the SYS 600 Application Objects manual.

PC-NET contains the extended status reporting functionality. The purpose of this is to simplify the supervision logic in application by providing the information in same way to the application layer independent from the underlying protocol type.

The extended functionality is enabled by configuring the PC-NET node System messages Enabled (SE) – attribute in the following way:

#SET NET3:SSE=4 (analog and binary status points updated)

When configured in the above way, the corresponding binary status object has an address Message Identification (MI) + 16 777 216 (MI + 1 000 000 hex). The purpose of the received value into binary process object is to indicate, whether the communication line, station object or the NET node is OK (value 1) or not OK (value 0). For more information about the binary objects with system message from PC-NET, refer to the System Objects manual. The related attributes are MI and MS.

For the IEC 61850 systems, use the following approach. When stations are connected to the SYS 600 system through IEC 61850 OPC Server, the process objects mapped to the Device connection status OPC Item per IED should be used.

Use the OPC Item IEC61850 Subnetwork\AA1CP2\Attributes\Device connection status to update the process object SYS_S0001:P10.

3.4.3. Configuring supervision symbols

The default palette of SYS 600 Display Builder contains a set of symbols, which could be used as symbols for System Self Supervision, as shown in table 3.4.3.-1.

Alternatively, it is possible to include own graphical bitmap images by using the same tool. For more information, refer to the SYS 600 Process Display Design manual.

Whether the symbols or bitmap approach is used, both of these approaches require their static contents has to be configured to add the dynamics into them separately.

Table 3.4.3.-1 Proposed graphical symbols for System Self Supervision

Functionality Symbol File Name Palette Tab

Base System ANGLED PC.SD 91– Computers

Monitor MONITOR.SD 91– Computers

Communication Line DECREASE.SD 97– International

Station IED.SD 01– SA_Common

LON Clock Master

SATELLITE DISH -WHITE-.SD

91– Computers

Printer LASER PRINTER.SD 91– Computers

3.4.4. Configuring dynamics for supervision symbols

When dynamics is added to the supervision symbols, they start to reflect the communication status of components in the system. For some supervision symbols, it may be useful to combine the dynamics inside the symbol itself producing the compact symbol with dynamics.

In Fig. 3.4.4.-1, the green color indicates active monitor (operator logged on), whereas the grey color indicates a passive monitor. The Polyline object from Objects toolbar has been used.

A071123

Fig. 3.4.4.-1 Supervision with inside symbol dynamics

Alternatively, if there is no suitable area inside the supervision symbol that could be used for dynamics, it is proposed to use rectangle or circle, beside the symbol. In Fig. 3.4.4.-2, the static symbol has been adjusted with the Rectangle object including dynamics.

A071124

Fig. 3.4.4.-2 Supervision with beside symbol dynamics